Qirava Cloud docs
Built vs planned
This page is the contract for Cloud claims. Use BUILT only for code that exists and is test-backed. Use SIMULATED when the control-plane state is real but the infra side effect is not. Use PLANNED for future fleet, billing, KMS/confidential, and self-hosted cloud work.
Built#
- Control-plane binary that boots a real DMS and serves
/cloud/*. - _cp_* catalogs for tenants, nodes, plans, subscriptions, usage, invoices, and audit.
cloud.*orchestration functions that persist state and write audit rows.- RBAC-gated Cloud Console, session-bound CSRF, 403 pages for forbidden direct access.
- First-fit placement over recorded node headroom and durable allocation counters.
Simulated / partial#
| Feature | Current state | What is missing |
|---|---|---|
| tenant provision | Creates tenant/subscription rows and allocation counters. | Boot real tenant DMS process/VM, mint tenant custodian once, attach domain. |
| vertical scale | Writes new caps and allocation deltas. | Signal running DMS to re-read caps and prove no downtime. |
| horizontal scale | Updates replica count for cluster tenants. | Add/drain real followers and cut over safely. |
| billing | Synthesizes invoice from cap × 24h period. | Streaming usage meter and payment integration. |
Planned#
- Node agent and tenant DMS control socket.
- Real DMS spawn, lifecycle, resource caps, health, and restart.
- No-disruption vertical scale, horizontal scale, migration, and upgrades.
- Self-hosted/third-party Cloud packaging so others can operate managed DMS clouds.
- Confidential VM / SEV-SNP / attestation-gated secret release for managed confidentiality.
- Real metering, billing, payments, pricing UI, and release/account lifecycle.