In standard SaaS applications, your data is often commingled in massive, shared databases. StateWarden rejects this model. To begin using the system, you must first establish a Realm.
What is a Realm?
A Realm is a cryptographically isolated administrative boundary. It is your private sovereign territory within the StateWarden ecosystem. Everything happens within the context of a Realm:
- Device Pairing: Agents are bonded cryptographically to a specific Realm.
- Data Residency: Storage policies (Driad Data Planes) are bound to the Realm's geographic region.
- Identity & Access: Role-Based Access Control (RBAC) and Multi-Factor Authentication (MFA) policies are enforced at the Realm level.
Data from Realm A cannot interact with, be accessed by, or be decrypted by Realm B - isolation is enforced cryptographically, not administratively.
Why Regions Matter
Backup payloads physically reside on Driad storage nodes assigned to your Realm, and every node belongs to a region. Region selection is not a latency optimization; it is an architectural boundary: data residency is enforced per region.
If you select a European region, your backup payloads will not leave the European Union. This turns GDPR data-residency compliance into a property of the storage layout rather than an administrative procedure.
Region names and availability are deployment-specific, so this guide does not enumerate them. Allowed regions are configured on the Security & Compliance page (/security) under Data Residency - select a deployment region (data residency is enforced per region) that matches your legal and compliance requirements. At least one region must remain selected.
Step-by-Step Setup
- Log into the StateWarden Dashboard: Navigate to
dash.statewarden.com. - Open the Realm List: The realm list (
/) is the landing view. Click Create New Realm. - Name Your Realm: Choose a descriptive name (e.g., "HQ Datacenter", "Finance Dept") and an optional description.
- Confirm: The system provisions the Realm and prepares the control plane for your incoming agents. Data-residency regions are not chosen in the creation dialog; they are configured afterwards under Security & Compliance → Data Residency (see above).
The Global Encryption Strategy (Optional but Recommended)
By default, each device manages its own unique encryption keys. However, for enterprise environments, you can configure a Global Master Key for the Realm.
True to our Zero-Knowledge architecture, our servers never store this key. You input the Master Key exclusively on the client-side Dashboard, and it is delivered to your Agents over their authenticated, encrypted channels, allowing your devices to adopt the global cryptography without the key being persisted on StateWarden infrastructure.