Skip to content
Qirava lowercase logo

Developer docs

Learn Qirava in the order humans need

Start from the product path, then dive into the per-product manuals. The docs explain what to run, how access works, how to build UI, and what is already complete.

Start path

From zero to a safe app

If you are new, do not begin with an API catalog. Follow this path first.

  1. 01

    Run the DMS

    Start the server, capture bootstrap credentials, and confirm QQL routes on the local worker.

    Open quick start
  2. 02

    Learn the access model

    Understand L1 before-auth, L2 execute scope, and L3 planner RBAC before mutating data.

    Read access model
  3. 03

    Build with Quill

    Use the component catalog, theme tokens, islands, and static export without hardcoded UI drift.

    Browse components
  4. 04

    Verify roadmap state

    Check built, partial, and planned capability status before relying on a feature.

    Open roadmap

Manuals

Pick the product you are working with

Each manual is product-specific. The website stays the SSOT; route files render authored content through the shared docs kit.

qdms

Qirava DMS

Install, run, query, secure, and operate the data system: QQL, RBAC, workers, API catalog, Studio, jobs, and replication.

Read DMS docsqquill

Quill

Build UI in Rust: views, styled/headless components, theme controls, scoped demos, islands, static export, and CLI.

Read Quill docsqpkgs

The q* stdlib

Understand qexec, qvalue, and the zero-dependency utility crates that products can depend on without pulling product code.

Read stdlib docsqcloud

Qirava Cloud

Learn the managed-control-plane design and what is planned versus what exists in the open-source primitives today.

Read cloud docs

Docs promise

No hidden second source of truth

Architecture, product docs, and roadmap/status live here. Operator runbooks can live elsewhere, but product truth should not fork into parallel files.

Architecture

Design SSOT

Security and performance rules are explained on the site so reviewers can evaluate changes against one published model.

Components

Theme-reactive demos

Quill docs keep density, radius, and scoped surface demos together so components prove they follow tokens.

Roadmap

Built / partial / planned

Status boards say what ships today, what has a working seam, and what remains planned — no vague future marketing.