Shipping today
Present in the codebase and usable now. It can still improve, but the capability exists.
Roadmap SSOT
What is complete, what is partial, what is planned
The qirava website is the source of truth for product status. This page gives the product-level summary; open a product board for the detailed lane-by-lane status.
How to read status
Working seam
A real implementation path exists, with known gaps or hardening still in progress.
Designed, not shipped
Important to the product direction, but not something users should depend on today.
Product boards
Status per product
Capability state is more useful than aspirational dates. Each product has an honest board with built, partial, and planned lanes.
Qirava DMS
qdmsEngine, workers, function registry, QQL/DDL, RBAC + governance, config-as-data, WAL, self-describing API, Studio, and single-leader replication are shipping; KMS/compliance and cluster automation remain planned.
Engine + workersKMS/complianceCloud scale
Open roadmapQuill
qquillThe view layer, native SSR, islands, static export, full component route coverage, theming, motion, and CLI are shipping; deeper playgrounds and dev ergonomics continue.
SSR · islands · SSG36 component routesquill dev
Open roadmapThe q* stdlib
qpkgsThe zero-dependency substrate crates are shipping. Planned work adds crypto primitives and broader standard library coverage behind first-party contracts.
13 cratesMore crypto
Open roadmapQirava Cloud
qcloudControl plane v1 is built: _cp_* catalogs, cloud.* functions, and the RBAC-gated Cloud Console. Thread/RAM/storage control state is real; tenant DMS spawn, caps, live scaling, billing/payment, and confidential compute are simulated/planned.
Control planeInfra simulatedLive scaling
Open roadmapCode audit snapshot
What the repo proves today
This tracker is based on local product code, not aspirational copy. Unknowns stay out until product info is supplied.
Qirava DMS
SSOTBuilt
Engine/QQL, WAL, worker funnel, auth/session/HMAC, Studio, API/OpenAPI, jobs, and single-leader replication are present in qdms.
Planned
KMS backend, worker secret/env reads, packaged compliance mode, authenticated replication hardening, Cloud orchestration, and confidential-compute seed ceremony remain planned/partial.
Quill
SSOTBuilt
view/style/theme/ui/design/runtime/docs/icons/cli/build/signal crates are present; every styled component has a docs route; Motion::Press/Lift/Tilt3d and the motion runtime are implemented.
Planned
quill dev, route auto-discovery hardening, advanced components, and deeper playground coverage remain planned/partial.
q* stdlib
SSOTBuilt
Thirteen q* crates are present: qexec, qvalue, qarray, qobject, qstring, qmath, qnumber, qconvert, qencoding, qcrypto, qregex, qtime, quuid.
Planned
Additional crypto/provider work and wider stdlib coverage remain planned.
Qirava Cloud
SSOTBuilt
qcloud boots a control DMS, creates _cp_* catalogs, registers cloud.* functions, and serves an RBAC-gated Cloud Console.
Planned
Real tenant DMS spawn, resource caps, no-disruption scaling, public signup, payment, domains, and confidential compute are simulated/planned.
Why this page exists
No parallel roadmap, no marketing fog
The roadmap is part of the website SSOT and is backed by the code audit: qdms, qquill, qpkgs, qcloud, qbrand, and qirava. Status changes should update this site instead of creating disconnected docs.
Status legend: BUILT means usable now, PARTIAL means a working seam with known gaps, and PLANNED means designed but not yet built. No dates are promised here.