Mirabase

MiraBase: one backend, a private database for every user, tenant and agent. THE PROBLEM A solo developer building a SaaS, team workspace or multi-agent app needs accounts, permissions, records, files, search, schema changes and recovery. Giving each customer or agent private storage should not mean deploying another backend for every database. And once every user has their own database, harder problems appear: running thousands of files cheaply, keeping authority unambiguous, surviving partial failure across files, and trusting a native engine inside your process. HOW WE SOLVED IT - Cost: Turso runs in-process through Go's database/sql. One HTTP server with bounded shared services manages many database files, so there is no process, scheduler or JavaScript VM per database. - Authority: ownership, grants, collection rules and privileged SQL are separate surfaces. Request context is immutable, and unauthorized or contradictory selection is refused with no silent fallback to primary storage. - Partial failure: generation, schema and policy guards, reviewed schema plans, rollouts that show mixed revisions, durable jobs and idempotency receipts. We do not claim cross-file ACID. - Trust: the native engine is pinned by compiled-in digests, and modified payloads are refused. A separate Quint-based Formal Verification harness backs security claims with executable evidence. WHAT WE BUILT Extending PocketBase with Turso, we added: - Shared, per-user, per-tenant and per-agent databases, provisioned automatically, with tenant memberships, invitations, scoped grants and credentials, and agent identities. - Four search modes: vector, full-text, hybrid and fuzzy, with budgets and deadlines. - Schema plans, templates and rollouts; durable change history, record sync and live queries; backups, export/import and durable jobs. - Agent workspaces with historical snapshots and restoration. - A PostgreSQL wire gateway (TLS, SCRAM, prepared statements), tested with node-postgres. - PocketBase adoption with staged cutover, plus JavaScript/TypeScript and Dart clients. - Formal Verification: 17 tools, 15 starter models, a 42-claim catalog. EVIDENCE Recorded Windows runs show 5,236 test passes, 23 package checks and four SDK transport tests. Known limits are stated openly: managed-record rule parity, operator-only workspaces and application isolation are unfinished. Self-hosted only; no cloud offering. Code: github.com/lordolami/mirabase Formal Verification: github.com/lordolami/formal-verification Demo: youtu.be/PVRYAADs-EQ