Open source, Apache-2.0

Feature flags
at the edge.

Run it free on Cloudflare Workers, or as one container on any host. Read flags from any OpenFeature SDK, and give your team its own sign-ins and roles.

new-checkout0 of 40 raised

Drag the rollout. The same visitors stay raised as it climbs.

Works today with these languages, each through its own OpenFeature provider:

  • Go
  • Java
  • Python
  • .NET
  • Ruby
  • Rust
  • JavaScript
The Flaghoist rule builder, showing a targeting rule that serves the EU cookie banner to visitors whose country is DE, FR, ES or IT.

The dashboard ships with the server.

One deploy brings up the OFREP read API, the admin API and this, at/admin, inside your own infrastructure. There is no second service to run and no vendor console to log into.

The rule you just built in the hero is the same rule shape this editor writes, evaluated by the same engine.

Built to be owned, not rented.

Free when nobody is asking

On the Cloudflare Workers free plan it scales to zero: no always-on process, no database instance, no monthly floor. Anywhere else, it is one small container.

Multiple languages, on day one

The read path implements OFREP, so Go, Java, Python and .NET work through their own OpenFeature providers. We ship no SDKs.

Point it at your database

A storage adapter is four methods. Cloudflare KV, Redis, Postgres and SQLite ship today, and a conformance suite proves any adapter you write.

Targeting that holds still

Sticky SHA-256 rollouts keep the same users in the same bucket across deploys. Ordered rules, first match wins.

One deploy, API and UI

The read API, the admin API and the dashboard all come up together at one URL. There is no second service to operate.

Inside your boundary

Flags live in your account and your compliance perimeter. Swapping to another provider is a one-line change.

Ready for the whole team.

Accounts are on from the first deploy, so everyone signs in as themselves. It is all part of the open-source server, with no paid edition to unlock.

Invites and four roles

Invite people with a single-use link. Viewer, editor, admin or owner, checked on every request, and the dashboard hides what a role cannot do.

A role per environment

Let someone edit flags in staging while production stays read-only for them.

Single sign-on

Sign in with Okta, Microsoft Entra, Google, Auth0 or Keycloak over OpenID Connect. Your groups can decide who gets which role.

Two-factor codes

Authenticator app codes and recovery codes for password accounts. Require them for admins, or for everyone.

Tokens for the CLI and CI

Personal access tokens that expire and never outrank their owner, instead of one shared secret passed around.

Who changed what

Every flag change is recorded against a person. Sign-ins and team changes go to a separate security log.

How accounts work

Why not just use X?

An honest table, including the rows where Flaghoist loses today.

LaunchDarklyFlagsmith / UnleashPostHogflagdFlaghoist
DeploymentSaaSServer + PostgresSaaS or server + DBSidecar per podServerless, or any runtime
Idle costSubscriptionAlways-on server + DBFree tier, then usageA sidecar per pod$0, scale-to-zero
Management UIYesYesYesNoYes, self-hosted
ProtocolProprietary SDKOF providersOwn SDKOpenFeature-nativeOpenFeature + OFREP
Your data livesTheir cloudYour DBTheir cloudFilesYour DB, your account
Multivariate flagsYesYesYesYesNot yet, boolean only
Experiments / A-BYesYesYesNoNo, bring your own analytics
MaturityMatureMatureMatureCNCFBeta

Why not just build it yourself? You can. A JSON blob in object storage gets you 60% of the way. The other 40% is what is here: sticky SHA-256 rollouts that do not reshuffle users on every deploy, ordered targeting rules, OFREP conformance so every OpenFeature SDK works unmodified, an audit trail, accounts and roles for your team, and a UI your PM can use without a deploy.

Five minutes, start to flag.

  1. Deploy the service

    One config file, one command. Deploy to Cloudflare Workers, or get a container for Render, Fly.io, Railway or your own servers, backed by Redis, Postgres or SQLite.

    $ npm create flaghoist@latest team-flags
    $ cd team-flags && npx flaghoist deploy
    → Cloudflare Workers, or a container for any host
  2. Install a client

    JavaScript shown. In Go, Python, Java or .NET, install your language's official OFREP provider instead. There is nothing Flaghoist-specific to add.

    $ npm i @openfeature/web-sdk @flaghoist/vue
  3. Register the provider once

    Wire it at startup and your application code never mentions Flaghoist again. It only ever talks to OpenFeature.

    await OpenFeature.setProviderAndWait(
      new FlaghoistProvider({ url, apiKey }),
    )
  4. Read a flag

    Then toggle it, roll it to 25%, or target a cohort. From the dashboard or the CLI, with no deploy.

    const newCheckout = useFeatureFlag('new-checkout')

Built by one person.
Here is why that is safe.

Weighing a single-maintainer project before you adopt it is fair. Here is exactly what it means for you, and why it matters less here than it would elsewhere.

Apache-2.0
Anyone can fork it and keep it alive. No CLA, no rug-pull clause.
Your flags, your storage
Your KV, your Redis, your Postgres, your SQLite. This project's health never touches your data.
An open protocol
The API is OFREP. To leave, point the same OpenFeature providers elsewhere. No rewrite.
Eject whenever
flaghoist eject hands you a self-contained TypeScript project you own outright.

If this project stalled tomorrow, you would keep running exactly what you are running today. That is deliberate. It is the whole point of self-hosting on open protocols.

Own your flags.

Self-host it, read it, fork it. Never pay per seat for a toggle again.

$ npm create flaghoist@latest team-flags