One database.
More of the picture.
RURAL is a database in development for software teams that need records, relationships and durable history to work together.
A working local prototype whose full native and mixed-load acceptance is still underway.
Read the current statusThe database works locally.
Documents, schemas, graph queries, authenticated local access, backups, branches, merges, analytics and bounded MCP views have completed their implementation packets. Full native acceptance, mixed-load qualification, packaging and final handoff remain open.
Scope and limitsKeep the record.
Keep its context.
Business data gains meaning from the relationships around it: what produced it, which work it belongs to, and how it changed. RURAL is being designed around those connections.
Store structured records.
Documents give applications a clear place to keep and retrieve their data.
Documents & models ↗ 02 / RELATIONSHIPSFollow how things connect.
Represent relationships alongside the records they help explain.
Queries & graphs ↗ 03 / HISTORYPreserve a clear history.
Explore changes from a stable snapshot and retain where a new path began.
Snapshots & branches ↗From a change
to a useful answer.
Follow a record through the database. Each stage has implementation evidence; the complete prototype is still passing its final acceptance gates.
01Write a recordAn application submits a bounded change.
Implemented document and schema commands validate the complete change before committing it.
02Record durable historyA local journal can preserve accepted changes.
Journal framing, ordered append and recovery foundations have component-level work. This is not a claim of replicated or production durability.
03Connect and queryRelationships add context to stored data.
Typed query plans, graph relationships and snapshot cursors are implemented within documented bounds.
04Return an evidenced answerAnalysis should retain source and scope.
Analytics and bounded Oracle/MCP views are implemented. Production-scale capacity and model efficiency remain unclaimed.
Try a change.
See the response.
Explore the current API examples in your browser. The playground is a guided prototype surface, not a live hosted database.
Built for explicit
control.
The native prototype is written in Zig. The engineering work focuses on clear state changes, bounded inputs and recoverable local history.
Component evidence describes its tested scope. It does not certify a complete database release.
Review project statusUnderstand the design.
Start with the
current foundation.
Explore the design.
Check the implementation status.