Getting Started

Consystence is an AI-native runtime for monitoring and operating industrial facilities — from mining and coal handling and preparation plants (CHPPs) through to general process control. The same codebase runs as a cloud organisation manager or as an on-prem site server, renders its UI from the server over a single wire format, and reaches the field through an edge runtime and a PLCnext border gateway.

This guide gets a developer or technical evaluator from a clean checkout to a running demo. You do not need a PLC, an edge box, or a cloud tenant to start — the development profile runs entirely on simulated equipment with in-memory storage.

Beta — not intended for production use

Consystence is in public beta. Use it for evaluation, authoring and simulation, and commissioning trials alongside your existing SCADA — production control stays on your existing systems until the beta label comes off. Deterministic controller logic and hardwired safety systems hold final authority over physical outputs regardless.

Before you begin

Two principles shape everything that follows, so it is worth stating them up front.

Advisory-only AI

Consystence’s AI configures, queries, classifies, and explains — it never issues commands to equipment. Control writes are an explicit, audited human action, and hard interlocks live in deterministic controller logic and hardwired safety relays — never in the server or AI path. Keep this in mind as you read about the platform’s automation features.

Simulation-first

The development profile seeds the built-in device types (no instances); importing the demo tenant — covered in the quickstart — adds a seeded site whose instances run against the built-in simulator, with Orleans state held in memory. You can explore the full platform — device types, the server-driven UI, edge data flow — before any hardware or external services are involved.

The path through

Work through these three pages in order.

1. Install locally

Get the .NET 10 backend and the TypeScript frontend building and running on your machine, then open the dev server in a browser.

→ Installation

2. Learn the concepts

Understand the vocabulary before you build: organisations and sites, device types versus instances, the controller → module → channel → tag engineering model, the deployment topology, and the server-driven UI.

→ Core concepts

3. Run the demo

Bring up the seeded demo, watch live tag values flow from the simulator, and walk a device instance end to end.

→ Quickstart

Where to go next

Once the demo is running, branch into the area you care about:

• Platform overview — organisations, the org/site model, authentication, roles, and licensing.
• Architecture overview — the deployment topology and how the pieces communicate.
• Device types — the reusable type system, tags, alarms, and commands.
• Edge runtime — the edge silo and PLCnext communication.
• API — the authentication model, tenant API keys, and the endpoint reference.
• Deployment — running Consystence on Azure or on-prem.

Not yet generally available

The hosted control plane (organisation provisioning, sign-up, cells, Stripe billing, and licence tier pools) runs in production behind launch gates — self-serve signup is not yet generally available. This guide focuses on running Consystence locally; see Cloud onboarding for the hosted path.