Qirava Cloud docs

Overview

Qirava Cloud is the managed-DMS control plane: it runs a control DMS that orchestrates tenant DMS instances. The product goal is simple capacity selling — threads, RAM, and storage — with vertical and horizontal scaling that does not disrupt service. Today the control-plane model is built; the real infrastructure effects are simulated and clearly badged planned.

What Cloud manages#

Qirava Cloud control DMS
  ├─ _cp_tenants / _cp_nodes / _cp_plans / _cp_usage / _cp_invoices
  ├─ cloud.* orchestration functions
  └─ Cloud Console
        │
        ▼ planned infra effect
Tenant DMS instance
  ├─ its own governance
  ├─ its own databases/workers/apps
  ├─ planned KMS seed/secrets
  └─ tenant data never belongs to the cloud control plane

Control plane owns the box; tenant DMS owns the data

threads: The CPU concurrency budget sold to a tenant DMS. In the future the running DMS executor re-reads this cap live.
RAM: The memory budget sold to a tenant DMS, represented in whole GB in the current control model.
storage: The disk/storage budget sold to a tenant DMS, represented in whole GB in the current control model.

What is built today#

Area	Status	Evidence
control DMS	BUILT	qcloud boots a real qdms::Qdb, ensures catalogs, registers functions, and serves the console.
_cp_* catalogs	BUILT	Tenants, nodes, plans, subscriptions, usage, invoices, and audit rows persist in the control DMS.
cloud.* functions	BUILT	Provision, vertical scale, horizontal scale, switch mode, suspend/resume, terminate, invoice.
Cloud Console	BUILT	RBAC-gated Quill console with honest simulated/PLANNED badges.
tenant DMS boot/caps/billing	SIMULATED	The row/state is real; the infra effect is returned as a planned note.

Scaling goal#

Vertical scale: change one DMS instance's thread/RAM/storage cap and have the running DMS re-read the cap live.
Horizontal scale: add or remove cluster replicas with replication/catch-up and a brief FIFO-hold cutover when needed.
Migration/upgrade: start a fresh DMS/VM, stream state, cut over, then retire the old one without rewriting data.

The same DMS remains installable outside Qirava Cloud: embedded in an app, standalone on a server, clustered by the owner, or operated by a third-party cloud provider competing on price or policy.