Flagsweep

Flagsweep is a self-hosted FeatureOps layer on top of the feature flags in your cloud. Your flags stay in your cloud's store, Azure App Configuration today and AWS AppConfig soon, and Flagsweep adds what the console lacks: an attributed audit trail, drift detection, locks, protected environments, owners, and retire-by dates.

Your applications keep reading flags from your cloud's store with the SDKs they already use. Flagsweep writes to the same store, and leaves feature filters and variants set in the console as they are.

What it does

• Shows each flag as one row with its state in every environment, and lets you change any environment from the flag's page
• Keeps an audit trail of who changed what and when, which Azure's own revision history does not record
• Marks flags changed in the cloud store directly, and flags switched differently between environments
• Protects environments so only admins can change them, and locks individual flags in the store
• Gives each flag an owner and a retire-by date, 90 days out by default
• Lets people without access to the cloud account see and change flags, with admin and member roles and link-based invitations

Azure App Configuration is supported today. AWS AppConfig is coming soon, and a hosted edition is planned.

Quick start

docker run -d --name flagsweep \
  -p 8080:8080 \
  -v flagsweep-data:/app/data \
  ghcr.io/flagsweep-hq/flagsweep:latest

Open http://localhost:8080, create the admin account, and follow Getting started. To try it without an Azure account, run it in sandbox mode.

Documentation

The documentation is published at https://flagsweep.com/. The pages live in docs/, and the Docusaurus site that renders them, with the landing page and blog, is in website/:

• Installation: the published image, a Docker build, or building from source
• Configuration: settings, running behind a reverse proxy, data and backups
• Connection string encryption: encrypting the stored Azure credentials
• Guides: using Flagsweep, from connecting a store to reading the audit trail

To run the site locally: cd website && npm ci && npm start, then open http://localhost:3000/.

Questions and ideas

Questions, ideas and what you built with it go in Discussions. Bugs go in Issues. Each release is announced in Discussions too, with a thread for feedback.

Development

Flagsweep is a .NET 10 API and a React 19 front end, with SQLite for its own data. Build from source covers running it locally, the Azure App Configuration emulator, and the test suites.

Releasing

Rename the [Unreleased] section of CHANGELOG.md to the new version and date, commit, then tag the commit vX.Y.Z and push the tag. The release workflow publishes the image and creates a GitHub release from that changelog section. Every push to main also publishes an edge image.

License

Flagsweep is licensed under the Apache License 2.0. You can use, self-host, modify and fork it, including inside closed-source and commercial products. Keep the license and NOTICE files when you redistribute it. The license does not cover the Flagsweep name or logo.

Pull requests are welcome. By contributing, you agree to license your contributions under the Apache License 2.0.