Deploy and Host Voltius Server on Railway

Voltius Server is the self-hosted sync backend for Voltius — a Rust/Axum API with Postgres behind it, handling account sync, teams, team vaults, and terminal sharing. Deploy it on Railway to run your own instance instead of using the hosted service.

About Hosting Voltius Server

Voltius Server is a small Rust/Axum API service backed by Postgres. It exposes the sync endpoints the Voltius desktop client talks to: account auth (JWT), encrypted vault sync, team management, and terminal-session sharing. Database migrations run automatically on every boot, so there's no manual setup step after the first deploy. Self-hosting unlocks every paid feature automatically — teams, team vaults, terminal sharing, audit logs — with no tier enforcement, no trial countdown, and no billing configuration to do. The server is AGPLv3-licensed.

Why Deploy Voltius Server on Railway?

Railway provisions the Postgres database alongside the server and wires DATABASE_URL between them automatically, so there's no separate database host to set up or connection string to hand-copy. JWT_SECRET is generated for you at deploy time. Railway builds straight from the repo's Dockerfile, so updates are a redeploy, not a manual rebuild-and-push. This gets you a private, fully-featured Voltius instance running in a couple of minutes, without managing a VM or writing your own compose file.

Common Use Cases

Running a private Voltius instance for yourself or a small team, with team vaults and terminal sharing enabled by default
Self-hosting for data residency or compliance reasons instead of using the hosted voltius.app service
A throwaway/staging instance to test a Voltius client build against a real server before pointing it at production

Dependencies for Voltius Server Hosting

PostgreSQL — provisioned automatically by this template; stores accounts, vaults, and sync state
JWT_SECRET — generated automatically on deploy; signs session tokens
Nothing else is required to start. Optional integrations (email via Resend, custom CORS origins, admin dashboard) can be added later — see the environment variable reference