Deploy file-db
file-db is a self-hosted SQLite management service with built-in visual UI
file-db
Just deployed
/data
Deploy and Host file-db on Railway
file-db is a self-hosted SQLite management service with a built-in visual studio. Each database is a single .db file stored on a Railway volume. Services in your project connect via HTTP using a shared admin token — no separate database infrastructure needed.
About Hosting file-db
Hosting file-db on Railway requires a single service with a persistent volume mounted at /data. All SQLite databases are stored as .db files on that volume. The app exposes an admin dashboard for browsing, querying, and managing databases, protected by a token-based auth layer. A SESSION_SECRET is used to sign session cookies. Both secrets are auto-generated on deploy. The service runs a standalone Next.js server and is accessible over a Railway-generated HTTPS URL.
Common Use Cases
- Cross-service shared state — multiple Railway services write and read a single SQLite file over HTTP without running Postgres
- Lightweight job queues & feature flags — store ephemeral application state in a durable flat file with zero ops overhead
- Internal admin tools — visually browse and query SQLite databases produced by your backend services, directly in the browser
Dependencies for file-db Hosting
- A Railway persistent volume mounted at
/datato store.dbfiles across deploys ADMIN_TOKENenvironment variable shared with any service that connects to the file-db API
Deployment Dependencies
- file-db on GitHub
- Railway Volumes documentation
- Outerbase Studio (upstream) — the open-source SQL viewer this project is built on
Implementation Details
Services connect to file-db by posting SQL to the query API:
Why Deploy file-db on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
Template Content
file-db
0xdps/file-db