Skip to content
Qirava lowercase logo

Products

One ecosystem, four product jobs

Qirava is not one giant bucket. DMS runs data and workers, Cloud orchestrates managed DMS capacity, Quill builds apps, and q* packages stay reusable.

Product map

What each repo is for

Use this as the quick product comparison before choosing docs or roadmap pages.

Qirava DMS

qdms
built

The core data/app runtime. Governance, database, jobs, replication, workers, and planned KMS are functions in one registry, reached only through execute() via a worker.

  • Embedded, standalone, and cluster install modes
  • Three checkpoints: L1 before-auth, L2 execute scope, L3 planner RBAC
  • Self-describing API, Studio, and compliance building blocks
Product page

Quill

qquill
built

The Rust-native UI/app framework used by this site: server-rendered pages, island hydration, full component route coverage, theme tokens, motion, and static export.

  • No server-side JavaScript toolchain
  • Headless state + styled token-driven components
  • Theme, density, radius, surface, and motion axes
Product page

The q* stdlib

qpkgs
built

Shared zero-dependency crates used by products: qexec, qvalue, and focused utility crates. It is not a dumping ground for product code.

  • Products depend on q*; q* never depends on products
  • Executor + value model substrate
  • First-party utilities only
Product page

Qirava Cloud

qcloud
partial

The managed-DMS control plane. Catalogs, cloud.* functions, and RBAC console are built; real tenant DMS infrastructure remains simulated/planned.

  • Thread/RAM/storage capacity model
  • Control plane built, infra effects simulated
  • Direct install and competing clouds stay possible
Product page

Boundaries

Packages are not products

The clean design system is not only visual: the product architecture has to stay legible too.

qpkgs

Shared packages only

qpkgs holds q* stdlib crates usable by any product. It is not where DMS, Quill, or Cloud product code goes.

qquill

Quill is a product

Quill is its own UI/app framework product, not a shared-functions folder moved into qpkgs.

qirava

Website is user-facing SSOT

Products, docs, architecture, roadmap, and status are explained here; engineering truth is tracked in the root docs/status registry.

Status legend: BUILT is shipping today, PARTIAL has a working seam with deferred parts, and PLANNED is designed but not yet built. See the roadmap for the full matrix.