Statey
The system of record for your AI work

Structured, permanent data for working with AI.

Work is moving out of single-purpose apps and into chat, but chat forgets everything. Statey is a real database you and your AI read and write as you work. Tasks, customers, docs, inventory, all stored in structure and pulled back the moment you ask.

No app. No UI. The conversation is the interface.

statey / dogfood workspace
live
Claude
Triage the runner retry bug and put it in progress.
create_record · tickets
update_record · TIC-206
Created TIC-206 and moved it to In progress.
Ask Claude…
tickets collection
2 records
IDTitleStatusOwner
204Draft Q3 onboarding docDoneyou
205Reconcile inventory countsBacklogagent
206Runner retry loop drops deliveriesTriageagent
event  ticket.created  actor agent:triage-bot
event  ticket.updated  status → in_progress
trigger matched → delivery queued · runner
trigger fired
Speaks MCP. Drop it into
ClaudeClaude CodeChatGPTCursor
01 · The problem

Chat forgets everything.

Every session starts from zero. The ticket your agent triaged, the customer it updated, the doc it wrote: all of it evaporates when the conversation ends, or gets pasted into a screenshot and lost. There's nowhere for the work to live that an agent can actually operate.

02 · What it is

Headless on purpose, so your agent draws the UI.

LLMs can now render a bespoke interface on demand: a board, a table, the one answer you need, drawn straight from a tool result. So Statey ships none. It's the structured layer underneath: collections, schemas, validated records, every change attributed, versioned, and logged. The view is the agent's to draw, fresh each time. The record is ours to keep.

Structured records

Collections and schemas, not a chat transcript. Validated contracts, not constraints.

Full provenance

Every write attributed to a human or agent, event-logged in the same transaction.

Multi-actor

You and your agents, safely concurrent, with optimistic concurrency from day one.

Soon

Reactive

Triggers fire your agents the moment data changes, with full causation tracking.

03 · How it works

Store. Query. React.

01

Store

An agent creates a collection and writes records conversationally, with no schema design up front.

create_record → tickets
02

Query

Agents read and write through tools shaped for direct rendering: boards, tables, the answer you asked for.

query tickets status:in_progress
03

React

Every mutation emits an event. Triggers match events and dispatch your agents to act and write back.

trigger ticket.created → runner
04 · Connected

Connect once. It's there from every surface.

Point any MCP client at your workspace and the same records are live everywhere. Your whole team and their agents read and write one source of truth at the same time, with every change attributed to whoever made it.

C
Claude Desktop
connected
>_
Claude Code
connected
{ }
Codex
connected
G
ChatGPT
connected
MCP
statey / dogfood workspace
live
ticketscustomersdocsinventory8 collections · 1,204 records
YODKPR
Your team and their agents, working the same data.
06 · Make it yours

Bend it into anything. Change your mind anytime.

You don't design a database. Describe what you're tracking and Statey builds the structure for you. Want it shaped differently next week? Just say so: add a field, split a collection, rename a status. No migrations, no schema files, nothing database-y, and no need to be technical.

customers / record
rec_8fae · v3
Also track a renewal date and an owner.
nameNorthwind Co.
planScale
mrr$4,200
renewal_datenew2026-09-01
ownernewdana@acme.co
schema updated · no migration
Steal a starting point

A lightweight ERP

Orders, inventory, and fulfillment stitched together and queried in plain language.

A marketing archive

Every campaign, asset, and result, searchable and reusable by your agents.

An applicant pipeline

Candidates, stages, and notes your recruiter-agent keeps moving on its own.

A research vault

Sources, findings, and citations that compound instead of scrolling away.

…or whatever you can describe
Bespoke task trackerCRMBug triageContent calendarDeal pipelineIncident logOKRs & goalsInventory countsReading listInvestor CRMProduct roadmapPress & PR listInvoice logHousehold inventoryHabit tracker
05 · Bring the work

Bring the work that doesn't fit in a chat window.

Tasks & tickets

A Linear-style tracker your agents run end to end.

Customer records

CRM data your agents read, enrich, and keep current.

Markdown docs

Endless structured documents, versioned and queryable.

Inventory & ops

Counts, statuses, and operations that stay in sync.

The way Airtable was the system of record for browser-driven work, Statey is the system of record for agent-driven work.

07 · Pricing

Pay for what you keep.

Statey is priced on the records you store, not the reads and writes flying back and forth. Your agents can work the workspace as hard as they like; you only pay as your data grows. Set a hard spend cap and Statey holds the line: breach it and writes pause, nothing is ever deleted.

See full pricing
$0while in early access

a generous free tier, then simple usage-based storage as you scale.

Priced by storage, not seats or activity
Reads and writes always run free
Set a hard cap, never a surprise bill

Connect it to Claude and start.

We're onboarding early teams now. Leave an email and we'll reach out with an invite.

No spam. Just an invite when your spot opens.Read the docs →