Design-partner cohort open · Q2 2026

PLC development,
in AI's native language.

Bring your existing project. Describe the change in plain English. Koyl reads your code, applies the change, runs the simulator, and pins existing behavior in tests. Ship without fear.

Apply for Design Partner Program → See what the agent can do →
Koyl IDE · AI chat · FB_PalletStop ● live

you

Walk me through FB_PalletStop.

● assistant

Station-level pallet handler. Latches stop_arm for one cycle on a rising pallet sensor, holds station_busy until reset. Three invariants worth knowing about:

  • ● stop_arm is a one-cycle pulse, not level.
  • ● fault always zeros station_busy.
  • ● Reset is one-shot via R_TRIG.

Want me to pin those in characterization tests before we change anything?

you

Pin them, then add jam detection on S_Jam with a 500ms debounce.

● assistant

Done. Pinned the three invariants in 4 characterization tests, then added jam_detected with a 500ms TON debounce.

Re-ran the scan-cycle sim across pallet, fault, reset, and jam scenarios. All four tests pass. Invariants hold.

Diff, tests, and trace below. Approve to apply.

What the chat does

From inheriting code to shipping changes. In one chat.

Reading, documenting, refactoring, generating from a CSV, writing characterization tests, running the simulator. Work that used to live across half a dozen tools, in the chat panel of the Koyl IDE. Same project, three vendor targets across Allen Bradley, Siemens, and Beckhoff. No tool switching.

Ships today

AI chat on your project

Describe the change in plain English. The agent reads the project, applies the edit across files, runs the scan-cycle simulator, and shows you the diff with sim parity confirmed. The same chat writes the tests that prove the change is safe.

Ships today

Understand and document

Open a forty-rung legacy routine and ask what it does. The agent reads through the project, follows which function blocks call which, and explains how the routine executes scan by scan. Generate FB overviews, inline comments, or full project docs on demand.

Ships today

Refactor or generate

Ask for a refactor: split an FB, rename a tag, add a fault state. Or hand the agent a CSV IO map and have it generate the tag tables. Greenfield and brownfield, same chat.

Ships today

Test and verify before hardware

Characterization tests the agent writes by observing scan-cycle behavior, re-run after every change. Pytest, coverage, CI. All out of the box, because the source is Python.

The IDE

Editor, chat, simulator. One surface.

Drop a vendor project in. Browse it as Python. Ask the agent for changes and watch it apply diffs across files, then verify in the simulator before you see them. Export back to a vendor file when you're done. No tool switching, no copy-paste, no context lost between steps.

The Koyl IDE with a Beckhoff XPlanar 12-Tile project open. The editor shows a multi-file diff with green and red lines marking proposed changes, plus Accept / Reject / Accept All / Reject All buttons at the top. The right-hand AI chat panel shows the agent's IEC 61131-3 compliance check across the project: a category-by-category table flagging which patterns comply and which need fixing (decorators, timer scope, type casing, qualifier usage), followed by a summary of the eight specific edits being applied across three files.
● The agent runs an IEC 61131-3 compliance check across a Beckhoff XPlanar project, then applies the eight fixes for review across three files. Accept or reject each one before it lands.

1 · File tree

Vendor projects open as Python. Function blocks, routines, IO configs, and utilities sit where you'd expect them to.

2 · Editor

Standard Python. Modern editing tools work on your PLC code automatically: autocomplete, jump-to-definition, refactor.

3 · AI chat

Reads the project, applies edits across files, and verifies in the simulator before showing you the diff.

4 · Simulator, tests, and I/O

Pin existing behavior, run scenarios, inspect IO maps. The same panel the agent uses to verify itself before showing you a change.

Design Partner Program · 10 slots

Hands-on with us. Free for twelve months.

We are picking ten controls teams and system integrators to run Koyl on production projects this year. Full toolchain, direct support, and the people building it on the other end of the line.

In exchange we ask for what we cannot get any other way: production usage, candid feedback, and one quote at the end.

Who we're looking for

  • • System integrators handing off code to plants
  • • Internal controls teams maintaining mid-to-large lines
  • • OEMs shipping standardized machines across vendors

What you get

  • → Access to the Koyl IDE: editor, chat, simulator, vendor parsers, all in one surface.
  • → AI chat that reads your project, applies edits across files, and verifies them in the simulator.
  • → Round-trip compiler on Allen Bradley, Siemens, and Beckhoff. Existing projects in, vendor-native projects out.
  • → Scan-cycle simulator. Pin existing behavior, then verify the change before it leaves your machine.
  • → Universal IR: inspectable, diffable, programmable.
  • → Direct line to the people building it. No support tier.
  • → First access to new capabilities as they land.

What we ask

  • → Hands-on use on production projects, not toy ones.
  • → Honest feedback on what worked, what didn't, and what was missing.
  • → One quote we can use after launch. Names and logos are optional.
Apply → Read the trust page first ↗