Ship with confidence. You control the switch.
No credit card required
One place to decide what runs in production
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 rolloutsRemote config
Update limits, settings, and JSON documents in production without deploying. Every value has a fine-grained type and the constraints you set.
Types & validationsTargeting & experiments
Serve different values by user, segment, app version, or any attribute you configure. Split traffic between variations and compare the results.
Targeting rulesAny 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 skillsFast changes need more than a switch
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 from the first value to the final cleanup
- 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.
- Step 2Safety
Update
Every update is validated, wherever it comes from, and recorded in the audit log.
- Step 3Delivery
Deliver
Target users and segments, roll out gradually, and run A/B tests. Test your rules before you save.
- 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.
- Step 5Longevity
Retire
Settled flags and unused configs raise alerts, so nothing lingers. Renames clean up the old key.
From zero to production ready in 5 minutes
Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI and more.
$ npx skills add ConfigDirector/agent-skillsAdd 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.tsreads it
Install, initialize, read a value.
$ npm install --save @configdirector/client-sdkimport { 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
);