Tulip is designed to have minimal IT requirements. The most simple description is: If you can access the web, you can access Tulip. The rest of this article is meant for individuals with a background in Information Technology (IT) and addresses the specific firewall settings required to access Tulip.

Bandwidth Requirements

Tulip is a versatile tool that can be used for all types of different use cases. As such, the exact bandwidth requirements will vary depending on your use.

In general, Tulip does not require more bandwidth than a typical computer that is browsing the web. However, depending on application complexity or heavily used environments, additional bandwidth may be required. This can typically be monitored and scaled during a phased deployment.

The stability of the connection is also highly impactful to performance within Tulip. If the connection to the internet is intermittent (i.e. dropping off and reconnecting every few seconds), it will take substantially longer for a message to be passed from your computer to Tulip's servers.

A simple utility is available to help you test your network connection:

WebSockets

Tulip makes extensive use of WebSockets, a type of long-lived connection, to enable our real-time updates. These WebSockets use SSL-encryption over port 443. Some proxies do not support these connections and some network monitors may need to explicitly allow these connections.

You can check your connection compatibility at:

Allowlist

The section below lists all connections Tulip requires to operate as a platform, separated by Tulip component. This list represents a complete list of addresses owned by Tulip.

Refer to the following IP addresses where access to Factory is specified:

Tulip Cloud

(your-account.tulip.co)

CIDR Blocks

  • 3.208.72.192/26

  • 20.84.217.148/30

  • 52.224.191.152/30

Addresses

  • 3.65.140.161

  • 3.123.244.32

  • 18.157.121.27

  • 18.196.208.150

  • 18.197.252.122

  • 23.96.58.54

  • 34.212.49.37

  • 35.157.130.74

  • 35.158.235.163

  • 44.227.129.199

  • 44.238.198.162

  • 44.241.118.68

  • 52.10.204.120

  • 52.28.199.118

  • 52.29.186.76

  • 52.35.248.97

  • 52.59.20.237

  • 52.61.162.10

  • 52.170.251.156

  • 52.222.21.191

  • 52.222.47.65

  • 52.222.55.193

  • 96.127.64.206

  • 96.127.114.157

DMG Mori Cloud

(your-account.dmgmori-tulip.com)

  • 20.48.15.3

  • 51.105.126.240

  • 51.124.87.41

Admin Interface (Web Browser)

To use Tulip's web interface, we require the following:

Tulip Player

To download, use, and update the Tulip Player, we require the following:

Tulip Edge Devices

To use and update Tulip's hardware, we require the following:

Requirements

Outgoing access to Factory:

Outgoing access for Edge Device updates:

Outgoing access for date time synchronization:

  • ntp://[0-3].north-america.pool.ntp.org

Tulip Cloud Connector Host

To use the Tulip Cloud Connector Host to connect to a database, API, or OPC UA server, we require the following:

Tulip On Premise Connector Host

To use the self-hosted Docker Tulip Connector Host to connect to a database, API, or OPC UA server, we require the following:

Requirements

Outgoing access to Factory:

Outgoing access for updates:

Outgoing access for connections:

  • All third-party services to be connected to Tulip

Did this answer your question?