Last updated June 1, 2026

Getting started

A short orientation to TameChaos — what the platform is, how the edge and cloud divide responsibility, and where to go next.

TameChaos is an edge-first experimental control platform: you design sensor-driven systems, run them on the authoritative edge, and let a fleet of edges improve its models from its own operation. This guide orients you to the pieces and points at the rest of the docs.

These pages are documentation for the marketing site — the product itself lives in the cloud app. Use them to understand the model before you open the app.

The shape of the platform

Everything you build follows the same three steps:

  • Design — compose real and virtual sensor arrays, physics and inference models, and the experiments that exercise them.
  • Run — execute experiments and simulations on the edge, in real, simulated, or hybrid mode, deterministically and repeatably.
  • Improve — aggregate like-processes across your fleet to refine the models that drive your systems.

Edge first, cloud second

The single most important idea is where execution lives. The edge server is the authoritative runtime — it owns your hardware and runs the control loop without waiting on the network. The cloud is a non-authoritative layer that oversees the fleet and aggregates across it; it never starts, stops, or mutates a live run.

If you remember one thing, remember that split. The rest of the docs build on it.

Where to next

  • Core concepts — the vocabulary: sensors, experiments, runs, and process-class templates.
  • Edge and cloud — exactly which responsibilities sit where, and why distribution is publish-and-pull.