Flagsmith
Self-HostedOpen-source feature flagging and remote config platform
Overview
Flagsmith is an open-source feature flagging and remote config platform that helps teams manage feature rollouts, reduce release risk, and iterate faster. It supports multi-environment workflows (dev/staging/prod), user segmentation for targeted access, A/B testing, and real-time updates. Deploy via Docker, Kubernetes, or cloud providers (AWS/GCP) for self-hosted control, or use the managed SaaS. Integrates with Jira, Slack, and CI/CD tools. Features include kill switches, gradual rollouts, and audit logs to track changes.
Self-Hosting Resources
Below is a reference structure for docker-compose.yml.
⚠️ Do NOT run blindly. Replace placeholders with official values.
version: '3'
services:
flagsmith:
image: <OFFICIAL_IMAGE_NAME>:latest
container_name: flagsmith
ports:
- "8080:<APP_INTERNAL_PORT>"
volumes:
- ./data:/app/data
restart: unless-stopped Key Features
- Feature flag rollouts & kill switches
- Remote configuration management
- User segmentation and A/B testing
Frequently Asked Questions
? Is Flagsmith hard to install?
No—Flagsmith offers simple self-hosting via Docker Compose, Kubernetes manifests, or cloud deployment guides. Step-by-step docs cover setup on AWS, GCP, or local servers, making it accessible for most dev teams.
? Is it a good alternative to LaunchDarkly?
Yes—Flagsmith provides core feature flagging capabilities (rollouts, kill switches) for free (self-hosted) vs LaunchDarkly's paid tiers. It’s open-source, allowing customization, whereas LaunchDarkly is proprietary.
? Is it completely free?
The self-hosted core (MIT license) is fully free. Managed SaaS plans have paid tiers for enterprise features like SSO, audit logs, and dedicated support, but self-hosted users get all basic and advanced feature flagging tools at no cost.
Top Alternatives
People Also Ask about Flagsmith
Tool Info
Pros
- ⊕ Self-hosted option for full data control
- ⊕ Open-source (MIT license) with no vendor lock-in
- ⊕ Integrates with Jira, Slack, and CI/CD pipelines
Cons
- ⊖ Requires server setup for self-hosted deployment
- ⊖ Advanced features (like SSO) need paid SaaS tiers
- ⊖ Learning curve for complex segmentation rules