← The Thermite family

Thermite PLC

Machine control. Open to your agent.

An AI-native soft PLC, written in Rust. IEC 61131-3 Structured Text and plain configuration files, with a command-line toolchain your own AI agent can drive from build to live trace.

One scan
Software-defined industrial control

The idea

A controller your tools can reach.

Programs are IEC 61131-3 Structured Text. Tasks and I/O mapping are plain configuration files. The whole project lives in Git and compiles to a versioned image for a separate runtime. Every engineering step is a command, so your agent can check, build, simulate, monitor, and trace with the same tools your engineers use.

Build from the command line.

Check the project, compile it to a versioned image, download it, and run it without opening a window. Compiler errors carry stable codes, and a language server pins them to the source line.

Inspect without taking control.

Read mode, scan time and jitter, faults, device health, and active forces from a running controller. Stream live values as JSON, capture scan-by-scan traces, and upload the running image to confirm what is deployed.

Simulate before hardware.

A separate simulation runtime cannot reach real I/O, so logic can be exercised there first. On a real controller, downloads, run and stop, and forces need the single control token: one session holds it at a time.

AI-native by design

Bring your own agent.

Thermite PLC has no built-in AI assistant, by design. Your agent works with the Structured Text and configuration files, Git, and the thermite command line: the same tools your engineers use to build, download, monitor, and trace. No plugin, skill, or MCP server is needed to begin. You choose the agent and the model.

Read
Programs, I/O mapping, controller status, faults, live values, traces
Change
Logic and configuration, as edits to text files
Check
Compiler diagnostics with stable codes; a simulation runtime isolated from real I/O
Ship
A versioned image, downloaded by the session holding the control token

Want to see it? Ask for a live session and bring your own agent.

Ask for a live demo
AGENT SESSION

YouThe parts washer aborts its wash cycle a few times a shift, and nobody can catch it happening. Find out why.

AgentI’ll check the controller, then trace the abort scan by scan.

Run thermite status --host washer:7700running, no faults, devices connected

Read programs/wash.stCycleAbort latches when LevelOk drops

Run thermite trace record LevelOk PumpRun CycleAbort --task main --trigger "CycleAbort rising" --pre 1s --post 1s --json --host washer:7700armed; one abort captured, 1,000 scans recorded

AgentFound it. LevelOk drops for three scans, 6 ms, while the pump is running: the level switch chatters. The abort latches on a single-scan drop.

Edit programs/wash.stLevelOk must stay low for 500 ms before aborting

Write sim/inputs/level_ok.ststarts a wash, then replays the 6 ms dropout every five seconds

Edit io/rio.tomllevel input bound to the simulation script

Run thermite connect-sim .local simulation runtime, no real I/O: downloaded and running

Run thermite trace record LevelOk PumpRun CycleAbort --task main --trigger "LevelOk falling" --pre 1s --post 1s --jsondropout captured: the pump keeps running, no abort

AgentThe fix holds in simulation. Nothing has been downloaded to the machine; the diff is ready for your review.

YouGood catch. I’ll review it and download at the next break.

Illustrative walkthrough with an example project and values, in the style of a Claude Code session. Any agent that can edit files and run commands can work the same way.

Connectivity

More ways to connect.

Four native remote-I/O paths and a separate supervisory gateway are implemented in current Thermite PLC source.

Modbus TCP
Native polled client/master for remote I/O.
EtherCAT
Opt-in Linux cyclic master. Physical NIC and slave qualification varies by application.
PROFINET
Opt-in Linux controller with DCP, bounded GSDML support, and RT_CLASS_1 cyclic I/O. IRT, PROFIsafe, and certification are outside this scope.
EtherNet/IP
Opt-in Linux Class 1 exclusive-owner scanner for fixed assemblies in development. The supported profile uses unicast; other profiles and multicast need further work.
OPC UA
A northbound server in a separate gateway daemon for browsing, reading, subscribing to runtime tags, and writing setpoints.

A growing protocol library.

Siemens S7, BACnet/IP, and MQTT/Sparkplug B are companion integration libraries. They provide a foundation for supervisory services, not native deterministic PLC I/O drivers or dynamically installable plugins.

Confirm build features, device profiles, and hardware qualification for the selected deployment.

Built around your equipment.

Need another protocol? We can develop additional drivers and integrations around your equipment and process. Talk with us about the devices, data, and timing your application needs.

Discuss your protocol needs

Under the surface

Logic you can follow.

Foundation
Rust soft PLC
Programming
IEC 61131-3 Structured Text
Project format
Plain text: Structured Text and TOML
Agent access
Files, Git, command line, JSON value streams, traces
Field I/O
Modbus TCP, EtherCAT, PROFINET, EtherNet/IP
Supervisory integration
Separate OPC UA server gateway
Scheduling
Soft real-time runtime
programs/wash.st
// Start a wash when the operator asks and the tank is full.
IF StartButton AND LevelOk AND NOT CycleAbort THEN
    Washing := TRUE;
END_IF;

// Abort if the level stays low for half a second, not on a flicker.
LevelLost(IN := Washing AND NOT LevelOk, PT := T#500ms);
IF LevelLost.Q THEN
    CycleAbort := TRUE;
ELSIF ResetButton THEN
    CycleAbort := FALSE;
END_IF;

// Stop when the ten minutes are up, or on an abort.
WashTimer(IN := Washing, PT := T#10m);
IF WashTimer.Q OR CycleAbort THEN
    Washing := FALSE;
END_IF;

// Run the pump while washing, and heat until the water is warm.
PumpRun  := Washing;
HeaterOn := Washing AND TankTemp < WashTemp;

Fair questions

Asked plainly.

Is there an AI assistant built in?

No, and that is deliberate. Instead of adding an assistant to the product, we made the product itself workable by the agent you already use: its files and its command line.

Which AI agents does it work with?

Any agent that can read and edit files, run commands, and make network requests. Nothing Thermite-specific is installed in the agent. How well a given model handles controls work is yours to evaluate, and we can help with that.

Is it safe to let an agent near a controller?

Start in simulation, on a separate runtime that cannot reach real I/O. On a real controller, reading does not take control; downloads, run and stop, and forces need the single control token. Safety functions stay in your safety system.

Do we have to use AI?

No. Engineers work with the same files, commands, and interfaces directly. An agent is a way to move faster on a system your team understands. It is not a requirement for running one.

What happens to our system if Blackett Applied is not around?

It keeps running. The controller executes the image you built and does not depend on any service of ours. Your programs and their history stay in your own repository, as standard IEC 61131-3 Structured Text and plain configuration files. Thermite PLC is proprietary software; where you need more assurance, a source-code escrow agreement can be arranged.

Your next step

See it work with
your own agent.

Ask for a live demo