The database for Live State
Your state, your logic, your derived views, all in one transactional flow. No caches to invalidate. No cron to babysit. No drift to debug.
$ warning: do not use in production yet. early adopters welcome.
// why_teams_care
ACID core for live state
Real transactions with real rollback. Not best-effort Lua scripts or cache hacks you have to debug at 2 AM.
Derived views stay fresh
Your views update as your data changes. No cron jobs. No stale dashboards. No "have you tried refreshing?"
Logic lives next to data
Put your logic next to your data, inside the transaction. Fewer network hops, tighter guarantees.
# capabilities
Why ReifyDB
You should not need four systems to manage state that lives in one place. ReifyDB gives you transactions, incremental views, and programmable logic in a single engine.
ACID core for live state
Your state stays consistent, even under contention. Serializable transactions with real rollback, not the best-effort scripts you are used to patching together.
Incremental derived views
Your views update the moment your data changes. No cron job to schedule, no polling loop to tune, no dashboard that is quietly three minutes behind.
Programmable transitions
Your validation and business rules run inside the transaction, right next to the data. Fewer round trips, fewer places for things to go wrong.
Native state primitives
Tables, counters, ring buffers, histograms, and views all live in one transactional core. Embed it in your app or run it as a server.
# playground
See RQL in Action
Write queries the way you think about your data. No translation, no ceremony.
// Query inline data directly. Great for prototyping and testing.
# use_cases
Built for Live Application State
If your application reads it, writes it, and reasons about it on every request, that is the state ReifyDB was built for.
>User & Session State
Sessions, preferences, auth tokens. You need them consistent and fast. You get both.
>Trading & Financial State
Positions, balances, order state. One bad write here can cost real money. ReifyDB makes sure that does not happen.
>Game & Simulation State
Player state, world state, simulation ticks. Everything stays consistent even when thousands of updates hit at once.
>Workflow & Process State
Multi-step workflows, task queues, process coordination. No more duct-taping Redis, Postgres, and a cron job together.
>Counters, Queues & Buffers
Counters, ring buffers, histograms, rate limiters. Built in, transactional, and ready to use. No external dependencies.
>Leaderboards & Rankings
Rankings that stay correct even when thousands of scores update at the same time. No eventual consistency surprises.
# pipeline
How It Works
Three steps, one transaction. Nothing drifts apart because nothing ever leaves the envelope.
Write state transactionally
You write your state with full ACID guarantees. If something goes wrong, it rolls back. No partial writes, no guessing.
Validate and apply logic
Your business rules run inside the same transaction. Invariants hold. Changes propagate. Nothing slips through the cracks.
Stay fresh automatically
Your derived views update the moment the transaction commits. You never poll, you never schedule, you never wonder if the data is stale.
One ACID envelope. Writes, logic, and derived state move together or not at all.
# replaces
What ReifyDB Replaces
You have probably duct-taped three or four systems together just to manage state. Here is what you can stop maintaining.
You know that moment when your cache says one thing and your database says another? That goes away. One store, one source of truth.
Your views update when your data changes, not whenever a cron job gets around to it. No polling, no refresh buttons, no stale numbers.
Stop scattering your state logic across microservices, workers, and cron jobs. Put it next to the data where it belongs.
Counters, queues, ring buffers, histograms. You do not need three systems and a pile of glue code. One engine, full transactional guarantees.
# faq
Frequently Asked Questions
Honest answers to the questions engineers actually ask