Skip to content
FlagSwiftDocs
Documentation

Release with control.

Feature flags, self-hosted or hosted. Learn it, build with it, run it.

Start here

Everything FlagSwift does

Each tile opens the guide or page that covers it.

Tour the console

One page per screen, in the same groups as the console sidebar.

All console pages

Pick your path

Works with your stack

Compare SDKs

How it fits together#

You create flags in the console, choose who gets them in each environment, and change them without a deploy. Your apps read the result through an SDK or the HTTP API using an API key. Browsers and mobile apps get only the outcome for one person. Backend services download the flag configuration and evaluate it locally, so a check is an in-memory lookup with no network call.

FlagSwift comes in two editions. With Enterprise, everything stays on your infrastructure: flags, keys, the audit log and the metrics live in your own PostgreSQL or MongoDB. Commercial is the hosted service, with Free, Pro, Business and Enterprise plans. See Editions.

Keep exploring

Ready to try it? Open the console.

What is not available yet#

These pages describe what is built today. Not available yet: single sign-on, multi-factor sign-in and SCIM, service accounts, per-organization webhooks, OpenTelemetry export, experiments with sample-size planning, automated rollbacks, AI-assisted flag management (planned: stale-flag cleanup, rollout advice, plain-language changes and release summaries), an OpenFeature provider, and SDKs for Ruby and Kotlin.