Products
The TameChaos ecosystem
Studio is the experimental design system. Field takes the same core to the floor on Android. The edge runs what you designed, and the cloud oversees your fleet. Four distinct products on one shared core — adopt one or all, in any order.
The products
Four products, one shared core
Studio leads because it's where most people start — that's emphasis, not a sequence. Each product stands on its own and has its own page; begin with whichever fits your work.

Studio
The experimental design system: model a real-world system, draft its control topology, mock up operator HMIs, and produce industrial-quality documentation. Standalone by design — the edge is optional.
DesignPre-release
Mac · iPad · iPhone · Windows

Field
Studio for the field, on hardware that survives it. Field authors a real Studio project on site — no server, no Mac, no network — then adds an optional Edge companion, on rugged Android hardware.
Design · in the fieldEarly access
Android
Where to start
Four entry points, not four steps. There is no step 1 — you can stay in one product indefinitely.
Platforms
One core, five platforms
Studio runs on Mac, iPad, iPhone, and Windows. Field is the same core on Android, plus capability the other platforms don't have — which is why it's its own product, not a fifth Studio build.
| Capability | MacStudio | iPadStudio | iPhoneStudio | WindowsStudio | AndroidField |
|---|---|---|---|---|---|
| Full authoringCanvas topology editing, HMI mockups, and documentation export on a large screen. | Yes | Yes | No | Yes | No |
| Field captureThe same project navigator in compact form, with node-first capture — photo, evidence, and provenance — straight into the diagram. | No | No | Yes | No | Yes |
| Edge companionLive runs, anomalies, journals, and role-gated run control when a project has a paired edge. | No | No | No | No | Yes |
Studio and Field are pre-release; this is the platform scope of the first release. A Studio project is the same project on every platform — you can start it on a phone in a plant and finish it on a workstation.
How they fit
Peers, not a pipeline
Field capture authors straight into a Studio project, and Studio can export to the edge — but it isn't a single left-to-right sequence. Three facts let you adopt one product or all of them, in any order:
One shared core, distinct products
Studio and Field are distinct products built on the same design core and the same project format — and both stand alone, with no server or network required. Field adds what the other platforms don’t have: an optional Edge companion, and rugged hardware.
The edge is authoritative
The edge server owns execution — it runs your experiments. The cloud only observes and aggregates; it never starts, stops, or commands a run.
Your fleet, your data
Aggregation and model improvement are scoped to a single owner's fleet. Your fleet learns only from its own operation — no cross-tenant data or model sharing.
Why Studio leads, and what it doesn't mean
Studio comes first because it's the most common starting point — the edge is reordered in sequence, not in importance, and it remains the authoritative runtime. Studio owns design-time authority; the runtime owns execution; the two meet at a project package that describes itself. A design never overrules what a running system measures.
Start anywhere
Adopt one product or the whole ecosystem — in whatever order fits your work. This is the marketing front door; the platform lives in the app.

