Alternatives
Products that do what FFlags – Feature flags as code, served from the edge does
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…
- 1
- 2
- 3
- 4
- 5
- 6FI
2017 · featureflags.io
- 7
- 8SO
We just released a major upgrade to SigNoz with support for Logs management based on ClickHouse. Would love to get any feedback from the community here on what you think and any questions you may have for us Many big companies like Uber and Cloudflare have been shifting to ClickHouse as their main workhorse for Logs management seeing much better performance. for e.g Cloudflare recently shifted from Elastic to ClickHouse and are seeing 8x improvement in memory/cpu resource requirement in ingestion. This is our first release with Logs support and we have added support for: - Filtering…
2022 · github.com
- 9
- 101O
2022 · github.com
- 11FF
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
- 12WB
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
- 13YD
If you've built any web-based app in the last 15 years, you probably used something like Datadog, New Relic, Sentry, etc. to monitor and trace your app, right? Why should it be different when the app you're building happens to be using LLMs? So today we're open-sourcing OpenLLMetry-JS. It's an open protocol and SDK, based on OpenTelemetry, that provides traces and metrics for LLM JS/TS applications and can be connected to any of the 15+ tools that already support OpenTelemetry. Here's the repo: https://github.com/traceloop/openllmetry-js A few months ago we launched…
2024 · github.com
- 14
Feature Flag Experimentation made by engineers for engineers
2022
- 15CA
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
- 16
- 17LO
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
- 18WB
Hey hn! I'm one of the co-founders of highlight.io, an open source monitoring tool. Today we're sharing a ClickHouse-based logging solution we've been working on. We wanted to showcase how we built it and share how you could try it out to give feedback. Since we started working on highlight.io, we've been hyper-focused on "cohesion", or ensuring that when you install your monitoring stack, all of the resources in that stack (user interactions, requests, traces, logs, etc.) are connected in a consumable way. We've written up more about our philosophy on this here [1]. We started building…
2023 · github.com
- 19
- 20IB
Read this article by Cloudflare this morning https://blog.cloudflare.com/code-mode/ the main argument being that LLMs are much better at writing typescript code than tool calls because they've seen typescript code many more times. HN Discussion: https://news.ycombinator.com/item?id=45399204 https://news.ycombinator.com/item?id=45386248 Deno provides a great sandbox environment for Typescript code execution because of its permissions system which made it easy to spin up code that only has access to fetch and network calls. Stick an MCP proxy…
Sep 2025 · github.com
- 21QR
QuickBEAM is a JavaScript runtime embedded inside the Erlang/OTP VM. If you’re building a full-stack app, JavaScript tends to leak in anyway — frontend, SSR, or third-party code. QuickBEAM runs that JavaScript inside OTP supervision trees. Each runtime is a process with a `Beam` global that can: - call Elixir code - send/receive messages - spawn and monitor processes - inspect runtime/system state It also provides browser-style APIs backed by OTP/native primitives (fetch, WebSocket, Worker, BroadcastChannel, localStorage, native DOM, etc.). This makes it usable for: - SSR…
Mar 2026 · github.com
- 22FO
2021 · github.com
- 23
- 24FG
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
Ranked by how close each launch is in meaning, then by votes. Refine with a description →