What is FlagPulse?
FlagPulse is a self-hostable feature flag management platform aimed at solo developers and small teams. Instead of paying for a hosted flag service or hand-rolling if statements around environment variables, you run FlagPulse alongside your app and get:
- A dashboard for creating projects, environments, and flags
- A small REST API that your services and CI/CD can drive
- A Client SDK API (
x-sdk-keyprotected) that your applications call to evaluate flags - Realtime updates over Server-Sent Events (SSE), so a flag toggle shows up in connected clients immediately
- An audit log of every change, with old/new values
Why FlagPulse
- Fast to stand up. One
docker-compose upbrings up Postgres, Redis, the API, and the dashboard behind Nginx. - No vendor lock-in. Your flag data lives in your own Postgres instance.
- Per-environment isolation. Each environment (e.g.
production,staging) has its own SDK key and its own set of allowed origins, so a leaked staging key can't be used against production. - Cache-first evaluation. Flag reads are served from Redis with a 5-minute TTL and are invalidated immediately on writes, so SDK reads stay fast without going stale.
Who it's for
FlagPulse is intentionally scoped for a single team's use case, not a multi-tenant enterprise rollout — there's no org/workspace layer, and authorization is currently project-ownership based rather than role-based. If that fits how you ship, it should feel very quick to adopt.
Next steps
- Getting Started — run FlagPulse locally with Docker Compose
- Core Concepts — projects, environments, flags, and flag values
- Architecture — how the pieces fit together