Skip to content
Thermite SCADA
Edge & Redundancy

Local gateways and active/standby deployment, with redundancy included.

Thermite SCADA collects local device data, serves browser screens, shares live tags between gateways, and runs fenced active/standby pairs. Redundancy is included in the platform licence.

Edge profile

The gateway runtime near your equipment.

Run the gateway near your equipment to collect field data and serve local screens. Remote tag providers share live project values with other gateways.

  • Use the same gateway binary at the edge and in the plant.
  • Run directly or use the supplied Docker build.
  • Record local history in configured PostgreSQL storage.
  • Map configured MQTT tags to broker topics for reads and writes.
Field I/O Thermite SCADA local gateway Plant Thermite SCADA API client HTTP · WebSocket live tags
profile
edge · same binary
history buffer
bounded memory
uplink
live project tags
Data and connection behavior

Local recording and live remote access.

The historian records to configured PostgreSQL storage and temporarily retains failed writes in bounded memory. Alarm transitions have a local file journal. Remote tags and forwarded writes use live gateway connections.

Local alarm journal

Alarm transitions are recorded in the gateway’s JSON-lines journal.

Bounded history buffer

Pending samples use a bounded memory buffer during database interruptions. New samples replace the oldest when the buffer fills.

Live tag subscriptions

Remote providers consume selected tag prefixes from configured peer projects.

Forwarded writes

Forwarded writes carry expiry deadlines and execute while the owning gateway is reachable.

Hub-and-edge

A gateway can consume live tags from peers.

Configure remote providers to expose selected live tag prefixes from peer projects in a consuming project. Each gateway retains its own deployed configuration and local screens; deploy source and access settings at each site.

cell-1 cell-2 cell-3 Thermite SCADA live tag consumer Plant ops Historian edge gateways
PLC bus Thermite SCADA primary Thermite SCADA standby Operators Historian replication
Redundant pair

Active / standby, included.

Run a fenced active/standby pair with matching project and gateway configuration on both nodes. Use a stable client endpoint with session handling for node changes.

Fencing

Fences govern promotion to active. A node demotes when it loses authority.

Arbiter

Add an independent arbiter to your quorum fence.

Historian write lease

Choose shared history with a write lease, or record history per node.

Client failover

Browser clients reconnect to their current origin. Provide endpoint routing and session handling for node changes.

Licensing

Redundancy is part of your platform license.

Active/standby pairing is a feature of the platform you already licensed. There's no redundancy uplift, no separate license for the standby that mirrors the same modules, and no surprise major-version upgrade bill on either node with active support. The license is unlimited — standbys, edge nodes, and every other server run on the one you already have.

Tell us your downtime tolerance.

We'll work through single gateways, redundant pairs, hub-and-edge, and DMZ designs with you.