Description
FFlags is a feature flag service that follows the OpenFeature standard, so you are not locked into one vendor. Flags are defined in code, and their logic is written in TypeScript, which lets you express complex rules with the full power of the language. The site says flags are served from the edge network using the OpenFeature Remote Evaluation Protocol, which suits global applications. There is no limit on the number of flags or users. Pricing is usage based at $39 per million requests, charged in million-request increments. The product is aimed at developers who want to handle feature flags without building or running the infrastructure themselves. The site says the goal is to simplify feature flag management by rethinking how flags are handled from the ground up. It links to documentation and a blog, and its terms and privacy policy are published on the site.…
Pricing
- Usage based$39per million requests
Highlights
- Feature flags defined as TypeScript code
- OpenFeature compliant with no vendor lock-in
- Served from the edge network
- No limit on flags or users
- Usage-based pricing per million requests
Ratings & Reviews
No ratings yet
Be the first to rate FFlags.
People also visit
FFlags FAQ
What are FFlags?
A feature flag service that serves flags from the edge, with flag logic written in TypeScript.
Is it compatible with OpenFeature?
Yes. The site says FFlags uses the OpenFeature Remote Evaluation Protocol to serve feature flags.
How is it priced?
Usage based at $39 per million requests, charged in million-request increments. There is no limit on the number of flags or users.
Why define flags in code?
The site says flags are defined in code, so you can write complex logic with the full power of TypeScript.
Does it suit global apps?
The site says it uses the edge network to serve flags, which makes it suited to global applications.
What are the best FFlags alternatives?
Popular alternatives to FFlags include Flipt, Abby and FeatBit. See all FFlags alternatives





