Alternatives
Products that do what VoidFlag does
feature flags that NEVER silently break production
- 1
- 2FF
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
- 3FF
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
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13UR
This project is inspired by some of the asserts in Unreal engine. Due to reliance on core_intrinsics it is necessary to develop using nightly Rust, but there are stubs in place so a production build will not require nightly. I recently released version 0.2 which includes no_std support and adds optional log message arguments to the ensure macro.
2024 · github.com
- 14
- 15FI
2017 · featureflags.io
- 16WB
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
- 17
- 18FG
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
- 19LO
Hey everyone, Here is a link to the first version of an on-premise feature flag/toggle system, made with GO, that I developed at the company I'm working at (MEDIGO). It allows you to isolate features within your projects, and enable/disable them in multiple environments with a simple click in a dashboard. For instance if you just developed a new feature and you want to enable it on the testing environment, all you have to do is go to Laika's web page and activate the flag for the feature on this environment. Or if a bug is spotted on a feature already in production, disabling is…
2016
- 201O
2022 · github.com
- 21
Feature Flag Experimentation made by engineers for engineers
2022
- 22
- 23
- 24CA
We've been building Crust (https://crustjs.com/), a TypeScript-first, Bun-native CLI framework with zero dependencies. It's been powering our core product internally for a while, and we're now open-sourcing it. The problem we kept running into: existing CLI frameworks in the JS ecosystem are either minimal arg parsers where you wire everything yourself, or heavyweight frameworks with large dependency trees and Node-era assumptions. We wanted something in between. What Crust does differently: - Full type inference from definitions — args and flags are inferred automatically. No…
Mar 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →