Gradual rollout
Widen slowly. Nobody bounces between old and new.
fallthroughRollout: {
variations: [
{ variation: "on", weight: 20_000 },
{ variation: "off", weight: 80_000 },
],
}
Open-source feature flags on the Postgres you already have. Release to 1% or to everyone, and switch it off in a click.
if (flags.get("new-checkout", { key: user.id }, false)) { // show the new checkout }
Raise the rollout, hit the switch, or click a user.
A switch around new code. Your team flips it from a dashboard, not a deploy.
New code goes live, hidden from everyone.
Staff first, then a slice of users, then everyone.
Something broke? No rollback, no redeploy.
Developer? Flip to see the code behind each one.
Widen slowly. Nobody bounces between old and new.
fallthroughRollout: {
variations: [
{ variation: "on", weight: 20_000 },
{ variation: "off", weight: 80_000 },
],
}
Off everywhere before the incident channel fills up.
curl -X POST \ $FK/v1/admin/projects/acme/environments/production/flags/payments-v2/off \ -H "Authorization: Bearer $FEATUREKIT_TOKEN" # every SDK, on the next stream event: # get("payments-v2") → false OFF
Pro features for Pro customers, on the app versions that support them.
rules: [{
clauses: [
{ attribute: "plan", op: "in", values: ["pro", "team"] },
{ attribute: "appVersion", op: "semVerGreaterThan", values: ["4.2.0"] },
],
variation: "on",
}]
Your team sees it a week before anyone else.
targets: [
{ variation: "on", keys: ["u-ana", "u-ben", "qa-bot"] },
]
Change copy, limits and prices without shipping code.
const discount = flags.get("loyalty-discount", ctx, 0); const banner = flags.get("promo-banner", ctx, "");
Goes live at 09:00. Nobody has to be awake for it.
curl -X POST $FK/v1/admin/…/flags/bf-banner/schedule \ -d '{ "patch": { "enabled": true }, "executeAt": "2026-11-27T09:00:00Z" }'
featurekit runs inside a Node app you already have. Postgres is the only dependency.
A change made in the dashboard, the admin API or an agent reaches FeaturekitServer, running in your own Node process, which writes config and audit rows to Postgres and compiles a versioned snapshot. Server SDKs receive the full compiled ruleset by stream or poll and evaluate in memory. Browsers, React Native and edge clients receive only evaluated values for one context, over server-sent events.
From the dashboard, the API, an AI agent or a file in your repo.
A bad change never replaces the last good one.
Pushed within seconds. No restart, no redeploy.
Your servers keep the rules in memory, so asking a flag costs nothing.
Slowed down 3,000×. The top bar still finishes before you see it move.
Node 22, one core, against the code that ships. Full benchmarks
Fixed precedence. First match wins; an error returns your default.
Break something. Your app keeps answering.
Your app: still answering
All fine. Changes stream in as they happen.
undefined.Ships with alerts and runbooks, including what to do when featurekit_snapshot_age_seconds passes
300.
Your targeting stays on your server. Each user's device only learns its own result.
Your server holds the rules, such as which plans and countries get a feature. A browser receives only the evaluated value for its own user, for example new-checkout is true.
fk_srv_
Gets the compiled ruleset and evaluates any context. Rejected by the client routes.
fk_clt_
Browsers and the edge. Values for one context. Rejected by the server routes.
fk_mob_
React Native and Expo. Same client tier, its own key type.
Approvals, schedules and undo, free. Most tools charge enterprise prices for these.
See who'd change before anyone does.
…/flags/:flag/dry-run
A teammate approves first.
…/flags/:flag/requests
It applies itself.
…/flags/:flag/schedule
No silent overwrites between teammates.
expectedVersion: 412
Hash-chained history. Edits are detectable.
…/audit/verify
Back to exactly how it was.
…/flags/:flag/revert
Works with Claude, Cursor and any MCP client. It can only do what its token allows, and every change is audited.
cart-v2-page or cart-v2-checkout.
Which one?claude mcp add featurekit \
--env FEATUREKIT_URL=http://127.0.0.1:3000 \
--env FEATUREKIT_TOKEN=fk_pat_... \
--env FEATUREKIT_MCP_WRITE=1 \
-- npx -y featurekit-mcp
Two SDKs. Anything else speaks two HTTP endpoints.
import { FeaturekitSDK } from "featurekit-server/sdk"; const flags = new FeaturekitSDK({ sdkKey: process.env.FEATUREKIT_SDK_KEY, baseUrl }); await flags.ready({ timeoutMs: 5_000 }); if (flags.get("new-checkout", { key: user.id, plan: user.plan }, false)) { // synchronous, in memory, no network call }
import { FeaturekitClient } from "featurekit-client"; const flags = new FeaturekitClient({ clientKey: "fk_clt_…", baseUrl, context: { key: user.id }, stream: true, }); await flags.ready(); flags.get("new-checkout", false); // typed by the default flags.on("change", () => render()); // pushed over SSE, no polling
export function useFlag<T>(flagKey: string, defaultValue: T): T { const subscribe = useCallback((onChange: () => void) => { const offChange = featurekit.on("change", onChange); const offState = featurekit.on("state", onChange); return () => { offChange(); offState(); }; }, []); return useSyncExternalStore(subscribe, () => featurekit.get(flagKey, defaultValue)); } const showNew = useFlag("new-checkout", false);
import { FeaturekitClient } from "featurekit-client"; // the same client, with a mobile key export const featurekit = new FeaturekitClient({ clientKey: "fk_mob_…", baseUrl: "https://flags.acme.com", context: { key: user.id, platform: Platform.OS }, stream: true, });
curl -X POST https://flags.acme.com/v1/client/state \ -H "Authorization: Bearer $FEATUREKIT_CLIENT_KEY" \ -H "Content-Type: application/json" \ -d '{ "context": { "key": "u-ana", "plan": "free" } }' # { "values": { "new-checkout": { "value": false, "reason": "FALLTHROUGH" } } }
Vue and Svelte adapters are in the adapters doc, the wire format in the HTTP spec.
No paid edition. No per-seat bill. Every feature is in the repo.
| Feature | featurekit | Unleash | Flagsmith |
|---|---|---|---|
| Self-hosted | Yes | Yes | Yes |
| Control plane | Inside your Node app | Separate service | Separate service (Python) |
| Change requests | Included | Enterprise edition | Paid plans |
| Tamper-evident audit | Hash chain you can verify | Event log | Audit log on paid plans |
| Framework SDKs | One client, 20-line adapters | Per-framework packages | Per-framework packages |
| License | MIT, no paid edition | Apache 2.0 core, commercial enterprise | BSD-3 core, commercial enterprise |
LaunchDarkly is hosted, billed by seats and usage, and does experimentation. If you need A/B analytics today, it or Unleash is the better fit. If you want governance without a sales call, pick featurekit. Every design decision is written down.
get().One install, a dashboard at /admin, and no more redeploys to turn things off.
We deploy featurekit on your infrastructure, migrate flags from LaunchDarkly, Unleash or Flagsmith, and offer priority support. Bugs go to GitHub issues.