How do I deploy Spicedb on Railway?

You can deploy Spicedb on Railway by clicking the "Deploy Now" button on this page. Railway will automatically set up all the necessary services and configurations for you.

What are the system requirements?

Railway handles all the infrastructure requirements. You only need a web browser to deploy and manage your application.

Is this template free to use?

Yes, this template is free to use within your existing Railway account.

Can I customize this template?

Yes, you can fully customize this template. After deployment, you will have full control of what you've deployed in your Railway project.

How do I get support for this template?

You can get support through our community forum: spicedb-95f71451, or click "Get template help" for this template for more assistance.

Deploy and Host Spicedb on Railway

What is Spicedb?

SpiceDB is an open-source, Google Zanzibar–inspired permissions database for building fine-grained, real-time authorization. You define a schema describing resources and relationships, then your apps write relationships and ask “can user X do action Y on resource Z?” via APIs and client libraries. (AuthZed)

About Hosting Spicedb

Hosting SpiceDB mainly involves running the SpiceDB service plus a supported datastore for durable relationship storage (commonly PostgreSQL for single-region setups, or CockroachDB/Spanner for higher throughput or multi-region needs). You’ll configure environment variables for datastore connection info and service ports, run migrations/bootstrapping as needed, and ensure your deployment has health checks, logs, and a plan for scaling. If you scale to multiple SpiceDB instances, you’ll also consider how requests are dispatched across instances and monitor performance. (AuthZed)

Common Use Cases

Fine-grained RBAC/ABAC for SaaS apps (orgs, teams, roles, resources, and scoped permissions)
Document/project sharing (“user can view/comment/edit this file/project because of group membership or explicit share”)
Entitlements and feature access (“who can access feature X for account Y, with hierarchy and exceptions”)

Dependencies for Spicedb Hosting

A supported datastore (typically PostgreSQL; alternatives include CockroachDB, Spanner, MySQL with caveats) (AuthZed)
Environment variable / secrets management for connection strings and config (Railway Docs)

Deployment Dependencies

SpiceDB documentation (overview / getting started): (AuthZed)
SpiceDB datastores (what DBs are supported and when to use them): (AuthZed)
Railway environment variables / config: (Railway Docs)

Implementation Details

If you’re using Railway Postgres, you’ll typically:

Provision a Postgres service in the same Railway project
Set SpiceDB datastore config via Railway Variables (e.g., a Postgres connection URI)
Expose SpiceDB’s API port(s) via Railway’s service settings
Add a liveness/readiness check endpoint (or TCP check) and monitor logs/metrics

(Exact variable names/flags depend on which SpiceDB image/version you deploy and how you choose to pass configuration—flags vs env vars—so it’s best to follow the datastore and configuration sections in the SpiceDB docs.) (AuthZed)

Why Deploy Spicedb 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.

By deploying Spicedb on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.