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

Show HN (score: 5)
Found: August 04, 2025
ID: 676

Description

Other
Show HN: FFlags – Feature flags as code, served from the edge 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 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.

More from Show

Show HN: SmokeVPN – All-in-One WireGuard VPN Hub – Switch Exits in Realtime

Show HN: SmokeVPN – All-in-One WireGuard VPN Hub – Switch Exits in Realtime I have started developing a prototype of a WireGuard VPN hub, where I could set a custom exit to a specific device, for example, my TV box would use a VPN in Germany, while my desktop a VPN is Serbia and I could switch the exit in realtime without having to stop the VPN connections and consequently no disconnections (ssh, etc).<p>The project grew, and I ended up adding SOCKS5 and HTTP proxy, Tor exits, exit pools, random exits, timed exits, and exits&#x2F;routes based on domains or IP addresses. I also added an in-house DNS with several default block lists (malware, gambling, social media, etc.)<p>I found this project to have potential and decided to commercialize it, Smoke VPN was born.<p>The logs live entirely on the RAM, and I plan to open-source the full stack as soon as I get feedback from real users, people like you...<p>Can you please try the project for free for 7 days or 50 GB (whichever comes first)?<p>You don&#x27;t need an account, email or password and you can add up to 10 devices.<p>Real feedback is truly welcome!

No other tools from this source yet.