Self-hosting Flipt the easy way
Yulei ChenFlipt is an open-source feature flag tool that lets you manage feature rollouts, A/B tests, and remote configuration without relying on expensive SaaS platforms like LaunchDarkly or Split. Self-hosting means full control over your data and zero per-seat pricing.
Sliplane makes self-hosting painless. With one-click deployment, you can get Flipt up and running in minutes - no server setup, no reverse proxy config, no infrastructure headaches.
Prerequisites
Before deploying, ensure you have a Sliplane account (free trial available).
Quick start
Sliplane provides one-click deployment with presets.
Deploy Flipt >- Click the deploy button above
- Select a project
- Select a server (If you just signed up you get a 48-hour free trial server)
- Click Deploy!
About the preset
The one-click deploy above uses Sliplane's Flipt preset. Here's what it includes:
- Official Flipt Docker image (
flipt/flipt) - Specific version tag for stability
- Persistent storage mounted to
/var/opt/fliptfor the SQLite database and configuration - Port 8080 exposed for the web UI and API
Flipt stores its data (flags, segments, rules) in a SQLite database by default. The persistent volume ensures your feature flags survive container restarts and redeployments.
Next steps
Once Flipt is running, access it using the domain Sliplane provided (e.g. flipt-xxxx.sliplane.app).
No default credentials
Flipt ships with no authentication enabled by default - you can access the UI right away. If you want to lock it down, configure authentication via environment variables:
| Setting | Description |
|---|---|
FLIPT_AUTHENTICATION_REQUIRED | Set to true to require authentication |
FLIPT_AUTHENTICATION_METHODS_TOKEN_ENABLED | Set to true to enable static token auth |
See the Flipt authentication docs for all available methods including OIDC and GitHub.
Key environment variables
You can customize Flipt's behavior by adding environment variables in your Sliplane service settings:
| Variable | Default | Description |
|---|---|---|
FLIPT_LOG_LEVEL | info | Log verbosity (debug, info, warn, error) |
FLIPT_DB_URL | file:/var/opt/flipt/flipt.db | Database connection string |
FLIPT_CORS_ENABLED | false | Enable CORS for the API |
FLIPT_STORAGE_TYPE | database | Storage backend (database, git, local, object) |
Logging
Flipt logs to stdout by default, which works well with Sliplane's built-in log viewer. Adjust the log level with FLIPT_LOG_LEVEL if you need more or less detail. For general Docker log tips, check out our post on how to use Docker logs.
Troubleshooting
If Flipt isn't starting properly, set FLIPT_LOG_LEVEL to debug for detailed output. Common issues include database permission errors (check your volume mount) and port conflicts. The Flipt configuration reference covers all available settings.
Cost comparison
You can also self-host Flipt with other cloud providers. Here is a pricing comparison for the most common ones:
| Provider | vCPU | RAM | Disk | Monthly Cost | Note |
|---|---|---|---|---|---|
| Sliplane | 2 | 2 GB | 50 GB | €22.80 | Flat rate, free egress, SSL included |
| Fly.io | 2 | 2 GB | 40 GB | ~$17.83 | Disk and bandwidth billed separately |
| Render | 1 | 2 GB | 40 GB | ~$35 | 5 GB bandwidth included on Hobby; disk billed separately |
| Railway | 2 | 2 GB | 40 GB | Up to ~$66 | Usage-based; Pro required for a 40 GB volume |
Click here to see how these numbers were calculated.
Prices checked July 19, 2026. Assuming an always-on instance running 730 hrs/month, Germany/Amsterdam where regional pricing applies, excluding VAT and egress.
- Sliplane: Base server with 2 vCPU, 2 GB RAM and 20 GB storage = €17.80/month; the 50 GB storage tier adds €5 -> €22.80/month. Unlimited services, free egress and SSL are included.
- Fly.io: in Amsterdam,
shared-cpu-2xwith 2 GB RAM = $11.83/month + 40 GB volume × $0.15/GB = $6 -> ~$17.83/month. Egress is billed separately at $0.02/GB in Europe. - Render: closest match is Standard ($25, 1 vCPU / 2 GB) plus 40 GB disk × $0.25/GB = $10 -> ~$35/month. A Hobby workspace includes 5 GB bandwidth, then charges $0.15/GB. Stepping up to Pro compute (2 vCPU / 4 GB) costs $85/month plus disk.
- Railway (Pro plan): at full resource usage: CPU 2 × $20/vCPU/month = $40; RAM 2 × $10/GB/month = $20; volume 40 × $0.15/GB/month = $6 -> up to ~$66/month. Actual CPU and RAM charges depend on usage. A 40 GB volume requires Pro; its $20/month subscription is a minimum commitment that counts toward usage, not an additional charge. Egress is $0.05/GB.
Bandwidth costs can add up fast on usage-based providers. Use our bandwidth cost comparison tool to see what your egress would cost on each platform.
Move the slider or play the animation to compare monthly egress costs. Sliplane stays free as traffic grows.
Egress only, excluding compute and storage. Based on public US/European rates checked July 19, 2026. Render includes its first 5 GB per month. Sliplane egress is free, subject to the Fair Use Policy.
FAQ
What can I use Flipt for?
Flipt lets you toggle features on and off without redeploying your app. Common use cases include gradual rollouts, A/B testing, kill switches for broken features, and environment-specific configuration. It supports boolean flags, multi-variant flags, and percentage-based rollouts.
Can I connect Flipt to an external database?
Yes. By default Flipt uses SQLite, but you can switch to PostgreSQL, MySQL, or CockroachDB by setting the FLIPT_DB_URL environment variable. For example, use postgres://user:pass@postgres.internal:5432/flipt to connect to a PostgreSQL instance running on the same Sliplane server.
How do I update Flipt?
Change the image tag in your service settings on Sliplane and redeploy. Check Docker Hub for the latest stable version.
Are there alternatives to Flipt?
Yes, popular options include LaunchDarkly (fully managed, per-seat pricing), Unleash (open-source with hosted option), and Flagsmith (open-source with cloud offering). Flipt stands out for being fully open-source with no seat limits or usage restrictions.
Does Flipt support GitOps workflows?
Yes. Flipt can read feature flag definitions from a Git repository instead of (or in addition to) its database. This lets you keep your flags as code, review changes via pull requests, and use your existing CI/CD pipeline. Set FLIPT_STORAGE_TYPE to git and configure the repository URL to enable this.
