Object Store
Object-oriented database with the EAV pattern
What it does
A live, typed entity-attribute-value graph backed by an embedded OODB with sub-millisecond reads. The substrate every other IOBOXX product reads and writes through. Any MCP-aware agent can traverse it; every write lands in a deterministic, hash-chained commitlog. Designed for application building and rapid prototyping without a schema migration tax.
The Object Store is the substrate. Every product above it — Memory, Connect, Studio — reads and writes through it. Typed entities live as EAV rows, reducers are the only path to mutation, and the commitlog under every reducer call is the source of truth for replay, audit, and contribution attribution.
Key features
- Typed objects, reducers, deterministic commitlog
- Sub-millisecond reads, real-time WebSocket subscriptions
- MCP tools — Fundis read and write directly
How it works
The Object Store runs as an embedded module inside SpacetimeDB. Reducers are written in Rust, types are defined declaratively, and the EAV model means you can prototype a new taxonomy without writing a migration. MCP tools surface object operations to any MCP-aware agent — read, write, search, traverse.
- Working memory (OODB) — the EAV storage model and reducer pattern.
- Data model — typed objects, attributes, and references.
- MCP server — the protocol surface agents use.
Try it
The quickstart walks through publishing the module, registering an agent, and watching objects materialise as your Fundi writes them.