Solutions / Adoption paths

Start with the agents you have.
Grow into the platform.

Govern existing agents, extend tools into workflows, build native agents and create the applications people use. Each path builds on the same runtime and dedicated instance.

Find your starting pointPlan your path with us

  1. Govern existing agents

    Apply identity, policy and required human review to consequential actions your agents already take.

    Adds
    Control over today’s actions
    Explore this path
    01Start with one agent

  2. Grow tools into workflows

    Extend a governed call into durable, multistep work involving rules, systems and people.

    Adds
    A defined business process
    Explore this path
    02Add to the same foundation

  3. Build native agents

    Build agents in Frozion using the same governed tools, workflows and business context.

    Adds
    Agents built and run here
    Explore this path
    03Add to the same foundation

  4. Build systems of engagement

    Build purpose-built applications and portals that connect participants and systems around a repeatable business process.

    Adds
    Applications where people work
    Explore this path
    04Add to the same foundation

Start at any path. Expand on the same dedicated instance, reusing identity, policies, data and evidence. Applications can use existing agents, native agents or both.

The paths

Where each path starts.
What it adds.

Govern existing agents

Right for you if: You already have agents in production or pilot and want control over consequential actions.

You build
Keep the agent framework. Connect selected tool calls to Frozion’s governed endpoints over MCP or HTTPS.
To start, you need
One agent, one meaningful operation and the systems it calls, with the required authority and integration scope.
You gain
Identity-aware control, explicit policy, required human review and connected evidence for the actions routed through Frozion.
Follow CASE-041: a supplier bank change

Grow tools into workflows

Right for you if: A tool call represents a real process with steps, rules, waits and people.

You build
Compose the workflow visually: typed steps, rules, API clients and human review. Preserve the caller’s contract as the work grows.
To start, you need
A process owner, the permitted system operations and a clear definition of completion.
You gain
A retained business case through waits, revalidation before protected action and reconciliation of uncertain external effects.
Follow PO-7730 through a timeout

Build native agents

Right for you if: You are building a new agent and want its tools, context and controls connected from the beginning.

You build
Build the agent in Frozion using declared tasks, registered tools, workflow contracts and the same identity, policy and data services.
To start, you need
A defined use case, eligible business context and the capabilities the agent may use.
You gain
Native-agent participation in an inspectable process, with authority and policy attached to governed work.
Explore agents, rules and human decisions

Build systems of engagement

Right for you if: People need a purpose-built place to participate in a business process.

You build
Compose applications with App Builder. Business analysts and operations teams shape the experience visually; developers add specialized extensions.
To start, you need
The business purpose, participant roles, integrations and process the application will coordinate. Existing or native agents can participate.
You gain
Portals, workbenches and management views for employees, customers, vendors and partners, connected to the same governed case.
Follow INV-1042 from exception to ERP result
In detail

One foundation.
Different work to govern.

The capabilities stay connected as your use expands. Each column describes their role in the work governed through Frozion.

Capability01Govern existing agents02Grow tools into workflows03Build native agents04Build systems of engagement
Identity & Continuous AuthorityConnect the initiator, agent, resource and delegated scope.Carry authority through the process; recheck before protected action.Give native agents identity, ownership and bounded permissions.Apply tenant, role and business scope to each participant.
Visual Policy BuilderCheck explicit conditions before the governed operation.Apply policy and review obligations at governed steps.Use the same policies for native-agent actions.Control protected reads and actions behind the experience.
HITL InboxHold sensitive actions for an authorized internal reviewer.Make required review part of the waiting workflow.Hand required decisions from native agents to people.Connect application workflows to the same internal review case.
Orchestration & Durable ExecutionA call can enter an operation independent of the caller’s session.Retain state through waits; revalidate and reconcile uncertain effects.Run native-agent tasks within the governed process.Keep application cases connected while work waits and continues.
API Client BuilderExpose a protected operation through a declared contract.Call APIs and external MCP tools; apply policy before and after MCP calls.Give native agents registered internal and external capabilities.Connect permitted application reads and writes to existing systems.
AI Data Plane & Feature StoreSupply eligible records, evidence and calculated facts.Reuse governed queries and consistent facts across steps.Provide scoped context with source and freshness in view.Use the same eligible data and facts in the application.
Model & Tool RoutingApplies to model steps run in Frozion; external agents keep their own models.Select internal tools, workflows or external MCP tools; populate parameters over multiple model turns.Use the same Tool Call Resolver/Router for native-agent tasks.Apply the same routing and parameter resolution to application model steps.
Provenance & EvidenceConnect the governed request, decisions, attempt and response.Keep one case history from sources to reported outcome.Record native-agent participation and its supporting evidence.Trace outcomes through application versions, decisions and sources.
App BuilderOptional: add a review or status experience.Optional: add forms and workbenches around the process.Optional: create screens for people working with agents.Connect purpose-built application screens to data and actions through governed workflows.
How it runs

One dedicated instance.
All four paths.

Your organization licenses a dedicated Frozion instance in its data center or cloud account. Add workflows, native agents and application experiences on that instance, reusing the same runtime and configured controls.

Within the instance, tenants can have separate users, data, permissions and evidence. Business units or regions can operate within their own scope. For software publishers, subscribing organizations can be separate tenants within the publisher’s instance.

Build on Frozion

For software companies and systems integrators.

Deliver solutions on the same foundation, with a clear customer boundary and operating model.

Software companies

Agentic SaaS

Build a branded governed product for subscribing organizations. Configure each tenant’s people, records, integrations, policies and reviewers.

Keep the product experience and customer relationship connected to a defined deployment and support model.

Explore Agentic SaaS
Systems integrators

Reusable accelerators

Package reusable workflows, agents, interfaces and integration patterns around an industry or business process.

Adapt the solution to the client’s approved environment, with deployment and support responsibilities agreed for the engagement.

Explore SI accelerators
Questions

Choose your starting point.
Keep your options open.

No. Start where the first use case fits. Governing an existing agent gives you a focused entry point; you can also begin directly with a workflow, native agent or business application.

You add more to the same dedicated instance: process steps, agents or application experiences. Reuse the configured identity, policies, data and evidence services, while defining the new work’s integrations and permissions.

No. Applications can coordinate existing agents, native agents, rules, enterprise APIs and people. Building agents in Frozion is an available path, not a prerequisite for application development.

Yes. App Builder supports external portals and other role-appropriate experiences. Sign-in, tenant membership and resource permissions define participation. The HITL Inbox remains for assigned internal members.

Yes. Frozion supports multiple tenants within an instance, with their own users, data, permissions and evidence. Define the tenant and operating boundaries for the organization or offering.

They can invoke Frozion through MCP or HTTPS. Registered tools, workflows and agents can be exposed through MCP. Start with a protected resource call and visually extend its process as the work grows.
Plan your adoption

Find your first step.

Tell us what you run today and what you want to build next. We’ll map where you can start and what the next path would add.

Plan your path with usDiscuss building on Frozion