A backend platform in a single binary
Self-hosted: data, auth, multitenancy, plugins and a marketplace. No cloud, no dependencies — download and run.
Latest stable … · Free to self-host. macOS, Linux and Windows, amd64/arm64.
Single binary
Data, REST, auth, realtime, admin — in one file. No Docker, no external DB.
Multi-tenant
Core-level tenant isolation, RBAC and per-collection access rules.
Plugins
A plugin marketplace: installed at runtime, sold per seat, licensed.
Admin built in
A ready SPA frontend and admin console — boot together with the backend.
What is Railbase?
Railbase is a self-hosted backend platform that ships as a single binary. Download one executable and you have authentication, an embedded NoSQL document database (Vault), REST APIs with auto-CRUD, realtime subscriptions, multi-tenancy with role-based access control, file storage, scheduled jobs and a full admin console — no external database and no container stack to operate.
Business capability comes from plugins — helpdesk, inventory, accounting, CMS, document translation and more. They are commercial modules you buy in the built-in marketplace and install at runtime as signed, licensed artifacts. The core is free; you pay only for the plugins you use.
Frequently asked questions
What is Railbase?
A self-hosted backend in a single binary: auth, an embedded NoSQL document store, REST auto-CRUD APIs, realtime, multi-tenancy, file storage, scheduled jobs and an admin console — with no external database to run.
Is Railbase free?
Yes — the core is free to download and self-host on Linux, macOS and Windows, with no usage metering. Commercial plugins are per-seat licenses, and many offer a one-time free trial.
How is Railbase different from Supabase, Firebase or PocketBase?
Like PocketBase, Railbase is one self-hosted binary — no container stack and no vendor cloud. The difference is ready business apps: helpdesk, inventory, accounting, CMS and more install at runtime from a built-in marketplace, so you ship a product, not just infrastructure.
Where is my data stored?
In a single Vault file — an embedded NoSQL document store — on your own server. A backup is a copy of one file, and moving hosts is copying it somewhere else.
How do plugins work?
Plugins are compiled, signed modules sold on the marketplace. Your instance downloads the artifact, verifies its signature and runs it at runtime — no rebuild, no third-party code to vet. Licenses are per seat and managed from your own admin.