One backend per ___.
Containers made compute disposable. Trubase does the same for backends. Here's where that changes everything.
Every agent gets its own backend
Every agent invocation gets its own isolated Postgres backend — a complete engine running as a Tokio async task. Branch from a template in milliseconds. The agent mutates state freely without touching shared tables. When done, dispose.
trubase branch template-api --name agent-session-7291✓ minted — zero bytes copiedReal physical isolation, not a row in a shared table
Give every SaaS user their own physical Postgres backend. Stop relying on tenant_id columns and policy workarounds. Because backends are tasks over copy-on-write timelines, millions of tenant backends share base storage and cost $0 when idle.
trubase branch template-saas --name user-8291✓ minted — zero bytes copiedBranch your backend like you branch code
Working on a feature? Branch the backend. Trying a migration? Branch first. Something broke? Dispose the branch. Your backend workflow matches your code workflow.
trubase branch production --name feature/new-auth✓ minted — zero bytes copiedThe backend is the workflow state
Branch at step 1. Run steps 2 through 10. If step 7 fails — dispose the branch. No saga pattern. No compensation transactions. No manual rollback. The backend IS the workflow state.
trubase branch production --name pipeline-run-4421✓ minted — zero bytes copiedNo more flaky tests from shared state
Every test suite gets its own backend. Branch from a known fixture state in milliseconds. Run tests in parallel — complete isolation. No cleanup scripts. No shared test databases.
trubase branch test-fixtures --name ci-run-1847✓ minted — zero bytes copiedEvery PR gets its own backend
Every pull request gets its own preview backend. Branch from production. Test migrations against real constraints, real state. Merge or close — the backend follows the PR.
trubase branch production --name pr-2847-preview✓ minted — zero bytes copied