Docs
How the Singularity is deployed, how data physically travels from a plant floor into it, and where that data sits once it arrives.
The Singularity runs in the cloud on AWS. It is multi-tenant, and it is delivered in the browser. A user needs a browser and an account.
One component runs on customer premises: an on-site MQTT client. That client is the entire mode40 footprint inside the plant. The modules, the data models, and the storage all run in the mode40 cloud.
None of these has ever been built for a customer, and none is available today. If a mandate requires the platform itself to run inside your own infrastructure or inside a disconnected network, the Singularity does not meet it. That is worth settling in the first conversation.
Data leaves the plant floor along one path:
The connection is outbound from your network. The site opens the connection to mode40. No inbound hole in your firewall is required for the platform to receive data, and there is no inbound path to punch through a NAT boundary. TLS protects the MQTT link, and the browser session runs over HTTPS.
The on-site MQTT client is the customer’s to run and configure. It has to publish every device that reports, and the data it publishes has to match the data model agreed for that machine type.
Databases sit in private VPCs. They are not exposed to the internet, and they are reachable only by the platform backend, which authenticates with a JWT. A browser session never talks to a database directly.
Data is encrypted in transit and at rest. Key management runs on AWS KMS, with tenant-specific keys available as an option. All communication runs on TLS 1.2 or higher. Security and governance covers identity, audit logging, data ownership, and the certification status in full.
The AWS region is chosen per customer at onboarding.
Data does not move across a border unless that movement is explicitly configured. The region is a deployment decision made once, at the start, so it belongs on the implementation checklist rather than in a later change request.
MQTT off the floor is one input. The Integration Hub is the Foundational Module that handles the rest of the systems an operation already runs.
It speaks REST, SOAP, OPC UA, MQTT, and file-based protocols to source systems.
It reaches the main business software for orders, inventory, and finance (ERP), plant control systems (SCADA), machine controllers (PLCs), connected sensors and IoT devices, quality platforms, scheduling tools, and third-party cloud apps.
Every signal that arrives is schema-normalized and source-tagged, so every module downstream reads the same values and can tell which system produced each one. The Hub writes back to source where a workflow requires it. Connection health monitoring watches each connection, so a dropped feed is flagged before a module works from stale data.
How systems connect covers the Integration Hub in full.
We use cookies to understand how the site is used and to connect form submissions to earlier visits. No analytics or marketing cookies are set until you choose. Privacy Policy