# Flagger

> Flagger (flagger.gg) is feature flags for teams that ship with coding agents. It is in early access with a waitlist: not generally available, no public pricing yet. It is built on the in-house flag system that runs Sandboxer and Transformer in production, from North Bay Ventures.

Live today (in the production system Flagger is built on):

- Flags are declared in code ({key, description, owner, default}); new flags start off and deploys never overwrite a state someone set. No create or delete through the API.
- Five states: off (no one), admins (platform admins), targets (listed users and workspaces, plus admins), percent (a sticky share of users, plus admins), on (everyone). Rules are kept when the state changes.
- Targeting: user ids or verified emails (case-insensitive), workspace ids, percent 0-100. Percent bucket: first 4 bytes of sha256(key + ":" + userId), big-endian, mod 100, below the percent.
- Checks are synchronous against an in-memory snapshot refreshed every 5 seconds and after each change. Unknown, not yet loaded or errored means off. Signed-out visitors and background jobs see only flags that are on.
- The browser receives only {key: true} for flags on for the caller; the flag list and targeting are never sent to non-admins.
- Admin API: GET /admin/api/flags, GET /admin/api/flags/{key} (with history), PATCH /admin/api/flags/{key} {state, rules, note}, POST /admin/api/flags/{key}/kill. Every change is recorded with who, when, before, after and a note.
- CLI: flags list | get | set <key> <state> [--percent N] [--note] | target <key> --users --workspaces | kill <key>.
- Agents use the CLI and admin API with admin credentials; customer API keys never get flag access. In Transformer, admin agents also use MCP tools flags_list, flag_get, flag_set, flag_kill.
- Test helpers: withFlag(key, on, fn), setFlagOverride(key, on), bothFlagStates(key, fn).

In development for early access (not available yet): flags tied to metrics, guarded rollouts with automatic rollback, segments, approvals, SDKs, experiments, a hosted MCP server.

Operated by North Bay Opco I, Inc. (a Delaware corporation), 777 Brickell Ave, Suite 500 PMB 1074, Miami, FL 33131. Contact: support@northbayventures.com.

## Pages

- [Home](https://flagger.gg/): what Flagger is and who it's for
- [Features](https://flagger.gg/features/): what's live today and what's in development
- [How it works](https://flagger.gg/how-it-works/): states, targeting, evaluation, admin API, CLI, agents, tests
- [Waitlist](https://flagger.gg/waitlist/): join early access
- [Privacy](https://flagger.gg/privacy/) and [Terms](https://flagger.gg/terms/)