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.

Read the guide

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.

Read the guide

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.

Read the guide

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.

Read the guide

How it works

Your first flag in three steps.

  1. Turn on Flags for your workspace and create a flag in the console.
  2. Install @productcraft/flags and give it your environment's SDK key.
  3. Read the flag with your user. Flip it in the console and your app follows.
server.ts
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.

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