By PLC engineers. For PLC engineers.

Build the logic. Prove the flow.

v0.1.1 · Pilot-ready software

From a warehouse drawing to PLC logic and a deterministic simulation. Find routing errors, test fault scenarios, and inspect the evidence before going on site.

Explore the sample plant Import your layout

Deterministic simulation core. Optional AI assistance. Engineering decisions stay with you.

01CAD

02Site model

03PLC logic

04Simulation

05Evidence

Sorter reference layout

STRUCTURED TEXT

(* Reference control pattern *)
IF PE_IN AND NOT JAM THEN
    CONVEYOR_RUN := TRUE;
ELSE
    CONVEYOR_RUN := FALSE;
END_IF;

Inspect and compile your program in Studio.

SCENARIO EVIDENCE

Criteria → observed results → repeatability digest

A digest helps check reproducibility. It is not a safety certificate.

A synthetic layout, not a live PLC connection. Open Studio to run actual scenarios.

START WITH THE TASK AT HAND

One plant. Three working views.

The same model and program follow you through the engineering workflow.

Layout

Import DXF or Site JSON, inspect the topology, and build the equipment model.

Open view

Logic

Edit Structured Text, compile it, and watch the simulated I/O.

Open view

Verify

Run acceptance scenarios, investigate failures, and export the result.

Open view

Or start with a ready-made example →

A TRACEABLE ENGINEERING WORKFLOW

Keep every step connected.

Geometry, control logic, simulation and evidence belong to one engineering process.

Start with the layout you have.

Import DXF or Ambar Site JSON in the browser. Review the resulting equipment and topology before moving on.

WORKING ARTIFACT

Input: .dxf / .json

DWG conversion uses the separate CAD gateway. Customer drawings still need an import review.

Continue in Studio →

FROM OBSERVATION TO A DECISION

Results you can inspect.

A moving 3D scene is only the start. Verification connects an explicit scenario to measurable outcomes.

01
Define the scenario
Set the duration, input conditions and acceptance criteria.
02
Inspect what happened
Review throughput, misroutes, stalls, timing and final values.
03
Check repeatability
Compare deterministic re-runs and retain the evidence digest.

Open verification view

What the report connectsSCENARIO → REPORT

Scenario inputsConditions, parameters and seed

Acceptance criteriaExpected behavior and thresholds

Observed resultsPass/fail, measurements and events

ReproducibilityConfiguration and evidence digest

Report structure shown for illustration. Actual results are generated in Studio.

A BOUNDED FIRST PROJECT

Bring one warehouse area.

Agree on the model scope, PLC workflow and acceptance scenarios before committing to a wider rollout.

Scope, schedule and commercial terms are proposals until agreed.

Local core: Model, simulation and verification can run locally without an AI service.
Optional AI: Agent features may send selected model, code and tool context to a configured external provider.
Lab integrations: DWG, OPC UA and S7 workflows require their gateways and the relevant engineering access.

Tools and details, when you need them.

Keep the main journey focused. Open the specialist tools and practical details below.

Examples & engineering tools

Choose a starting scene or open a specific tool without running it automatically.

Flagship sorter + pick station + AS/RS Barcode sorter example Mini-load AS/RS example Equipment builder I/O, forcing & simulation faults Performance & sizing PLC Academy · 10 lessons Agent tools

Available exports: ST, SCL, PLCopen XML, GLB, Site JSON, IFC, AutomationML and protocol maps. IFC and AutomationML are exports, not browser import formats.

Local quick start

TERMINAL

pip install -e ".[all]"
ambar demo sorter --open

Current capability & readiness

Available in the core

Deterministic simulation, ST runtime, scenario verification, Modbus TCP and browser 3D inspection.

Optional components

DXF parsing, agent/MCP services, DWG and OT gateways depend on the selected installation and configuration.

Review in your environment

Real PLC/tool interoperability, foreign DWG drawings and customer acceptance need project-specific validation.

The repository includes reference scenarios, internal benchmark results and test evidence. These are not a customer success guarantee.

How agent assistance fits

The engineering workflow can be used manually. Optional agent tools help inspect models, draft PLC code or run checks. Review the generated changes and the actual verification output.

No agent is running on this page. This page does not send project data to an AI service.

Open agent tools →

Illustrative opportunity estimate

Explore your own assumptions. This is arithmetic based on the values you enter, not a forecast or a price quote.

Currency (no conversion)Site days avoided / projectCost / site dayProjects / yearPeople in the site teamYour estimated annual software costEnter a quote or your own assumption. No list price is implied.

Opportunity / project: —
Opportunity / year: —
3-year net estimate: —
Simple payback: —
Site team hours / year: —

Assumptions: 8 hours per site day; the same project saving each year; no discounting, tax or currency conversion. Negative net outcomes remain visible.

Appearance & interface preferences

Use the paper or graphite interface, or retain a legacy theme preference. The engineering workflow is the same.

The interface uses locally hosted Inter and JetBrains Mono for code and measurements.

Typeface license →

Pilot & commercial notes

AjantikPLC (Ambar) is commercial, pilot-ready software. Repository prices and proposals are drafts for discussion, not a final offer. The pilot brief helps describe a scope; it does not place an order.