Codoverse
Under training · pilot access

The native model for factory automation.

Codoverse writes and converts PLC control code, triages faults, and reasons over your plant’s own protocols — trained until it compiles, not until it sounds right. It deploys on your network, including fully air-gapped.

Generated · Ladder logicMotor_Start.rll
Ladder logic rung: motor start/stop/seal-in circuit with a high-temperature alarm rung001002E_StopStart_CmdMotor_RunMotor_RunHigh_TempAlarm_Out
Compiled cleanAwaiting engineer approval

Live rung — motor start/stop with seal-in

Control languages
ST · SCL · LD · FBD
Deployment
30B engineering tier + edge distill
Network
Cloud, on-prem, or air-gapped

Your engineer is still the compiler

Every general-purpose model has the same three gaps on the plant floor, and they compound.

Generic models guess at syntax

IEC 61131-3 is a low-resource language for every frontier model. They write Structured Text that reads correctly and fails at compile — because none of them were trained against a compiler.

Cloud copilots want your project files

The engineering workstation that opens your PLC project is usually the one machine your security team least wants talking to the internet. Most industrial copilots require it anyway.

Nothing checks the output before you do

Autocomplete-style suggestions reach you unverified. You become the compiler, on every line, for code that's supposed to save you time.

Verified before you see it, not after

Every draft clears a compiler and a runtime simulation on its own before it becomes something you review.

  1. 01

    Plan

    Reads the request against your project's own tags, routines and naming conventions.

  2. 02

    Generate

    Drafts control code in the target language — ST, SCL, Ladder, or FBD.

  3. 03

    Compile & simulate

    Runs the draft against a real compiler and runtime before anyone sees it.

  4. 04

    Present diff

    Shows the change as a diff against the existing routine — never a silent overwrite.

A person approves every diff. Approved changes go through your own CI to the controller. Codoverse is hard-blocked from writing to safety-related program units, and from deploying anything itself.

Request → generated diffMixer_Line3.st
Engineer’s request

“Add a 5-second startup delay and an E-stop interlock to the mixer motor on Line 3.”

Generated · Structured Text
IF NOT E_Stop AND StartCmd THEN
  StartTimer(IN := TRUE, PT := T#5s);
  IF StartTimer.Q THEN
    MotorRun := TRUE;
  END_IF;
ELSE
  StartTimer(IN := FALSE);
  MotorRun := FALSE;
END_IF;
Compiled clean · 0 errorsSimulated 1,200 cyclesDiff ready for review

A model, not a wrapper around one

Most industrial copilots are a chat window in front of a general-purpose model. Codoverse is trained on the thing it's supposed to be good at.

Generic AI layer
Codoverse
The model
A general-purpose LLM pointed at your documentation.
Trained from the ground up on verified, compiled control code.
Verification
Trusts its first answer. You find the compile error.
Every training sample compiled. Every draft is checked before you see it.
Deployment
Cloud-hosted, with local as an afterthought — if offered at all.
Built to run fully air-gapped from day one, on your own hardware.
What it knows
Your manuals and support tickets, retrieved on request.
Your tags, your alarm history, your own project's conventions.

Nothing here touches your controllers on its own

The question every plant asks first, answered before you have to ask it.

Your data stays on your site

Codoverse runs on your network — cloud, on-prem, or fully air-gapped. Project files never have to leave the building for the model to read them.

A human commits every change

Codoverse drafts a diff. It never writes to a live controller and is hard-blocked from safety-related program units, regardless of deployment mode.

Built for zone-and-conduit thinking

Architected in alignment with IEC 61508 lifecycle practice and IEC 62443 network segmentation — designed to sit cleanly inside an OT security model your team already runs.

Codoverse is pre-certification. “Aligned with” and “architected for” describe design intent, not a claim of formal certification against IEC 61508 or IEC 62443 by an accredited body.

Talk to us about a pilot

Not a waitlist. Tell us the problem and we'll tell you honestly whether Codoverse is ready for it.