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.
Thermite PLC
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.
PumpRun := Washing; HeaterOn := Washing AND TankTemp < WashTemp;
The idea
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.
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.
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.
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
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.
Want to see it? Ask for a live session and bring your own agent.
Ask for a live demoYouThe 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.
Connectivity
Four native remote-I/O paths and a separate supervisory gateway are implemented in current Thermite PLC source.
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.
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 needsUnder the surface
// 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
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.
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.
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.
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.
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