InvariantDB is the temporal-truth runtime. InvariantDB is the AI memory platform built on it. StaticOwl is the deterministic publishing platform built on it. Three distinct surfaces, three buyer profiles — one engineering team, one engine.
The substrate brand and the flagship product brand are the same — InvariantDB — because compliance buyers are looking for "the database that proves things," and that's the substrate sold as itself. InvariantDB and StaticOwl are opinionated platforms that build on the substrate for different audiences.
The three pieces have radically different buyers, sales motions, and price points. Forcing them under one brand creates marketing mush. Splitting them under one substrate creates a coherent ecosystem.
A bitemporal graph runtime with a tamper-evident audit chain. Every fact has both valid time and transaction time; every mutation is signed into a SHA-256 chain; every primitive (sort, merge, audit-link, span correctness) has a formal proof in the invariant catalog. Cypher-queryable, Raft-replicated, formally verified where it matters.
Long-term memory for LLM agents. Bitemporal, graph-shaped, MCP-native. Devs sign up,
install the SDK, and start writing/reading agent memories in minutes. Beneath the
memory.remember() / memory.recall() API is a multi-tenant
InvariantDB cluster — but the developer experience hides the runtime.
A static-site / content engine where the source is a graph, not a folder of Markdown. Deterministic compiles from the graph state, lineage-tracked rebuilds, time-travel previews, explainable dependency invalidation. Content teams author in StaticOwl; the InvariantDB substrate gives every publish a signed receipt.
The three brands aren't fenced off from each other — they share an engine, and that creates real adoption flywheels.
The pattern is what worked for HashiCorp (one runtime, many opinionated products), MongoDB (engine + Atlas), Elastic (engine + Kibana). One foundation, many surfaces, multiple buyers.
The three surfaces speak in different registers. Same engineering integrity, different posture.
Substrate gravitas. Compliance language. Whitepapers, SOC 2 attestations, analyst briefings. Voice: "the database that proves things."
Developer energy. Technical-but-accessible. Docs-first, conference talks, GitHub. Voice: "memory that remembers when, not just what."
Tooling clarity. Editor-friendly. Visual diffs, build-output streams. Voice: "publishing you can audit."
None of the three are "the playful one." All three carry the substrate's integrity. They differ in register, not seriousness.