Deploy and Host Flipt Local on Railway

Flipt is an open-source feature flag and A/B testing platform. This template runs Flipt v2 in local-first mode using Git-native storage instead of an external database. Flag data is persisted to a Railway volume with file permissions pre-configured for Flipt's non-root user.

About Hosting Flipt Local

Flipt Local stores all flag definitions, segments, and rules on the local filesystem rather than requiring a separate database or cache layer. This template extends the official Flipt v2 image to handle Railway's volume permission model, where volumes mount as root but Flipt runs as a non-root user. After deploying the service, you attach a persistent volume at /var/opt/flipt and the container handles ownership correction at startup. Authentication is not configured by default, so you should either place the instance behind a private network or enable one of Flipt's built-in auth methods.

Common Use Cases

• Feature flagging for small teams or solo projects that don't want to manage a database alongside their flag server
• Internal tooling where Flipt sits behind a private network like Tailscale and serves flags to other services in the same Railway project
• Staging or development environments where you want quick, disposable feature flag infrastructure with persistent state

Dependencies for Flipt Local Hosting

• A Railway persistent volume mounted at /var/opt/flipt
• A private network or authentication method if the instance will be publicly reachable

Deployment Dependencies

• Flipt v2 documentation
• Flipt authentication configuration
• Flipt environment variable reference

Why Deploy Flipt Local 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 Flipt Local on Railway, you are one step closer to supporting a complete full-stack application with minimal burden.