Creating Your First Realm: The Sovereign Boundary

Creating Your First Realm: The Sovereign Boundary

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 can mathematically never interact with, be accessed by, or be decrypted by Realm B.

Why Geographic Regions Matter

When you create a Realm, you must select a geographic Region (e.g., EU-Central, US-East). This is not just a latency optimization; it is a strict legal and architectural enforcement.

StateWarden ensures Data Sovereignty. If you select a European region, your backup payloads will never leave the European Union. This makes achieving GDPR compliance a structural guarantee rather than an administrative hurdle.

Step-by-Step Setup

  1. Log into the StateWarden Dashboard: Navigate to dash.statewarden.com.
  2. Initialize the Realm: Click Create Realm.
  3. Name Your Realm: Choose a descriptive name (e.g., "HQ Datacenter", "Finance Dept").
  4. Select Region: Choose the region that aligns with your legal and compliance requirements.
  5. Confirm: The system will immediately provision your isolated database schemas and prepare the control plane for your incoming agents.

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 see this key. You input the Master Key exclusively on the client-side Dashboard. It is securely transmitted directly to your Agents via secure tasks, ensuring that your devices can seamlessly adopt the global cryptography without ever exposing the key to the StateWarden infrastructure.

Was this article helpful?