A single workbench for industrial automation — 3D wiring, machine simulation, and PLC & robot programming on your own hardware. It is not finished and not downloadable yet. The lessons below, however, are free and available right now.
Status: Arsyn is pre-release software. Nothing is downloadable yet and no release date is announced. See exactly what is and is not built before you read any further.
What it is for
Building a machine means moving the same information between a CAD tool, an electrical package, a PLC IDE and a simulator by hand, four times over. Arsyn is an attempt to keep it in one model instead. Items marked planned below are not built yet.
Import STL assemblies, build the kinematic chain with local reference frames, and draw wires between component pins in the 3D scene. Auto-wiring and physical cable-tray routing are planned, not built.
Zone and token-based flow simulation over the assembled scene. It does not write back to live PLC variables today — hardware-in-the-loop is planned, not built.
Ars, a typed automation language, compiles to an intermediate representation that vendor backends read. The language and compiler front-end work; the vendor backends do not yet.
Planned, not built. The intent is a locally-run model (Ollama) that reads your machine structure with no network calls. Treat it as a roadmap item, nothing more.
BOMs and wiring diagrams generated from the project model rather than maintained by hand. Partially working — the document organizer and attachments are in, full export is not.
The core is closed and stays closed. The module SDK, the .arsyn file format and the Ars language are what get published, so your data and your modules are not hostage to this project surviving.
The obvious objections
If you build machines for a living, these are the first questions you would ask. Here are the honest answers.
Then Arsyn cannot be your deliverable tool, today or soon. That is a contractual and insurance constraint, not a tooling preference, and no amount of unified workflow dissolves it. TIA/Codesys round-trip is on the roadmap and is genuinely hard; until it exists and is trusted, Arsyn is a design and simulation aid that sits beside your vendor toolchain, not a replacement for it.
For production work right now, you should. They are mature, supported, and accepted by your customers. RoboDK does robot simulation and offline programming far better than Arsyn does. EPLAN does electrical documentation to a standard Arsyn will not match for years. The only thing Arsyn offers is one model instead of several, and that is worth nothing until the model is complete enough to matter.
A fair suspicion, and I cannot disprove a future intention. What I can do is be precise: the desktop application is free and closed-source, and there is no open-source promise to walk back later, because none was made. The published parts — file format, module SDK, language — are chosen so that if the pricing ever turns hostile, your projects and your modules survive it.
One person, working on it alone. That is a real risk factor for anything you would put near live equipment, and it is why the current honest recommendation is: read the lessons, watch the build log, and do not put pre-release software in the path of anything that can hurt someone.
Free lessons
Whatever happens to the software, this part already works: structured lessons, challenges and live simulators, at no cost and with no account.
Get in Touch
Project inquiry, partnership, or just a technical question — reach out directly. I reply within 24 hours.
// Have a spec? No spec? // Either way — let's start.