Liberate industrial code from proprietary silos.
2ot is the IEC 61131-3 execution and tooling layer behind the workflow you choose. Automation scripts and LLM agents invoke a stable router for fast diagnostics, transpilation, protocol services and Siemens TIA, CODESYS or Beckhoff TwinCAT operations; engineers stay in the harness and engineering environment they prefer.
The fast loop stays in the compiler
2ot check --fast delivers compiler-only diagnostics without waiting for a vendor IDE to start. Vendor-aligned mappings and structured enrichments let scripts, CI jobs and LLM harnesses make useful next-step decisions with very low feedback latency.
The vendor runtime stays behind the router
Once a workspace is configured, common operations such as pull, push and build can infer the active vendor. The calling harness keeps using 2ot; dedicated TIA, CODESYS and TwinCAT runtimes own the vendor-specific work behind it.
Four pillars of the ecosystem
The 2ot CLI
A stable workspace-aware execution contract for scripts, agents, protocol services and vendor-specific operations.
Fast compiler feedback
Compiler-only diagnostics with vendor-aligned mapping and structured context for automated repair loops.
Vendor runtimes
Route the same harness workflow into Siemens TIA Portal, Beckhoff TwinCAT and CODESYS.
Universal transpilation
Analyze, lower and emit IEC 61131-3 Structured Text across supported targets through one compiler pipeline.
Bring the harness you already want to use
The 2ot router can describe its schema-emitting command surface for dynamic MCP discovery. An internal tool, automation script or LLM harness can therefore invoke the same routed operations and consume structured results. The engineer chooses the interface and controls the workflow; 2ot stays underneath it as the execution layer.
Product surfaces
The gateway keeps these capabilities independently deployable while exposing one stable execution surface to automation scripts, protocol clients and LLM harnesses.
| Surface | Role |
|---|---|
| gateway | Workspace-aware routing, executable discovery and schema normalization for calling harnesses. |
| compiler | Parsing, semantic analysis, fast diagnostics, lowering and target emission. |
| diagnostics | Vendor-aligned errors with structured context for automation and LLM-assisted repair. |
| agents | CLI and MCP integration over the same routed command model. |
| lsp | Compiler-backed language operations exposed through the Language Server Protocol. |
| testing | Multi-vendor and runtime-equivalence verification infrastructure. |
| vendor runtimes | Isolated Siemens TIA, CODESYS and TwinCAT automation behind the gateway. |
Browse the public knowledge portal
Provider bundles, callables, semantic rules, telemetry mappings and schemas are browsable and searchable as part of the public 2ot knowledge surface.
Open knowledge portal →Keep Siemens-derived API knowledge local
2ot can build a version-aware Siemens PublicAPI graph from licensed inputs on a developer machine. The website documents that pipeline without publishing the proprietary corpus.
How the local graph works →