Frequently Asked Questions
What Trubase DB is, where the build stands, and why rebuilding the engine is the only way to make backends mintable.
When you mint a Trubase backend, you don't get a connection to a shared cluster. You get a complete, isolated Postgres universe — wire protocol, SQL engine, transactions, its own catalogs and roles, its own timeline in storage. We call it a "backend" because it's the full thing, not a connection string into somebody else's instance — and because it's a value: minted in milliseconds, branched like git, asleep at zero cost.
Because a backend is a Tokio async task weighing kilobytes, not an OS process weighing 10–30MB. Tokio's work-stealing scheduler spreads tasks across every core; tasks that are waiting cost almost nothing. An idle backend isn't even a task — it's a timeline record plus cold bytes on object storage. RAM only pays for the backends that are awake right now.
Pre-launch, and we're honest about what that means: the design phase is complete — the architecture, the storage model, the wake path, and the full engineering documentation corpus are written — and the engine is being built in public against it. The first artifact is the proof machinery itself: a harness that runs PostgreSQL's own test suite against the engine and publishes the pass rate as a live public scoreboard.
Because the process model is load-bearing. The C engine assumes fork(), shared memory segments, blocking disk I/O, and process-level isolation — every subsystem is built on those assumptions. You cannot bolt a task runtime onto it from outside. And it's a pure rewrite — hand-written safe Rust, no C in the address space, no mechanical translation.
Branching: zero bytes are copied. A branch is a new timeline record pointing at the parent's copy-on-write layers — a metadata write, milliseconds. Scale-to-zero: when a backend goes idle, its tasks drop and their memory is reclaimed. State persists on object storage. The wake begins during the connection handshake — so suspended and running are indistinguishable to the client.
We're building in public and will onboard from the waitlist in small batches once the engine crosses the compatibility bar. Join the waitlist, or write to olamilekan@trubase.dev if you're building an agent platform or per-tenant product and want to be a design partner.
Yes — we're talking to seed-stage investors and advisors who invest in infrastructure. The demand curve (agents minting backends) is arriving faster than any process-per-connection architecture can serve it, and the engine that serves it has to be built the way we're building it. For inquiries: olamilekan@trubase.dev.
That's the bar. Compatibility is a number, not an adjective. The bar is 100% of Postgres's observable behavior — wire protocol, SQL semantics, catalogs, error codes — measured by running PostgreSQL's own 200,000-test suite, with the pass rate published continuously. What's excluded: loading C extension binaries — the capabilities that matter are rebuilt natively in the engine.