Show HN: FFlags – Feature flags as code, served from the edge

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 enterprise slop. You're not tied to my platform if you want to move.

3. Performance: It uses an edge network to serve the flags, which keeps the wall-time latency low (sub-25ms) for globally distributed applications.

I was trying to avoid the heavy cost and complexity of existing enterprise tools while still getting better performance than a simple self-hosted solution.

There's a generous free tier ($39 per million requests after that, with no flag/user limits). I'm looking for feedback on the developer experience, the "flags-as-code" approach, and any technical questions you might have.

Thanks for taking a look.

Show HN: FFlags – Feature flags as code, served from the edge
fflags.com

I am probably not directly an intended user but I sure would be glad to understand what this is (as an amateur dev)

If you have any kind of back-end infrastructure, it'd seem trivial to implement this yourself. Doing it yourself also allows you to make the feature flags more controlled, e.g. by some flag associated with the current user such as opting into experimental features.

For efficiency, I'd also want to batch a bunch of such flags together, so e.g. when a use logs in they get a list of enabled features that gets cached locally, rather than having to query each and every one via REST.

So I'd echo the question, what problem is this solving?