Everything, organized.
Most docs hubs make you guess where the answer is. This one names the destination on every tile.
Start here
Pick the on-ramp that matches how you learn: a guided runbook, a five-minute quickstart, a full feature catalog, or a use-case guide.
Reference docs
The surfaces you'll live in once you're building. Every tool, endpoint, and language construct — with the promises and caveats spelled out.
AT VALID / AT RECORDED / OVER VALID BETWEEN). Procedures, functions, gotchas.By role
Four short paths through the same material, sorted by why you showed up.
Operate it
What running InvariantDB in production actually looks like — deploys, backups, replication, and the failure modes we've written down.
Help, support, talk to us
Talk to a human. Every unanswered question is a docs gap we want to close.
The fastest way to reach us is the signup form — it captures who you are and what you're trying to build, and we'll reply with a personal note from the founder. NDA-protected conversations are fine.
For deeper questions: every page on this site links to the underlying capability. If the docs don't answer it, we want to know — that's the gap we'll fill next.
Build systems that can explain themselves later.
Connect an agent, maintain an agentic twin, or replay a historical state. The underlying record stays inspectable from day one.