From a selected tool to an authorized action.
A model’s choice still needs an acting identity, permitted scope and the business conditions for that specific operation.
Compare / Your agent stack
Keep your framework.
Govern the work it initiates.
Your framework, workflow engine and AI gateway each handle part of the job. Frozion connects agent actions to business authority, contextual policy, human decisions, durable execution and evidence in one visually inspectable runtime.
Start with the components you already run. Govern selected actions through MCP or HTTPS, then grow the process behind the call.
FROZIONExecution FabricGoverned from request to outcome
- Choose the capability
Internal tool, workflow or external MCP tool
- Resolve the inputs
Populate parameters across model turns
- Govern the invocation
Authority, policy and required review; policy before and after external MCP calls
Connect the call to durable work and its recorded outcome.
The integration burden
The work crosses components.
The controls must stay connected.
From a pause to an accountable decision.
A review needs the exact proposal, current facts, an authorized person and a decision connected to the process that resumes.
From separate logs to one business case.
The outcome needs to remain traceable through the rules, sources, approvals and system responses that shaped it.
01 / Comparison
What each component supplies.
What your team connects.
Categories overlap, and individual products differ. Compare the responsibilities in your own stack with what Frozion provides as a connected platform.
| Responsibility | Agent framework | Workflow engine | AI gateway | Frozion |
|---|---|---|---|---|
| Agent reasoning and tool selection | Primary focusBuild reasoning loops and select tools. | Product dependentCoordinate agent code or integrate a framework. | Product dependentSome gateways include agent and tool routing. | Built inBuild native agents or connect your existing framework. |
| Long-running work and durable waits | Product dependentPersistence and pause/resume capabilities vary. | Primary focusRetain execution state through long-running work. | Product dependentDurable business processes may require another runtime. | Built inRetain the case through waits; revalidate and reconcile uncertain effects. |
| Model routing and usage controls | Product dependentConfigure providers, middleware and limits. | IntegrateCall model services and implement the desired controls. | Primary focusRoute model traffic and manage access, budgets and usage. | Built inApply model eligibility and data policy, usage attribution and configured effort limits. |
| Acting identity and delegated authority | IntegrateConnect identity and business authorization to tool use. | IntegrateCarry the actor and business scope through workflow code. | Product dependentKey, user, team and tool access controls vary. | Built inConnect agent identity, delegated business scope and current authorization. |
| Policy using business history | IntegrateConnect business data and evaluate rules in the application. | IntegrateRead historical state and implement the business rule. | Product dependentPolicy depth and business-data integration vary. | Built inUse reusable, freshness-checked Feature Store facts in visual policy. |
| Human approval of the proposed action | Product dependentApproval middleware and interrupts are available in some frameworks. | Build on primitivesUse durable signals, updates or tasks to implement the review process. | Product dependentSome tool and MCP flows support approval controls. | Built inReady-made HITL Inbox, exact-revision binding and policy-required FIDO2. |
| MCP exposure and external tool calls | Product dependentMCP clients and adapters vary by framework. | IntegrateRun MCP clients or expose workflow-backed tools through integration code. | Product dependentSome gateways broker MCP tools and enforce access controls. | Built inExpose native tools, workflows and agents; call external MCP tools with policy before and after. |
| Tool inputs across model turns | Product dependentBuild or configure the tool-selection and parameter loop. | IntegrateCoordinate parameter-resolution logic as workflow steps. | Product dependentTool-loop behavior depends on the gateway and client. | Built inThe Tool Call Resolver/Router selects across internal tools, workflows and external MCP tools, with multi-turn parameter population. |
| Visual inspection of definitions | Product dependentGraph views and developer tooling differ. | Product dependentDefinition, execution and operations views differ. | Product dependentRequest, policy and administration views differ. | Built inInspect workflows, policies, contracts, mappings and dependencies visually. |
| Connected decision evidence | IntegrateConnect traces, tool results and approval records. | Execution historyConnect run history to business identity, facts and review evidence. | Request recordsConnect traffic and tool logs to the business case. | Built inKeep facts, versions, policy decisions, approvals and reported outcomes in one tamper-evident record. |
| Change review, simulation and rollback | Product dependentUse the framework’s tooling and your delivery process. | Product dependentVersioning, testing and deployment controls vary. | Product dependentPolicy and configuration lifecycle controls vary. | Built inInspect dependencies, compare workflow versions and simulate recorded cases before approval and publication. |
Primary focus identifies a category’s central job. Integrate describes work your application connects. Product dependent means coverage varies. Built in describes Frozion capabilities; configured integrations, policies and scope still determine how they apply.
02 / Category by category
Fit the platform to
the stack you already run.
01
Agent frameworks
Build the agent and its reasoning loop.
What it does well
Frameworks provide the programming model for prompts, reasoning, state and tool use. Some include approval middleware, persistence and graph views.
With Frozion
Keep the framework. Route selected actions to Frozion over MCP or HTTPS. The call can enter a single governed operation or a complete workflow with identity, policy, human review and evidence.
Works alongside your framework02
Workflow and durable-execution engines
Keep long-running work connected.
What it does well
Durable engines provide execution state, waits and mechanisms for signals, retries and human interaction. Business authorization and the review experience are responsibilities to design around those primitives.
With Frozion
Frozion combines durable workflows with visual contracts, policies, delegated authority and the ready-made HITL Inbox. Existing engines can remain in use elsewhere; Frozion can call endpoints they expose where the process needs them.
Explore durable execution03
AI and MCP gateways
Control access and traffic at shared boundaries.
What it does well
Gateways can provide model routing, access controls, usage tracking, guardrails and MCP tool access. Their coverage depends on the product and the paths routed through it.
With Frozion
Use Frozion to connect governed tool calls to the business process around them: reusable facts, revision-bound decisions, durable waits, authorized system actions and connected evidence. Model routing and MCP controls overlap; evaluate the integration against your existing gateway.
Explore the AI Control Plane03 / MCP to business process
One MCP tool can become
an entire business process.
Start with a protected call. Extend its work visually into rules, reusable facts, human decisions and durable waits, without coding.
Expose any Frozion-built tool, workflow or agent natively through MCP. Inside the process, invoke external MCP tools with policy applied before and after each call.
Compare the four adoption pathsTool Call Resolver/Router
Internal and external capabilities. One place to select.
Present internal tools, workflows and external MCP endpoints as available tools for the LLM. Populate the selected capability’s parameters over multiple turns before invocation.
Selection, parameter resolution and permission to execute remain distinct. The call passes the applicable contracts, authority and policy checks.
Explore model and tool routing04 / Questions
Make the boundary
clear from the first call.
No. Keep the framework and connect selected actions through Frozion over MCP or HTTPS. The scope governed by Frozion is the work routed through it.
Approval code is one part of the process. Frozion connects the review to agent identity, business policy, eligible facts, the exact proposal revision, durable state and the evidence of what happened.
There is overlap in durable execution, routing and MCP controls. Choose the boundary for your application. Frozion can run the governed process while existing frameworks, engines and gateways continue serving their other responsibilities.
Yes. Expose any Frozion-built tool, workflow or agent natively as an MCP tool or endpoint. Frozion workflows can also invoke external MCP endpoints with policy before and after the call.
Yes. The Tool Call Resolver/Router can present internal tools, workflows and external MCP tools, and support multi-turn parameter population before invocation. The selected call remains subject to contracts, authority and policy.
Choose one consequential action and identify the agent, business owner, systems, permitted scope and completion criteria. Map which controls already exist and which Frozion should carry through the process.
Start with one governed action
Bring your stack.
Map the work it needs to govern.
Follow one action from the agent’s request to the business outcome. See which controls you already have and where Frozion connects the process.