L the languagewlG github

Your data isalready a graph.Query it that way.

Owl is a database for objects that point at each other.
You follow the references. You never write a join.

orders.customer.name

H to hoot

The language · OQL

Learn the verbs once.
Use them on everything.

A collection, a list inside a document and a reference followed backwards all take the same where, select, sort and count.

// An order points at its customer. Follow it.
orders.select {
    id,
    total,
    who: .customer.name
}

If an order has no customer, who is null. Nothing fails.

.customer.orders.itemsorderscustomersitemsa list inside each order

The engine

Rust, all
the way down.

There is no other database underneath. Owl's own engine stores the data, and it knows your schema and your references, so it can use both.

01

References that never break

Every object has a 64-bit identity that says nothing about where it is stored. Owl can move the data and every reference still holds.

collection16object32generation16
02

Records shaped by your schema

Field names are stored once, not in every record. Ask for two fields and Owl decodes two fields.

03

Writes that survive a crash

Every commit is checksummed and synced to disk before any reader sees it. After a crash, Owl loads its last checkpoint and replays the rest.

04

Indexes that know the graph

Every reference gets an index for the way back. You can add ordered, unique, composite and vector indexes.

Evidence

Right first.
Then fast.

Two suites give Owl and SQLite the same data, the same indexes and the same durability, then require the same rows back. Only then is anything timed. One suite is an ordinary shop. The other is built to be hard.

The shop suite has sixteen queries. Its check fails unless both engines return the same rows for every one.

Read the suites

Run it

Three commands
to a first answer.

# 1. Start a server (needs only a Rust toolchain)
cargo run --release -p owl-server -- --data shop.owl

# 2. Declare two collections and add a row to each
curl 127.0.0.1:7878/v1/script --json '{"source": "schema customers { id: String, name: String }\nschema orders { id: String, customer: Ref(customers), total: Float }\ncustomers.insert { id: \"c1\", name: \"Ada\" }\norders.insert { id: \"o1\", customer: \"c1\", total: 12.5 }"}'

# 3. Follow the reference from order to customer
curl 127.0.0.1:7878/v1/query --json '{"query": "orders.select { id, who: .customer.name }"}'

{"rows":[{"id":"o1","who":"Ada"}]}