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.

If this is your first time hearing about Tulip, it may be helpful to watch our 2 minute introduction video.

Networking requirements are region-specific. If you do not know which of the following regions applies to you, contact your Tulip representative. IP addresses and ranges are listed in parenthesis beside hostnames that have static IP addresses. Not all hosts have static IP addresses.

Bandwidth Requirements

Tulip is a very 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. Deployments with Machine Monitoring that are processing 1000s of events per second may require additional bandwidth, but this is easily scaled and monitored during a phased deployment.

More important than the bandwidth, however, is the stability of the connection. If the connection to the internet is intermittent (dropping off and reconnecting every few seconds for example), it will take substantially longer for a message to be passed from your computer to Tulip's servers.

A simple utility is available at https://your-account.tulip.co/networkCheck or https://your-account.dmgmori-tulip.com/networkCheck 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, however, some proxies do not support these connections and some network monitors may need to whitelist these connections. You can check your connection compatibility at: https://your-account.tulip.co/networkCheck or https://your-account.dmgmori-tulip.com/networkCheck.

North America - AWS

To access the Admin Interface in your web browser, we require:

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

To use a Tulip Gateway, we require:

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

  • Incoming access from 3.208.72.192/26

To use the self-hosted Docker Tulip Connector Host to we require:

North America - Azure

To access the Admin Interface in your web browser, we require:

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

To use a Tulip Gateway, we require:

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

  • Incoming access from 23.96.58.54, 52.170.251.156, 52.224.191.152/30

To use the self-hosted Docker Tulip Connector Host to we require:

North America - AWS GovCloud

To access the Admin Interface in your web browser, we require:

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

To use a Tulip Gateway, we require:

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

  • Incoming access from 52.61.162.10, 52.222.21.191, 52.222.47.65, 52.222.55.193, 96.127.64.206, 96.127.114.157

To use the self-hosted Docker Tulip Connector Host to we require:

Europe - AWS

To access the Admin Interface in your web browser, we require:

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

To use a Tulip Gateway, we require:

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

  • Incoming access from 3.121.68.52, 3.126.157.29, 3.127.99.196, 18.185.231.254, 18.197.252.122, 35.157.130.74, 35.158.235.163, 52.28.75.198, 52.28.199.118, 52.59.10.173

To use the self-hosted Docker Tulip Connector Host to we require:

Europe - Azure DMG Mori

To access the Admin Interface in your web browser, we require:

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

To use a Tulip Gateway, we require:

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

  • Incoming access from 51.105.126.240, 51.124.87.41

To use the self-hosted Docker Tulip Connector Host to we require:

East Asia - Azure DMG Mori

To access the Admin Interface in your web browser, we require:

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

To use a Tulip Gateway, we require:

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

  • Incoming access from 20.48.15.3

To use the self-hosted Docker Tulip Connector Host to we require:

Did this answer your question?