Planes and residency
Where Sparq keeps configuration and where it keeps your data.
Sparq separates where it is configured from where your data lives.
| Part | Holds | Never holds |
|---|---|---|
| Directory (global) | Opaque placement ids and region codes, to route a request to the right geo | Conversation content; customer names in DNS |
| Control plane (one per geo) | Configuration, credentials as hashes, grants, settings, compliance profiles, the model registry, Releases, the administrative audit | Conversation, run or knowledge content |
| Stamp (data plane, inside a geo) | Conversations, runs, files, knowledge and vectors, the usage ledger, the runtime audit | Data from any other stamp |
A geo is an explicit list of regions, including its backup and disaster-recovery regions. Disaster recovery goes to a paired region inside the same geo, never across a border. No query, foreign key or cache crosses from one stamp to another.
Deployment models
| Model | Control plane | Data plane | Models | Status |
|---|---|---|---|---|
| Frontier Cloud | Sparq | Sparq | Any registry deployment your policy allows | Early access |
| Hybrid Sovereign | Sparq | Your cloud | Your provider accounts or self-hosted models | Roadmap |
| Full Sovereign | You | You | Open-weight models only | Roadmap |
Full Sovereign can only run open-weight models, because proprietary frontier models are not distributed as weights.
The deployment model decides where Sparq runs. Each client's compliance profile decides where that client's data may be processed. Sparq applies both and refuses a setting where they conflict.