Product features
The capabilities that make up Featureflip. Each one is evaluated locally in sub-milliseconds and changes from the dashboard without a redeploy. Explore how each works in depth, then see the integrations that reach them from your editor, your Terraform, and your CI.
Percentage rollouts
Ramp a feature from 1% to 100% of users on a slider. The percentage is a dashboard setting, not a redeploy, and deterministic sticky bucketing keeps each user in place as you climb.
Sticky bucketing · sub-ms local eval · live over SSE
Explore the feature →
Feature flag targeting
Serve a variation to the users who match an attribute rule and the default to everyone else. Combine conditions with AND and OR, reuse a segment across flags, and change who is targeted from the dashboard.
Attribute rules · reusable segments · per-environment
Explore the feature →
Environments
Keep development, staging, and production fully isolated. Each environment has its own SDK key and its own flag states, targeting rules, and rollout percentages, so a feature is on in one and off in another with only the key telling your deployments apart.
A key per environment · isolated config · promote without a redeploy
Explore the feature →
Scheduled changes
Queue a flag to turn on or off automatically at a future time and let Featureflip flip it for you. No cron jobs, no CI wiring, no one awake for the cutover — the change applies server-side, streams to your SDKs live, and is recorded in the audit log under your name.
Future on/off · per environment · cancel while pending · Team plan and up
Explore the feature →
Flag lifecycle
Give each flag an expiry date and, on Pro and up, an owner. When a flag expires or stops deciding anything, a cleanup email goes out on Team and up, and a GitHub Action opens the pull request that removes its code.
Expiry dates · flag owners · cleanup emails · removal by PR
Explore the feature →
Webhooks
Send a signed HTTP request to your own endpoint whenever a flag or its configuration changes. Start a deploy, post to a chat channel, or refresh a cache, with retries and a delivery log behind every event.
HMAC-signed · retries and redelivery · dashboard, API, MCP, Terraform
Explore the feature →
Single sign-on
Let your team sign in through Okta, Microsoft Entra ID or any OpenID Connect provider. New people join with a default role, and you can require SSO so your identity provider is the only way in.
OIDC · automatic provisioning · require SSO · Business plan
Explore the feature →
SDKs
Official libraries for 13 languages and frameworks. Server SDKs evaluate flags locally in sub-milliseconds, every SDK streams live updates over SSE, and the same flag returns the same answer on every platform.
13 SDKs · local eval · one consistent API
Explore the feature →
Audit log
Every change to a flag, recorded automatically: who made it, what moved from and to, and when. Read it organization-wide with filters or per flag on a History tab, with retention from 7 to 365 days.
Automatic · before-and-after values · filterable
Explore the feature →
REST API
Everything the dashboard does, over HTTP. Create flags from CI, toggle them from a deploy script, and build internal tooling on the same configuration your team edits, with idempotent creates and rate-limit headers on every response.
Full management surface · token auth · included on every plan
Explore the feature →
Integrations
Featureflip also works from the tools you already run. Each of these is included on every plan, and the cards below point straight at the docs.
MCP server
Manage flags from Claude Code, Cursor, Copilot, and other agents that speak the Model Context Protocol. The server exposes flag creation, targeting, rollouts, and staleness as tools, so the editor you are already in can create a flag and ramp it without you opening the dashboard.
Claude Code · Cursor · Copilot · Cline
Read the docs →
Terraform provider
Declare projects, flags, targeting rules, segments, and webhooks in HCL, then apply them alongside the rest of your infrastructure. Flag changes get reviewed in a pull request the same way a change to the rest of your infrastructure would be, promote cleanly between environments, and stay reproducible.
On the Terraform Registry · reviewed in pull requests
Read the docs →
Flag cleanup Action
A GitHub Action that opens one reviewable pull request per dead flag, deleting the code path across thirteen languages with AST transforms and no LLM. The same repository always produces the same diff, and merging the pull request archives the flag.
13 languages · no LLM · archives on merge
Read the docs →
Looking for the patterns, not the pieces?
The use-case guides show these features working together on real problems — progressive rollouts, kill switches, entitlements, and more. The docs cover the full reference.
Ready to ship behind a flag?
Start on the Free plan — 10 flags, 2 environments, no credit card.