
DNS-Editor Cloud
Internal operations documentation for the hosted variant — tenants, plans, provisioning, operator panel and cluster operation.
Context
Section titled “Context”Internal operations documentation. This code is not shipped: it runs the hosted variant of DNS-Editor. The Cloud layer builds on EE (and thus transitively on the CE core) and adds what only an operator needs.
┌─────────────────────────────────────────┐ │ Cloud Tenants · Plans · Operator │ ├─────────────────────────────────────────┤ │ EE Audit · Restore · Scan · SSO │ ├─────────────────────────────────────────┤ │ CE Zones · Providers · Users │ └─────────────────────────────────────────┘Packages
Section titled “Packages”| Package | Purpose |
|---|---|
tenancy/ | Plan per organisation, home region, plan limits |
identity/ | Global identity by email, memberships across organisations |
operator/ | The operator panel: registry, dashboard, regions, platform settings |
provisioning/ | The single path through which tenants come into being |
registration/ | Self-service registration via magic link |
orgshare/ | Project sharing across organisation boundaries |
backup/ | Nightly tenant exports and restore points |
demoseed/ | Large demo dataset (~10 organisations, all features) |
Where to start?
Section titled “Where to start?”- Getting started — startup and configuration
- Cluster operation — multiple nodes, Valkey, YugabyteDB
- Creating tenants — provisioning API and registration
- Operator panel — the operator’s interface