Connectivity setup guide
Use this guide to determine the best way to connect your data sources to Heisenware. Follow the questions below and click the links to navigate to the exact setup that fits your use case.
Last updated
Was this helpful?
Use this guide to determine the best way to connect your data sources to Heisenware. Follow the questions below and click the links to navigate to the exact setup that fits your use case.
No – If you are building an independent App that relies solely on built-in databases and does not require external connectivity, you can skip this guide and start directly with the Overview.
Yes – If your use case requires reading or writing data to an existing database, machine, IT system, scanner, API, or industrial protocol, continue to How is your Heisenware tenant hosted?.
Your connection method depends on where the Heisenware platform runs.
Self-hosted connectivity (on-premise or private cloud)
Your tenant is hosted by Heisenware in the cloud. Is your data source accessible via the public internet (such as via an API)?
Yes – If the data source is reachable via the internet, you can use our standard connectors directly.
No – If the data source resides in an isolated or local network, continue to Connecting isolated data sources.
Your tenant is hosted on-premise or in your private cloud. Is your data source accessible from the network where the platform is deployed?
Yes – If the data source is in the same network, you can use our standard connectors directly.
No – If the data source is in an isolated network segment, continue to Connecting isolated data sources.
Does Heisenware offer a standard connector for your specific data source?
Yes – If a standard connector exists, continue to Choose your Agent setup.
No – If you need to connect a custom source, you can use a Code Adapter or build a Custom Extension. These features let you wrap custom code and expose it as visual function blocks inside the platform. Alternatively, contact our support team to discuss your requirements.
To access isolated networks, you must deploy an Agent. The Agent acts as a secure, outbound-only tunnel that maps data and enables remote logic configuration. It runs locally to bridge isolated networks and buffers data via MQTTS.
What infrastructure is available in your local network?
Use the native binary to run the Agent as a highly efficient system service directly on your operating system without requiring Docker. For next steps, see the Native Agent documentation.
Deploy the Docker container for the Agent. This is the recommended approach for containerized environments on OT servers or edge devices. For next steps, see the Docker Agent documentation.
Deploy the LXC container for the Agent. This setup is suitable for specific edge devices running LXC runtimes, such as INSYS routers. For next steps, see the LXC Agent (Insys) documentation.
Last updated
Was this helpful?
Was this helpful?