01 / OBSERVE
Capture how agents actually perform
Collect cost, latency, quality, provider, domain, policy, and outcome signals from governed agent runs.
Agent fleet intelligence, under governance
cascadeflow Studio is the managed operating layer for the cascadeflow runtime. It brings policies, domain routing, fleet analytics, and continuous optimization into one control plane.
Private workspace · policy-enforced routing · in-process runtime
cascadeflow Studio · agent fleet overview
// OSS_VS_STUDIO
The runtime is open source. Studio operates the fleet.
cascadeflow OSS gives developers the in-process intelligence and enforcement layer. Studio adds the managed builders, analytics, governance, and organization-wide workflows needed to improve many agents as one system.
cascadeflow OSS
cascadeflow Studio
Primary role
In-process runtime library and agent harness installed in your Python or TypeScript application.
Managed control plane for operating, governing, and continuously improving agent fleets.
License and access
MIT licensed, source available on GitHub, and free for commercial use.
Commercial managed product with a private workspace and organization controls.
Policies
Configure built-in runtime constraints and KPI weights in code.
Build, version, stage, and govern custom policies and scoring dimensions visually.
Domain routing
Define domain-aware cascades and runtime behavior through SDK configuration.
Map specialist cascades in Domain Builder and manage them consistently across the fleet.
Optimization scope
Observe and enforce decisions within the applications where the runtime is installed.
Compare performance across agents, models, providers, domains, users, and KPI targets.
Analytics and reporting
Decision traces, run summaries, cost tracking, and telemetry integrations.
Fleet BI, ROI and value reporting, forecasts, optimization events, alerts, and exports.
Team operations
Your team owns deployment, configuration, and operational workflows in code.
RBAC, SSO/SAML, audit logs, multi-org workspaces, and controlled fleet-wide rollouts.
// BOTTOM_LINE Use OSS to build and enforce in code. Add Studio when the operating problem expands from one runtime to a fleet.
cascadeflow
Fleet-wide visibility and governance
Business intelligence for AI agents, plus two dedicated visual builders, one for policies and one for domains, so you can govern KPIs, cost routing, and compliance across your entire agent fleet.
Dedicated builder
Policy Builder
Define custom scoring dimensions, KPI weights, and governance policies beyond the six built-in dimensions. Enforce them across every agent with gradual rollouts and automatic rollback.
Dedicated builder
Domain Builder
Map each domain to its specialist model cascade and tune keyword and semantic routing visually without code. Version domains and enforce them fleet-wide.
Self-learning agent intelligence
Every run feeds patterns back to through auto-benchmarks, model fleet suggestions, compounding optimization.
Fleet BI & ROI analytics
Real-time cost breakdowns by provider, model, domain, and user. Spending forecasts and exportable reports.
KPI enforcement & governance
Turn business KPIs into live guardrails for cost routing, compliance rules, and quality bars at every step.
Organization controls
Role-based access, SSO/SAML, audit logs, and multi-org workspaces. Integrates with Slack, Datadog, and your finance stack.
See governance running across your agent fleet.
// Studio Domain Builder
Turn domain expertise into reusable routing intelligence
Map each type of work to a specialist model cascade, tune keyword and semantic routing visually, and apply versioned domain behavior across governed agents.
$
domain:code"Fix this Python race condition"
→ code-tuned drafter, escalate to flagship on failed tests
$
domain:writing"Draft the launch announcement"
→ writing-optimized model, higher quality bar
$
domain:data"Summarize this CSV of orders"
→ fast, low-cost model · speed prioritized
$
domain:legal"Review this indemnity clause"
→ high-accuracy verifier, strict compliance scoring
$
domain:support"Why was my invoice declined?"
→ cheap drafter first, escalate only when unsure
$
domain:general"Anything else"
→ free-first cascade, escalate on quality miss
// SELF_OPTIMIZING_OPERATIONS
Every governed run makes the fleet easier to improve
The OSS runtime makes decisions inside one application. turns evidence from many runs into an operating system for continuous optimization. Teams can see what works, adjust policy and routing, and measure the result.
02 / LEARN
Find the patterns humans miss
Compare model and policy performance by agent, task, domain, and KPI target instead of relying on aggregate token spend.
03 / OPTIMIZE
Turn evidence into better configurations
Use benchmarks and fleet intelligence to improve model cascades, thresholds, policies, and domain routing over time.
04 / GOVERN
Roll out changes with control
Version policies and domains, stage changes, monitor impact, and keep an attributable record of what changed and why.
// STUDIO_FAQ
Questions about Studio and the OSS core
Is cascadeflow Studio a replacement for the open-source runtime?+
No. The MIT-licensed runtime stays inside your agent applications and provides the execution-time intelligence. Studio is the managed operating layer that helps teams configure, govern, analyze, and improve those runtimes across an agent fleet.
What makes Studio agentic and self-optimizing?+
Studio uses evidence from governed agent runs to surface model, policy, domain, KPI, and cost-quality patterns across the fleet. Teams can use those insights and builders to improve configurations over time, then measure the impact of each change.
What is Policy Builder?+
Policy Builder is the visual workspace for defining custom policies, KPI weights, scoring dimensions, and runtime controls beyond the core's built-in dimensions. Policies can be versioned and rolled out across governed agents.
What is Domain Builder?+
Domain Builder maps types of work to specialist model cascades. Teams can tune keyword and semantic domain routing, version the configuration, and apply it consistently across multiple agents without hand-editing each integration.
What fleet analytics does Studio provide?+
Studio brings together agent-run volume, costs, latency, KPI performance, model and provider behavior, domain performance, policy interventions, optimization events, alerts, and ROI-oriented reporting in one control plane.
Does Studio move agent execution behind an external proxy?+
The cascadeflow runtime remains in-process with the agent. Studio adds the managed control, policy, and intelligence plane around governed runtimes rather than turning cascadeflow into a request-time model proxy.
Can a team start with OSS and add Studio later?+
Yes. Teams can start with the MIT core in observe mode, validate runtime behavior, and add Studio when they need shared builders, fleet-wide analytics, organization controls, and continuous optimization across multiple agents.
// AGENT_FLEET_INTELLIGENCE
Put your agent fleet under measurable control
See how connects runtime governance, fleet analytics, Policy Builder, and Domain Builder around the agents you already run.