Feature flags for every stage of delivery.
From canary releases to kill switches — see how engineering teams use FeatureSignals to ship safer and faster, with zero added latency and complete control.
Release Pipeline
checkout-redesign · production
1% Canary
Internal team + beta users
10% Rollout
10% of US traffic
50% Rollout
50% of all users
100% Launch
Remove flag, archive code
Roll out features gradually. Stop bad releases instantly.
Deploy code to production behind a feature flag, then progressively expose it to users. Start with internal teams, expand to beta users, then dial up to 100% — all without a redeploy.
How it works
Deploy new code behind a feature flag — off by default.
Roll out to 1% of users. Monitor error rates, latency, and business metrics.
Increase rollout: 10% → 50% → 100%. Adjust at any time without a redeploy.
If something breaks, kill the flag in one click. Issue resolved in seconds.
Once fully launched and stable, the AI Janitor removes the stale flag code.
Percentage Rollout
Consistent hashing · MurmurHash3
10.5K
Users receiving
14.5K
Users not receiving
Canary Target
Beta users + EU region · ~5% of traffic
Internal testers and early adopters
European data center users only
Exclude free-tier users
0.12%
Error Rate
42ms
p95 Latency
99.98%
Crash Free
Test in production with real users
Staging environments can't replicate production traffic patterns. Canary releases let you validate new features with a small subset of real users before going wide — with automatic rollback if metrics degrade.
How it works
Target a specific cohort: internal users, beta testers, or a geographic region.
Route a small percentage of production traffic to the new feature path.
Monitor error rates, latency, and business metrics against the control group.
Gradually expand the canary group as confidence increases.
Automated rollback via webhook if health checks fail — no human intervention needed.
Emergency off-switch for any feature in production
When a feature causes issues in production, you don't have time for a rollback pipeline. Kill switches give you instant control — one click, API call, or automated trigger disables the feature globally.
How it works
Every flag is a kill switch. Toggling off instantly returns the default value to all SDK consumers.
Kill via dashboard, API, or automated webhook trigger from your monitoring stack.
Graceful degradation: SDKs receive the off state and your application handles it with sensible defaults.
Every kill action is audit-logged with before/after state, user, and timestamp.
Notify your team via Slack, Datadog, or PagerDuty — webhooks fire on every kill event.
Active Kill Actions
Audit trail · Last 24 hours
jane@acme.com · 8 min ago
Error rate spike to 2.3% in canary group
automation (Datadog) · 47 min ago
p95 latency exceeded 500ms threshold
mike@acme.com · 2 hours ago
Root cause identified and patched
A/B Experiment
pricing-page-v2 · 3 variants · 50/30/20 split
48.2K
Impressions
1,204
Conversions
2.5%
Conv. Rate
Measure what moves your metrics
Ship hypotheses, not guesses. Run A/B experiments directly on your feature flags with weighted variant assignment, impression tracking, and per-environment configuration. No separate experimentation tool required.
How it works
Create an A/B flag with multiple variants and weighted distribution.
Users are deterministically assigned to a variant via MurmurHash3 — consistent across sessions.
Fire impression events from your application to track which variant each user sees.
Measure conversion events against variant assignments to calculate lift.
Combine with targeting rules to run segmented experiments on specific user cohorts.
Switch from LaunchDarkly without rewriting your codebase
The Migration Engine imports your flags, environments, segments, and targeting rules in minutes. OpenFeature-native SDKs mean this is the last migration you'll ever need — future provider changes are a one-line config switch.
How it works
Connect to your existing provider via API key — LaunchDarkly, ConfigCat, Flagsmith, or Unleash.
Run a dry-run preview. See exactly which flags, segments, and rules will be created.
Review the migration plan. Operator mappings, strategy translations, and edge cases are surfaced.
Execute the migration. All configuration is imported while your existing provider stays live.
Swap your SDK initialization to FeatureSignals. OpenFeature means a single config change.
Migration Path
Zero-downtime switchover
GitOps Workflow
PR #312 · feat: add holiday-promo flag · Open
Terraform Configuration
CI/CD Pipeline
Manage flags as code. Review, approve, deploy.
Treat feature flags like the rest of your infrastructure. Version flag configurations in git, review changes through pull requests, and apply through your existing CI/CD pipeline — with full drift detection.
How it works
Define flag configurations as code using Terraform, Pulumi, or Ansible providers.
Open a pull request. Your team reviews flag changes alongside application code.
CI/CD runs a plan: see exactly which flags will be created, modified, or removed.
Merge and apply. Flag state is synchronized with your infrastructure.
Drift detection continuously monitors for discrepancies between IaC and live state.
Ship fast without compromising compliance
Enterprise-grade access controls, audit logging, and compliance readiness — so your platform team can enable developers without losing control. SOC 2, GDPR, and HIPAA ready.
How it works
Assign roles: Owner, Admin, Developer, Viewer — with per-environment permission scopes.
Enable change approval workflows for production environments. Configurable reviewer pools.
Every action is logged: flag creation, toggle, targeting change, approval — with before/after diffs.
Integrate with your identity provider via SAML/OIDC SSO. Enforce MFA across your organization.
Restrict access by IP range, provision users via SCIM, and create custom roles for your needs.
Role-Based Access
Per-environment permissions · 4 built-in roles
| Permission | Viewer | Developer | Admin | Owner |
|---|---|---|---|---|
| View flags | ||||
| Toggle flags | — | |||
| Edit rules | — | |||
| Manage segments | — | — | ||
| Approve changes | — | — | ||
| Manage billing | — | — | — |
Ready to ship safer and faster?
Join engineering teams that use FeatureSignals for progressive delivery, canary releases, A/B testing, and more. Start free — no credit card required.
Free forever for up to 50 flags. No credit card required. Open source under Apache 2.0.