trailbaseio/trailbase: An open, sub-millisecond, single-executable Firebase alternative with type-safe APIs, built-in WebAssembly runtime, realtime subscriptions, auth, MCP and admin UI built on Rust, SQLite (PG) & Wasmtime.

An open, sub-millisecond, single-executable Firebase alternative with type-safe APIs, built-in WebAssembly runtime, realtime subscriptions, auth, MCP and admin UI built on Rust, SQLite (PG) & W...

Summary

TrailBase is a self-hostable backend packaged as a single executable that bundles an HTTP server, type-safe REST and realtime APIs, authentication, an admin dashboard, and a WebAssembly runtime. It is written in Rust, uses SQLite by default (with experimental Postgres v0.28+ support), and is positioned as an alternative to Firebase-style backends for mobile, web, and desktop apps. The project is marked alpha, the server is licensed under OSL-3.0, and the client libraries are dual-licensed under Apache-2.0.

What it is useful for

TrailBase is useful when an engineer wants to ship an application backend without running a fleet of services. A single binary exposes typed REST endpoints, realtime subscriptions, auth, and an admin UI, with the README citing sub-millisecond latencies that remove the need for a separate caching layer. The built-in WebAssembly runtime lets teams add server-side logic or UI components (the README shows trailbase/auth_ui as an example), and geospatial capabilities are part of the database layer. Pre-built client SDKs are published for JavaScript/TypeScript, Dart/Flutter, Rust, C#/.Net, Swift, Kotlin, Go, and Python, so the same backend can serve web, mobile, and desktop clients from one process.

How engineers can use it

The README documents three install paths: download a pre-built archive from the GitHub releases page for Linux/macOS/Windows, run the installer script curl -sSL https://trailbase.io/install.sh | bash (or the PowerShell equivalent on Windows), or use the trailbase/trailbase Docker image with a local traildepot volume mounted. Running trail run starts the server on localhost:4000, bootstraps a ./traildepot data directory on first start, and prints admin credentials to the terminal for the dashboard at http://localhost:4000/_/admin/. Adding the bundled auth UI is a single command, trail components add trailbase/auth_ui, which mounts a WASM component exposing endpoints such as http://localhost:4000/_/auth/login.

Building from source requires Rust, Node.js, geos, protobuf, and pnpm, plus git submodule update --init --recursive, then cargo build --bin trail. Engineers should weigh the alpha status and the OSL-3.0 license: the maintainers interpret OSL-3.0 as covering only modifications to TrailBase itself rather than applications connecting to it, and direct licensing questions to [email protected]. Detailed configuration, schema definitions, and CLI flags live on the trailbase.io site rather than in the repo, so for anything beyond the steps above the README is the starting point.