Industrial apps on live plant data, built without code.

It connects to what is already on the floor

Six ways in, and the plant keeps its own historian.

Tags are browsed from the source's own address space and mapped under names your people already use. Nothing is copied into the platform that the plant already keeps somewhere better.

• OPC UAPLCs and SCADA servers, browsed by their own address space. Signed and encrypted, trusted by certificate thumbprint.opc.tcp://plc-line3:4840 · Basic256Sha256
• Industrial Edge / IIHTags and the history the plant already keeps. The past is read from IIH, never duplicated locally.Asset_Line3.Aspect_Energy.Power_kW
• MQTTBrokers by topic, in and out — a whole JSON payload or one pointer into it.plant/line3/energy#/power/kw
• Modbus TCPRegisters mapped once from the meter's own map, then named. Word order, scaling and status bits handled.40011 · float32 · ABCD · kW
• SQL ServerThe MES and the databases beside it. One SELECT, read-only, in a transaction that rolls back.SELECT … FROM dbo.OpenOrders
• RESTAnything else with a web address, polled and pointed into.GET /rest/v1/plant → /line3/output_t

Live values are read through the server, never by the browser: a certificate, a password or a PLC address is never handed to a screen on the floor. Every write is checked against the operator's role and written to an audit log the database itself will not let anyone edit.

Built by choosing, not scripting

The people who know the process build it themselves.

Screens, by dragging

Forty widgets — tables, forms, charts, galleries, pop-ups, signatures, gauges — arranged on a grid against live data. What an operator sees is what their role allows, and the same screen scales up to a wall display or stacks down onto a phone.

• Live while you design. The canvas is the real renderer on real values, not a preview.
• Checked before it ships. Every binding and every action is verified; a broken app cannot be published.
• Versioned. Publish, roll back, and export the whole app as one file to carry to another line.

Logic that runs on the server

Flows fire on a schedule, on a value crossing a limit, on a button, or on a web hook. They read history, write tags back to the PLC where that is allowed, add rows, publish to MQTT, send e-mail and call web services — and every run is logged with what it did.

• Not in the browser. Flows run on the edge server, so they keep working when nobody is logged in.
• Rehearsable. Simulate a flow and watch every node's value before it ever touches the plant.
• Accountable. A tag write carries the name of whoever published the app, and lands in the audit log.

Data out, on a schedule

Export jobs built by choosing: which tags, which rows, which window — as a spreadsheet, CSV or JSON, to a file store, an e-mail, a web address, or straight back into a SQL Server table. At 06:05 every morning, or from a button, or from a flow.

• Fenced by IT. Each destination sends only inside the boundary its admin set — one folder, one domain, one table.
• Retried. A destination that fails is tried again after 1, 5 and 15 minutes, and every delivery is audited.
• Read by your own tools. A read-only data API with per-app tokens for Power BI, Grafana or a script.

Three real apps, in order of ambition

Start with an afternoon's work. Finish running the line.

These are not mock-ups. All three run on the demonstration server, on simulated plant data, and each does something the one before it cannot.

Rung onean afternoon

Line 3 wall board

One screen at the end of the line: is it running, how fast, how hot, how much power. Six tags, no database, no logic — every part of it placed by dragging a widget and picking a tag.

1 SCREEN6 TAGS0 FLOWS

Rung twoa few days

Maintenance rounds

The clipboard round, on a tablet: a route of checkpoints, a reading and a photograph at each one, a signature, faults e-mailed the same afternoon and the week filed as a spreadsheet on Monday. It needs nothing from the automation — which is why it is usually the first thing a plant buys.

5 SCREENS2 TABLES1 FLOWWEEKLY EXPORT

Rung threethe full system

Production cockpit

The line run from one app. The order comes from the MES, the drive takes its setpoint, stops log themselves from the running signal, quality and scrap are recorded on the floor, and the day is filed to storage, to an inbox, and back into the MES. OEE is worked out by the app in its own SQL — so the figure on the wall and the figure in the spreadsheet are the same figure.

8 SCREENS4 TABLES4 FLOWS5 PROTOCOLS2 EXPORT JOBS

And it is a plant's to run

Built to be handed to IT, not to us.

• INSTALLOne file, minutesThe release carries the platform and everything it runs on, so the server needs no internet. HTTPS from your own certificate, or a self-signed one to start.
• BACK UPEvery night, encryptedRestored onto a second server with apps, data, connections and trusted certificates intact — which is also how you move to new hardware.
• UPGRADERehearsed, then reversed if wrongThe platform tries the upgrade on a copy of the data first, switches, checks itself against the backup it just took, and puts the old release back if anything is missing.
• WATCHIt tells you firstA connection down, an export failed, a disk filling or a certificate expiring reaches the admins by e-mail — and your own monitoring reads the same figures at /metrics.

Price

Bought once, per server.

A licence is a small signed file you install on the server. There is no licence server to reach, nothing phones home, and no dongle — because a plant network usually has no way out, and shouldn't need one.