Connect SCADA data to your IT systems.
Thermite SCADA exposes project tags, current alarms, and history through HTTP and WebSocket APIs. PostgreSQL queries and transactions connect application data to databases. With authentication on, the gateway checks project permissions for tag writes.
One server, several ways to connect.
REST API
AvailableRead your project tags, current alarms, and history as JSON. HTTP writes use session cookies and CSRF tokens.
WebSocket subscriptions
AvailableLive tag updates and alarm events use separate WebSocket endpoints with structured messages. Terminate browser TLS at your reverse proxy.
SQL connections
AvailablePostgreSQL connection pools shared by configured named queries and transaction groups.
Named queries
AvailableServer-side SQL templates with required-parameter and value-type checks, executed through the gateway administrator API.
Transaction groups
AvailableWrite tag values to PostgreSQL and read database values into project tags, using tag-change triggers. Database reads update the gateway’s tag cache.
Webhooks
AvailableOutbound HTTP alarm-notification webhooks with retries and optional HMAC signing.
Project lifecycle CLI
AvailableCreate projects, publish production snapshots, and manage named drafts with the thermite command line.
Browser API
AvailableThe supplied thermite.js library connects screens to project tags, tag writes, and history queries.
Read a tag. Subscribe. Query. Write.
GET /p/press-line-a/api/tags/hydraulics/head_pressure
{
"type": "tag",
"path": "hydraulics/head_pressure",
"value": {
"value": 1820.4,
"quality": "good",
"timestamp": "2026-04-27T20:14:08Z"
}
}
# Tag WebSocket endpoint and example messages /p/press-line-a/api/ws/tags {"type":"subscribe","tags":["hydraulics/head_pressure"]} {"type":"update","values":{"hydraulics/head_pressure":{ "value":1820.4,"quality":"good", "timestamp":"2026-04-27T20:14:08Z" }}} # Alarm WebSocket endpoint /p/press-line-a/api/ws/alarms
# Example configured query, on the administrator API
POST /api/queries/shift-summary/execute
Content-Type: application/json
{"parameters":{"shift":"A","date":"2026-04-27"}}
{"query":"shift-summary","row_count":0,"rows":[]}
# Project session and CSRF token
PUT /p/press-line-a/api/tags/recipes/active_id
Content-Type: application/json
X-CSRF-Token: <project session CSRF token>
Cookie: <project session cookie>
{"value":"HX-204"}
{"ok":true}
Sessions, write permissions, and runtime audit records.
HTTP writes use scoped session cookies and matching X-CSRF-Token headers. WebSockets use single-use tickets. The audit log records runtime writes with actor, project, target, submitted value, and outcome.
Project requests use project sessions; named queries use the administrator session.
Browser and HTTP tag writes use the same project permission check.
HTTP writes require a matching CSRF token from the session.
The audit log records runtime events in JSON lines and, when configured, PostgreSQL.
Need a specific integration?
Bring your ERP, MES, BI, IT historian, or ticketing requirements. We'll work through the integration with you.