xolu

Olu

A graph-enhanced document store with SQL-like query capabilities

v0.9.7-patched74 — 2360 tests passing. See MANUAL.md for complete documentation.

What is Olu?

Olu is a REST API server that combines document storage with automatic graph representation of entity relationships. Define your data, create entities with references, and get both SQL-like queries (OQL) and graph traversal for free.

Olu operates in two modes:

• Single-tenant — full feature set: CRUD, REFs, OQL, full-text search, graph traversal
• Multi-tenant (strict) — full feature set: CRUD, REFs, OQL, full-text search, graph traversal; all operations tenant-scoped

Olu is a Go port of rserv (Python). Both share the same API design.

Quick Start

git clone https://github.com/ha1tch/xolu.git && cd olu
make build && ./bin/olu

Create an entity:

curl -X POST http://localhost:9090/api/v1/users \
  -H "Content-Type: application/json" \
  -d '{"name": "Alice", "email": "alice@example.com"}'

Create with reference:

curl -X POST http://localhost:9090/api/v1/posts \
  -H "Content-Type: application/json" \
  -d '{"title": "Hello", "author": {"type": "REF", "entity": "users", "id": 1}}'

Query with OQL:

curl -X POST http://localhost:9090/api/v1/oql/query \
  -d '{"query": "SELECT * FROM users WHERE age > 25 ORDER BY name LIMIT 10"}'

Key Features

Multi-Tenancy

Olu provides two operational modes:

Single-tenant (OLU_TENANT_MODE=path): All features enabled. Non-tenant routes use the default store (tenant 0). Tenant-prefixed routes (/api/v1/tenant/{id}/...) provide optional scoping.

Multi-tenant strict (OLU_TENANT_MODE=strict): Tenant context required for all data operations. Graph, OQL, search, and export are available through tenant-prefixed routes only. Graph operations are fully tenant-isolated: node IDs are transparently prefixed and stripped, and cross-tenant traversal is blocked at the snapshot layer. Auto-registration of new tenants is controlled by OLU_TENANT_AUTO_REGISTER. Timeseries storage (Pebble-backed) is available only in this mode.

See the Multi-Tenancy section of the manual for the full security model.

API Overview

All entity and query endpoints have tenant-scoped variants at /api/v1/tenant/{tenant_id}/....

Configuration

Key environment variables:

# Storage
OLU_STORAGE_TYPE=sqlite          # jsonfile or sqlite
OLU_DB_PATH=olu.db               # SQLite path
OLU_FULLTEXT_ENABLED=true        # Enable FTS5

# Multi-tenancy
OLU_TENANT_MODE=strict           # path or strict
OLU_TENANT_AUTO_REGISTER=false   # Explicit tenant creation only

# SQLite tuning (0 = backend default)
OLU_SQLITE_MAX_OPEN_CONNS=0      # Writer pool size (default: 1 for WAL)
OLU_SQLITE_READ_POOL_SIZE=0      # Reader pool size (default: NumCPU)

# Auth
OLU_AUTH_TYPE=jwt                # none, jwt, or apikey

See MANUAL.md for all options.

Testing

make test        # Quick tests
make test-full   # Full suite including stress tests
make bench       # Benchmarks

Project Structure

olu/
├── cmd/olu/              # Server entry point
├── cmd/olu-migrate/      # JSONFile → SQLite migration tool
├── pkg/
│   ├── cache/            # Memory (sharded) & Redis cache
│   ├── config/           # Configuration with validation
│   ├── errors/           # Structured error codes
│   ├── graph/            # FlatGraph — tenant-isolated in-memory graph with persistence
│   ├── middleware/        # Auth, rate limiting, metrics
│   ├── oql/              # OQL engine, planner, SQL generator
│   ├── server/           # HTTP handlers and routing
│   ├── storage/          # JSONFile & SQLite with read/write split
│   ├── sulpher/          # Sulpher graph query engine
│   ├── tenant/           # Tenant registry
│   ├── timeseries/       # Pebble-backed timeseries storage
│   └── validation/       # JSON Schema validation
└── docs/                 # Architecture and API documentation

Documentation

• Manual — Full API and configuration reference
• Timeseries Design — Pebble-backed timeseries storage for sensor events
• Fleet Architecture — Multi-instance deployment design
• OQL API — Query language reference
• Graph API — Graph traversal endpoints
• Export API — Data export endpoints
• Query Planner — Adaptive query planner internals

License

Copyright (c) 2025-2026 haitch

Apache 2.0 — See LICENSE

Full Documentation →