QIRAVA DATABASE / DEVELOPMENT PREVIEW

Your data.
Your engine.

A Rust database for documents, queries and object storage. Run the same transaction engine in your application or on your server.

Embedded + standalone today.
Cluster architecture in development.

Rust at the coreQQL for your dataEncrypted by defaultOne transaction path
OPEN THE ENGINE / 01—03

Every record.
One path to durable.

Start with a query. Follow its index candidates, transaction boundary and storage protection. Explore the layers to see what each one owns.

Trace a request →
ONE ENGINE / THREE LAYERS
Transaction engine

The planner chooses candidate access. A shared execution context keeps resolved records available through the transaction.

THE FOUNDATION

Keep the hard parts
in the database.

Build with explicit contracts, predictable mutations, and storage that owns the full commit lifecycle.

A LANGUAGE FOR THE WORK

Readable queries.
Real transactions.

Follow a document from query planning to durable storage. Typed operations and QQL use the same validation and commitment rules.

See how indexes work →
projects.qql
SELECT title, status FROM projects
WHERE workspace = :workspace
  AND status = "active"
SORT title ASC
LIMIT 20
Bind values. Keep query text stable.
CHOOSE YOUR BOUNDARY

Close to your application.
Consistent at the core.

Explore operating modes →
Available for development

Embedded

Use the public Rust library directly in your process. Your host owns the key and lifecycle.

qirava::Database
Available for development

Standalone

Run the server and connect over local Unix sockets or verified remote HTTPS.

qiravad serve
MEASURE. VERIFY. IMPROVE.

Performance needs evidence.

Explore recorded workloads, recovery checks and the tradeoffs behind each optimization.

Read the benchmarks ↗
120matched trials across
1, 2, 4 and 8 workers
FZ server measurements · warm reads · encrypted storage
BUILD SOMETHING THAT LASTS

Start with a local database.