Change how agents behave.
Keep control.
Release prompts, models, tools, and skills to the right users without redeploying your application or sending model traffic through FlagDash.
Two products, one clear boundary
AI Config is the artifact.
AI Releases is the decision.
AI Config Releases New
How it works
A safer loop for every AI change.
Your application still calls OpenAI, Anthropic, or another provider. FlagDash only decides which configuration the application should use.
Define
Save model, prompt, tools, parameters, and skills as a named configuration.
Target
Use user, plan, region, segment, or percentage rules to choose a variant.
Observe
Send cost, latency, quality, safety, or business signals back to the release.
Act
Advance, pause, or roll back without a deploy when the evidence changes.
For the whole team
One release surface.
Developers, product, and the business.
release graph / live
support-agent
v3
prompt + tools
10%
candidate cohort
Pass
latency · cost
Developers
Keep provider calls in your application, but move targeting and AI-version branching out of your code.
Product teams
Test prompts, models, and tool policies against outcomes—not intuition or a lab-only score.
Companies
Limit exposure, control spend, preserve an audit trail, and recover quickly when behavior changes.
The boundary matters
FlagDash selects.
Your app requests.
No model keys in FlagDash. No user prompts routed through another service. Your existing OpenAI or Anthropic SDK keeps making the request with the configuration FlagDash returned.
See the integration guide