Skip to content
Thermite SCADA
Architectures

From local projects to live tag sharing between sites.

The Rust runtime supports single and multi-project gateways, configured active/standby pairs, and live tag sharing between peers. Deploy matching source to redundant nodes and plan network access for each site — all on one unlimited license.

PLC Drives Thermite SCADA gateway Operators Historian
PLC Drives Thermite SCADA gateway Operators Historian
Topology

Single gateway

One Thermite SCADA gateway connects to field devices, runs the historian, hosts HMI, and exposes APIs.

Good fit

Pilot deployments, single machines, lab cells, and small plants where a single point of operation is acceptable.

Deployment

For a redundant pair, plan matching configuration, fencing, and a stable client endpoint.

line-a lab-1 utility Thermite SCADA gateway /p/line-a/ /p/lab-1/ /p/utility/ project scopes one URL per project
Topology

Multi-project gateway

Host several projects on one gateway. Each has its own URL, role bindings, screens, and tag namespace.

Good fit

Plants where one operations team supports several independent lines, labs, or utilities under one runtime.

Deployment

Projects share the gateway process, device connections, and database resources. Size the host for their combined workload.

PLC bus Thermite SCADA primary Thermite SCADA standby Operators Historian replication
Topology

Redundant pair

Run a fenced active/standby pair with matching configuration and a stable client endpoint.

Good fit

Production lines with downtime cost. Redundancy is part of the platform, not a separate paid module.

Deployment

Use quorum or historian-lease fencing with client routing and session handling for node changes.

Field I/O Thermite SCADA local gateway Plant Thermite SCADA API client HTTP · WebSocket live tags
Topology

Local edge gateway

A gateway near the equipment collects device values, serves local screens, and can expose live project tags to configured peers.

Good fit

Cells, skids, and remote sites that need local operation.

cell-1 cell-2 cell-3 Thermite SCADA live tag consumer Plant ops Historian edge gateways
Topology

Hub-and-edge

A consuming gateway subscribes to selected live tag prefixes from configured peer projects through the gateway mesh.

Good fit

Operations teams that need screens using live tags from several gateways. Each site retains its own deployed configuration.

Thermite SCADA plant gateway Broker external MQTT/TLS IT systems SQL · BI OT zone DMZ IT zone
Topology

DMZ broker

Map MQTT topics to your broker in a segmented network. You control firewalls, broker permissions, and TLS.

Good fit

Sites with an OT/IT boundary managed through your firewalls, proxies, and brokers. Thermite connects as an MQTT client.

Tag consumer Thermite SCADA Site A gateway Site B gateway Site C gateway edge devices · operators
Topology

Multi-site enterprise

Gateways across plants can share selected live project tags with a consuming gateway. Deploy each site’s projects and access configuration locally.

Good fit

Enterprise rollouts that need standardization without forcing every site onto one global gateway.

Deployment targets

Where Thermite SCADA runs.

Run your gateway directly on Windows or Linux, or build the supplied Docker image.

Linux

Run the gateway directly with your site directory.

Windows

Run thermite-server.exe with a site directory containing gateway configuration and published projects.

Docker build

The supplied Dockerfile builds the gateway and CLI. Mount the site directory into the container.

Site configuration

Keep devices, databases, feature flags, and gateway authentication in config/server.toml.

Project publication

Publish source with the CLI. The gateway serves snapshots from the site’s published store.

OT / IT boundary

Connect across your OT/IT boundary.

Use your firewalls, proxies, and brokers to segment the network. Thermite SCADA connects to MQTT brokers and exposes project HTTP and WebSocket APIs. Your network configuration controls access.

  • OT-side gateway runs drivers, historian, and HMI for plant operators.
  • Configure MQTT topic mappings and permissions on your external broker.
  • Permit IT consumers through the broker or selected gateway interfaces.
  • Keep private keys and live credentials in secured deployment configuration outside Git.
Thermite SCADA plant gateway Broker external MQTT/TLS IT systems SQL · BI OT zone DMZ IT zone

Sketching a deployment? Bring it to us.

We'll map your sites, networks, devices, and redundancy targets to a Thermite SCADA deployment.