Quick Start

This walkthrough takes you from no account to your own hosted workspace: a free individual sandbox on the Consystence hosted service. You need a web browser and nothing else: no download, no controller and no edge. If you want the vocabulary first, read the core concepts.

Public beta

The hosted service is in public beta. During the beta, free individual sandboxes and paid organisations are both arranged with our team: request access. See plans.

1. Request a sandbox

During the public beta, free individual sandboxes are arranged on request: request access. Each account can hold one free sandbox, and Cloud onboarding describes how a sandbox is set up and the rules for its slug.

2. Sign in and open your sandbox

Go to account.consystence.com and sign in, or sign up if you do not have an account yet. Sign-in runs through Microsoft Entra External ID at id.consystence.com, so Consystence holds no password of yours. Signing up is also where you accept the Terms of Service and Privacy Policy.

Once your sandbox is ready, it is listed under My tenants in the account console. Open it to reach your workspace at https://{slug}.consystence.dev, where your account is its first owner.

3. Browse the library

A new sandbox has one starter site, Main Site, with nothing in it yet: no controllers, no devices and no simulation.

Open Library to browse the device types available to your tenant, including the first-party Consystence Standard Library. A device type declares a kind of equipment once (its tags, alarms and commands), and every device you add is an instance of one. Note a type id for the next step, for example consystence.pump.centrifugal. See Device types for how types are built.

4. Add a controller and a device

A site’s model is the controllers it has and the devices they serve. As the owner, you can edit it from the web console:

1. Open Controllers and choose Add controller. Give it a name, an asset number (for example PLC-001), a platform, a protocol and an address (for example 192.0.2.10). A new controller starts offline.
2. Open Devices and choose Add device. Give it a name and an asset number (for example PP-01), enter the type id you noted, and in Controller enter the id (ctl_…) of the controller you just added; the same page lists the site’s controllers with their ids. Area and tag mappings are optional. The server gives the device its id and opens the device’s engineering page.

The starter site is display-only

A new starter site is display-only: you can build and inspect its model, but no simulation runs on it and device commands are refused. Running a simulation on a sandbox site is not yet available. See Roles for what a site’s operator-surface declaration admits, and Simulation profiles for how a device type’s simulation behaves.

5. Ask the assistant

Open Assistant and ask IO (the assistant) about your site, for example about the device you added and its device type. The assistant reads, explains and recommends; it never commands equipment. Your sandbox includes a starter advisory AI allowance. The page shows a notice that the conversation is recorded: it is kept as a permanent record in the operational journal, and the Privacy Policy describes what that record holds.

Next steps

• Core concepts: organisations, sites, device types and instances.
• Cloud onboarding: the hosted path in full, including identity, subdomains and joining an organisation.
• Device types: the type system behind the Library.
• CLI Quick Start: the csy client. CLI access is arranged through a beta engagement.
• API: API keys and the endpoint reference.

Site servers

Site-server deployments are arranged with our team during the beta: contact us. There is no public download yet; published packages will be announced on consystence.com/download. See On-prem / site server for how a site server fits in.