Flags
Turn features on for the right people.
Feature flags and remote settings that your app decides locally, so the user details you target on never leave it. Roll out without a deploy, and turn a feature off with one switch.
Decided inside your app.
The SDK downloads one small config and checks every flag in your own process. The user details you target on never leave your app, and a flag check is a function call, not a network request.
Roll out to 10%, then 50%, then everyone.
Each user keeps their place as the percentage grows, so nobody sees a feature appear and disappear. Turning it off is one switch.
Target the right people.
Write rules on any detail you pass in, such as plan, country or app version. Define a group like “beta testers” once and reuse it in every flag.
Safe to change, safe to fail.
Production changes need an admin, and every change is in the history, where one step restores an earlier version. If ProductCraft can't be reached, your app keeps using the last config it had.
How it works
Your first flag in three steps.
- Turn on Flags for your workspace and create a flag in the console.
- Install
@productcraft/flagsand give it your environment's SDK key. - Read the flag with your user. Flip it in the console and your app follows.
import { FlagsClient } from "@productcraft/flags";
// Downloads this environment's config and refreshes it every 60 s.
const flags = new FlagsClient({ sdkKey: process.env.PRODUCTCRAFT_FLAGS_SDK_KEY });
// Evaluated in your process: the user object is never sent anywhere.
const on = await flags.getValue("new_checkout", false, {
identifier: "user-123", // percentage rollouts hash this, so a user keeps their bucket
email: "ada@example.com",
custom: { plan: "pro" },
});More in the box
Everything else Flags does.
- Settings, not just switches Text, number and JSON values for copy, limits and remote configuration.
- Environments Development, Staging and Production, or your own, each with its own SDK key.
- Prerequisite flags Serve a flag only when another flag has a given value.
- Protected Production Members change Development freely; Production needs an admin, and can require a note with every change.
- Agents propose, people approve Choose per environment who must ask first: everyone, or only API keys and AI agents. A reviewer who is not the author approves the change before it goes live. Approvals guide
- Scheduled changes and ramps Turn a flag on at 09:00, or roll it out to 5%, 25%, 50% and everyone on the days you pick, with pause and stop. Schedules guide
- Stale-flag report Lists flags that look finished and the value to inline in their place, emails owners every Monday, and gives AI agents the same list. Cleanup guide
- Signed webhooks An event whenever a config changes, with Send test, a 30-day event log and replay.
- Node, React and OpenFeature
@productcraft/flags,@productcraft/flags-reactand@productcraft/flags-openfeature. - Import from ConfigCat Bring over flags, segments and targeting rules in one step. Users keep their rollout buckets.
- Hosted in the EU Flags runs in Frankfurt with the rest of ProductCraft.
For your AI agents
A management API and MCP tools, behind the policies you set on each key, so an agent can create a flag without being able to turn on Production. Read about MCP
Your first flag, end to end.
Create a flag, read it from Node, then flip it in the console and watch your app follow. Flags is free during the preview.
Coming from ConfigCat? Read the migration guide