The questions we hear most.

No. Koyl compiles standard Python. Anything that parses as Python 3.11 parses for Koyl. The compiler enforces a strict allowlist of supported constructs, with Python's syntax, semantics, and error messages throughout, but there is no new grammar to learn and no new file extension to adopt.

No. Koyl ingests L5X, SimaticML, and TcPOU losslessly. You can open a working project, edit it in Python, and export it back with a clean diff. Round-trip is a first-class guarantee, not a convenience.

A DSL asks your team to learn new syntax, your editors to ship new plugins, your CI to build new infrastructure, and your tests to run on a new runtime. Koyl asks none of that. Python brings the rest of software with it: version control, code review, type systems, automated tests, formatters, language servers, packaging, and the broader ecosystem any Python developer already uses. A DSL starts that ecosystem from zero.

A one-way compiler assumes you are starting a project from zero. That does not describe the installed base of Western industry. Koyl is bidirectional. Vendor files remain valid source, and Python remains valid source, and you move between them without loss.

Allen Bradley (ControlLogix, CompactLogix via L5X), Siemens (S7-1200, S7-1500 via SimaticML), and Beckhoff (TwinCAT 3 via TcPOU and tsproj). These three vendors cover the majority of Western industrial deployments. Additional targets are on the roadmap after the core three are fully hardened in the field.

The IR is a structured, serializable Pydantic model. You can inspect it, diff it, analyze it statically, and, crucially, give it to a language model as a function-calling target. Unlike an opaque compiler pipeline, Koyl's IR is a programmable surface. Build linters, migration tools, or AI agents against it.

Yes. Koyl ships an editor with the AI chat, scan-cycle simulator, and vendor parsers built in. Because the source language is standard Python, every language server, linter, formatter, and testing tool the wider Python community already uses works inside it. You don't switch dev-tool ecosystems; you get them tuned for industrial code.

Koyl includes a deterministic scan-cycle simulator that walks the IR. You can pin existing behavior with characterization tests, then verify changes before they go near hardware. The simulator is the same loop the chat agent uses to verify its own suggestions before showing them to you.

Yes. Readability is a requirement, not a nice-to-have. High-level framework features (state machines, timing helpers, edge detection) compile down to ordinary CASE statements, FB invocations, and boolean logic. A technician on the plant floor can open the exported L5X, SimaticML, or TcPOU in the vendor IDE and understand it without knowing Koyl exists.

Now, through the design partner program. We are onboarding ten controls teams and system integrators with hands-on access to the full toolchain.

Koyl is pronounced like "coil," after the relay coil, the symbol every ladder logic program inherits from the electromechanical controls that came before. The name is a nod to what this industry was built on, and to what it's still for.