Alternatives
Products that do what FlagSwift does
Ship fearlessly, rollback instantly
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8FF
Hey all, I'm the founder of Flipt, an open-source (https://github.com/flipt-io/flipt) feature flag tool that I (and others) have been working on for the past few years. About a year or two ago we added support for serving flag state from various non-relational declarative stores like Git, OCI, Object Store, etc. Many of our users came to love the git-backed storage, as it allows them to keep their feature flags close to their code in there organization's repos. But they had one (rather large) ask, and that was the ability to use the UI to manage flag state changes and…
2024 · flipt.io
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
Feature Flag Experimentation made by engineers for engineers
2022
- 17
- 18WB
Hi. We just open sourced Bullet Train, a Feature Flag and Remote Config platform. It's a collection of tools: server API, admin front end and clients for a bunch of different platforms. Together they allow you to control feature flags and remote config across projects, environments and users. We realised that we were building ad-hoc feature flag stuff into individual projects over and over, so we had a look around to see if there was a way of doing this in a more formal manner. There are a few commercial solutions around but they were quite expensive and seemed to be aimed more at the…
2018
- 19FF
Hi HN, I'm the creator of FFlags. I built this because I wanted a feature flagging system that gave me the performance and reliability of an enterprise-scale solution without the months of dev time or the vendor lock-in. The core ideas are: 1. Feature Flags as Code: You define your flag logic in TypeScript. This lets you write complex rules, which felt more natural as a developer myself than using a complex UI for logic. 2. Open Standard: The platform is built on the OpenFeature standard (specifically the Remote Evaluation Protocol). The goal is to avoid vendor lock-in and the usual…
2025 · fflags.com
- 20
- 21FG
Why? - Decouple application deployment from releases How it works: - Make changes to your features and segments (YAMLs) via Pull Requests - Generate datafile (JSON file) in CI/CD workflow and upload to your CDN - Fetch datafile in your application runtime and consume with SDKs Supports: - Feature flags: boolean flags - Experimentation: a/b tests - Segments: targeting traffic with conditions - Variables: namespaced under each feature and conditional - Gradual rollouts: avoid big bang releases, go from 0% to 100% - Consistent bucketing: same user sees same variation - Multiple…
2023 · featurevisor.com
- 22
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →