explaingit

ricalanis/saobase

Analysis updated 2026-05-18

0RustAudience · developerComplexity · 5/5Setup · moderate

TLDR

An experimental database built for AI agents, where every write must pass through a governed merge step before it becomes official truth.

Mindmap

mindmap
  root((SAObase))
    What it does
      Gates every write
      Branch and merge model
      Tamper evident ledger
    Inspiration
      SAO 2026 workshop
      WormBase ledger idea
      Supabase style inversion
    Tech stack
      Rust
      SQLite projection
      Python oracle
    Use cases
      Agent safe writes
      Policy enforced merges
      Budget tracked changes

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Give autonomous agents a database where writes only land after passing a policy check.

USE CASE 2

Let an agent explore changes on a branch before merging them into the permanent record.

USE CASE 3

Track which agent made which change with built in provenance stamps.

USE CASE 4

Undo a mistaken change by proposing a new correcting entry instead of rewriting history.

What is it built with?

RustSQLitePythonTOML

How does it compare?

ricalanis/saobase04amanrajj/netwatch0xr10t/pulsefi
Stars000
LanguageRustRustRust
Setup difficultymoderatemoderatehard
Complexity5/53/54/5
Audiencedeveloperops devopsdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires installing the Rust toolchain before building the sao command line tool.

In plain English

SAObase is an experimental database designed for AI agents rather than for humans typing SQL by hand. The central idea is that every write to the database goes through a single controlled gate before it becomes official truth. Agents do their exploratory work on separate branches, similar to how a programmer might work on a branch in version control, and only when that work is merged back into the main record does the system check policy rules, verify the change, record who made it, settle any budget the agent was allowed to spend, and permanently log the entry, all as one atomic step called the Gate. The project grew out of a workshop on agent-oriented data systems and an earlier project called WormBase, which introduced the idea of a single, permanent, tamper evident ledger as the only source of truth, with every other view of the data generated from that ledger. The README also compares the approach to Supabase, the popular database and backend platform, arguing that just as Supabase built authentication and other services directly into the database rather than bolting them on separately, SAObase wants to build governance and safety controls directly into the database for agent systems, plus an outer layer that manages policy and a client toolkit that helps agents track budgets and decisions. The project is currently an early preview release, not a finished product, with an internal checklist of required features being tracked and verified before anything is considered complete. To try it, a developer needs the Rust programming language installed. After cloning the repository, they can install a command line tool called sao and run a built in demo, or manually create a store, branch off proposed changes, and merge them through the Gate using a series of commands. The system does not support rewriting history, only adding corrective entries on top of it. The codebase is organized into several Rust crates that separate the core storage engine, input and output handling, a small SQL like language, the command line interface, testing tools, and a formal model used to check correctness.

Copy-paste prompts

Prompt 1
Explain what happens inside SAObase's Gate when a branch is merged into truth.
Prompt 2
Walk me through the sao demo command and what it shows about the write path.
Prompt 3
Show me how to create a strand, propose a change, and merge it using the sao CLI.
Prompt 4
Compare SAObase's governance model to how Supabase built services into Postgres.

Frequently asked questions

What is saobase?

An experimental database built for AI agents, where every write must pass through a governed merge step before it becomes official truth.

What language is saobase written in?

Mainly Rust. The stack also includes Rust, SQLite, Python.

How hard is saobase to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is saobase for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.