Remote config & feature flags

Ship with confidence. You control the switch.

Decide what features reach your users in seconds, without redeploying. Move fast with coding agents while keeping changes gradual, reversible, and within the constraints you set.

No credit card required

What you get

One place to decide what runs in production

Feature flags, remote config, targeting and experiments, with SDKs for every stack and skills for your coding agent.

Feature flags

Ship code behind a flag and turn it on when you decide. Roll out to 1%, specific segments, or everyone. Roll back in one click.

Gradual rollouts

Remote config

Update limits, settings, and JSON documents in production without deploying. Every value has a fine-grained type and the constraints you set.

Types & validations

Targeting & experiments

Serve different values by user, segment, app version, or any attribute you configure. Split traffic between variations and compare the results.

Targeting rules

Any stack, any agent

SDKs for web, mobile and server, OpenFeature, Terraform, a CLI and an MCP server. Skills let your coding agent wrap changes in flags.

Agent skills
Why guardrails

Fast changes need more than a switch

A switch outside the deploy pipeline is outside its safety net too. The risk of wrong values going live, or incomplete JSON documents breaking an app, increases with agents in the loop. Our guardrails are the safety net that modern systems need.

Invalid values are refused.

Every value has a fine-grained type and optional constraints. JSON documents can be validated with JSON schemas. A bad config value is rejected before it reaches any users.

Incorrect use of configs and flags is caught.

Monitoring detects a key that was renamed or accessed with the wrong type, and the CLI fails the build in CI before it ships.

Settled flags are retired.

A feature flag that has been enabled long enough raises an alert, and code references show where it is read, so you or your coding agent can remove it.

Guardrails at every stage

Guardrails from the first value to the final cleanup

Every stage of a config's life has a guardrail, from the moment you define it to the day it's ready to retire.
Safety prevents mistakes and alerts on issues Longevity keeps flags, configs, and code tidy
  1. Step 1Safety

    Define

    Pick a fine-grained type and the constraints your code expects. Your coding agent can use our skills to wrap a feature in a flag.

  2. Step 2Safety

    Update

    Every update is validated, wherever it comes from, and recorded in the audit log.

  3. Step 3Delivery

    Deliver

    Target users and segments, roll out gradually, and run A/B tests. Test your rules before you save.

  4. Step 4Safety

    Monitor

    Telemetry is watched for wrong types, mismatched in-code default values, and outdated SDKs. The CLI catches a wrong key or type in CI.

  5. Step 5Longevity

    Retire

    Settled flags and unused configs raise alerts, so nothing lingers. Renames clean up the old key.

SDKs and agent skills

From zero to production ready in 5 minutes

Install the SDK and read a value, or ask your coding agent. With the ConfigDirector agent skills, your agent picks the SDK for your framework, wires it up and creates your first feature flag.

Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI and more.

$ npx skills add ConfigDirector/agent-skills
your coding agent

Add ConfigDirector to this app and put the new onboarding flow behind a flag

  • Picked the JavaScript SDK for this Vite app and installed it
  • Reads the SDK key from VITE_CONFIGDIRECTOR_SDK_KEY
  • Create the flag new-onboarding-flow, off in every environment? yes
  • Created it, and src/onboarding.ts reads it

Install, initialize, read a value.

$ npm install --save @configdirector/client-sdk
app.ts
import { createClient } from "@configdirector/client-sdk";
export const client = createClient("YOUR-CLIENT-SDK-KEY");
await client.initialize();

const enabled = client.getValue(
  "new-onboarding-flow",
  false // in-code default value
);

Move fast.
Don't break things.