Security
A public-safe summary of how the platform is built to limit blast radius when something goes wrong — not an exhaustive security audit.
Per-device identity
Every enrolled device holds its own credential rather than a fleet-wide shared secret. A device's access can be rotated or revoked individually, without affecting any other node in the organization.
Organization boundary
Every resource in Core Cloud — devices, jobs, nodes, assets — is scoped to exactly one organization, and every API request is authorized against the caller's membership and role in that organization before any data is returned.
Audit trail
State-changing actions are recorded as outbox events, giving the platform a durable, ordered record of what happened and when — the foundation for the audit views planned in the Control Center.
Access model
There is no public self-service sign-up. Every account is created by invitation from an existing organization Owner or Admin, and every invitation link is one-time.