Skip to content
Feature Flags

Ship code behind flags. Release when ready.

Boolean, string, number, and JSON flags with instant toggling. Deploy behind flags and control who sees what — without redeploying.

Get started for free Read the docs
Feature Flags
production
new-checkout
boolean · 100%
ai-assistant
boolean · 25%
dark-mode-v2
boolean · off
checkout-layout
string · "redesign"
Target precisely✦ Release progressively✦ Measure impact✦ Retire cleanly✦
Coming Soon

Schedule flag changes ahead of time.

Plan product launches, maintenance windows, and timed experiments. Set it once and walk away — the change fires at the time and timezone you chose.

Scheduled Change
SCH-2026-0218
PENDING
Target Flag
new-checkout-flow
boolean · production
Action
Enable flag
set to true
Scheduled Activation
Date
Feb 20, 2026
Time
09:00 UTC
Timezone
UTC+0
Countdown ~2 days remaining
Created Feb 18, 2026 Activates Feb 20, 2026
Set date & time
Automate maintenance
Coordinate launches
Timezone aware
terminal
200 OK
Request
curl -H "Authorization: Bearer sk_your_api_key" \
https://flagdash.io/api/v1/flags/new-checkout \
-G -d "user_id=user_42" \
-d "country=US" \
-d "plan=premium"
Response
{
"key": "new-checkout",
"value": true,
"flag_type": "boolean",
"enabled": true,
"matched_rule": "country=US AND plan=premium"
}
Context-Aware API

Evaluate flags with
user context.

Pass user attributes and get precisely targeted flag values. One API call gives you the evaluated result based on targeting rules, rollout percentage, and A/B test assignments.

  • RESTful JSON API with bearer auth
  • SDKs for JS, React, Node, Go & Python
  • Sub-3ms evaluation with consistent hashing
  • Pass any attribute: user_id, country, plan, email

Precise control with targeting & experiments

Show each user the right experience, using rule-based targeting and weighted A/B tests.

Targeting Rules
3 rules active
RULE 1
country equals "US" AND plan in "premium", "enterprise"
Then serve true
RULE 2
email ends_with "@flagdash.io"
Then serve true (internal beta)
eq neq contains in not_in regex gt / lt starts_with ends_with
A/B Testing
experiment
checkout-redesign
string · 2 variations
A Control
50%
value: "classic"
B Treatment
50%
value: "redesign"

Consistent Hashing

Same user_id always maps to the same bucket. Ramping from 10% to 25% adds new users without reassigning existing ones.

Everything you need for safe releases

Decouple deployment from release. Merge and deploy continuously, then choose the moment each feature goes live.

Instant Toggle

Enable or disable any flag with a single click. Changes propagate instantly — no deploy needed.

Percentage Rollouts

Gradually roll out to 1%, 10%, 50% of users. Consistent hashing means ramping up never drops anyone who was already in.

Boolean, String, Number & JSON

Use string, number, or JSON flags for multivariate experiments and complex configuration.

Targeting Rules

Target by country, plan, email, or any custom attribute. Combine conditions with AND/OR logic for precise segments.

A/B Testing

Define weighted variations for experiments. Consistent hashing ensures stable assignment across all evaluations.

Scheduled Changes

Schedule flag changes ahead of time. Plan launches, maintenance windows, and timed experiments automatically.

Beyond the toggle

Operate the entire flag lifecycle.

A release does not end when a flag turns on. FlagDash also handles delivery, evidence, ownership, and cleanup, in every runtime that reads the decision.

01 · Guard

Rollout steps gated on health signals

Advance through traffic steps only when external health signals stay inside your thresholds. Pause safely or roll back to the starting allocation.

02 · Clean up

Lifecycle ownership and code references

Mark temporary flags, assign owners, scan repositories, and see when references are gone so release code does not become permanent debt.

03 · Reuse

Segments shared across decisions

Model audiences once from user and company context, then reuse them in targeting rules without duplicating country, plan, or account logic.

04 · Explain

Evaluation reasons, analytics, and audit

Inspect why a value won, understand exposure, and trace configuration changes without making telemetry load-bearing on the read path.

05 · Deliver

Realtime updates with resilient fallback

Push changes over SSE, reconnect automatically, and keep a safe local fallback when networks or secondary systems are unavailable.

06 · Integrate

SDKs, OpenFeature, CLI, and MCP

Use JavaScript, React, Node, Go, or Python; connect through OpenFeature and OFREP; or operate releases from terminal and agent workflows.

Ready to ship your first flag?

Start using feature flags in under 5 minutes. Free forever for small projects.

Get started for free Read the docs