One case, shared state
Keep the interface connected to the process instead of maintaining a second account of where the work stands.
Purpose-built applications.
Governed from data to action.
Build the interface.
Connect the work.
Turn agents, workflows and business data into the applications people work in: workbenches for employees and management, portals for customers, vendors and partners, and complete SaaS products. Screens share the identity, policy, workflow state and evidence of the work behind them.
Compose forms, portals, dashboards, contextual AI and review workbenches on the same identity, data, policy and execution model as the process behind them. Start around an existing agent's governed workflow, or build a native application from day one.
CASE-041 · SUP-204
Review required
Bank account change
Proposed changePayment account ··4821 → ··9036Same proposal used by the governed workflow
Bank changes / 30 days2 recorded changes
Before approvalFIDO2 required by policy
Verification evidenceSource revision + decision context
Execution
waiting for an authorized decision
Shared identityBusiness recordsPolicyDurable stateEvidence
From a focused workbench to a complete business product
Internal applicationsCustomer & partner portalsContextual AIReview & approvalsTenant-aware SaaS
App Builder across your adoption path
Govern existing agents
Optionally add a review or status workspace around an existing agent’s governed work.
Grow tools into workflows
Give workflow participants forms, case views and purpose-built workbenches.
Build native agents
Create experiences for people working with agents built in Frozion.
Build systems of engagement
Build portals and applications for employees, customers, vendors, partners and management.
The problem this solves
Business work needs more than a chat window.
An agent can answer or propose. People still need records, forms, status and a place to decide. Building those pieces separately means keeping the screen, permissions and workflow in sync.
Authority behind the screen
Apply the same identity and policy to data and actions, including requests made outside displayed controls.
Evidence where people work
Show why a case is waiting and which facts informed the proposal.
The application around the agent
Give people a place
to complete the work.
A useful agent can retrieve information or propose an action. A business application also needs records, forms, permissions, review queues, status and a way to understand the result.
App Builder brings those experiences together. A reviewer opens the proposal the workflow is waiting on. An operator sees its durable state. An authorized auditor follows the evidence tied to that same operation.
For an existing agent, add the portal or workbench around the Frozion workflow it calls. For a native application, compose the experience and governed process together.
BUILD THE EXPERIENCE
App Builder
Pages, forms, records, contextual AI and human work.
RUN THE PROCESS
AI Control Plane
Per-step RBAC, visual policies, HITL, FIDO2 and durable execution.
Explore Control Plane ↗
INFORM THE DECISION
AI Data Plane
Eligible records, retrieval, Feature Store facts, context and lineage.
Explore Data Plane ↗One case. Different responsibilities.
Four views.
One governed process.
Explore the supplier-change case used across the platform pages. Each person gets the information and controls appropriate to their role, connected to the same proposal and execution.
FINANCE REVIEW WORKBENCH
Decision pending
Review the exact proposal.
Inspect the proposed account change alongside eligible evidence, calculated facts and the policy that requires review.
- Proposal
- Payment account ··4821 → ··9036 · proposal revision 2
- Business fact
- 2 bank changes / 30 days · Feature Store definition v3
- Evidence
- Verification document + permitted supplier history
- Decision boundary
- Authorized finance reviewer + policy-required FIDO2 step-up
Inspect the checks behind this view
Reviewer authority, proposal revision, eligible context and policy obligations are evaluated for the current decision. Approval stays bound to the proposal; the subsequent business write still requires runtime authorization.
The reviewer and the workflow work against the same proposal,
context and policy.Role views show configured scope; switching views here is not authentication.
The same case. The right place to decide.
Your internal reviewers can use the ready-made HITL Inbox or a review workbench you design here. Both connect to the case and its approval rules. Customers, vendors and partners participate through application portals.
01 / Design & data
Compose the experience
around the business task.
Combine pages, layouts, navigation, forms, tables, dashboards and record views into the experience the work requires. Add queues, evidence panels and AI interaction where they help the user move forward.
Use common components and templates while keeping each application's schemas, data, workflows and permitted actions explicit.
Records & forms
Create, inspect and update typed business entities. Capture requests with validation and mappings into the process.
Dashboards & queues
Present current work, assigned tasks, waiting cases, exceptions and completed operations.
Portals & workbenches
Give employees, customers, partners and reviewers the application appropriate to their responsibility.
Knowledge & evidence
Bring search, contextual AI, source references, decision history and execution inspection into the work.
Operational Collections & forms
Build on business objects
that the workflow understands.
Use typed entities and relationships for supplier records, invoices, cases, documents and change requests. Support create, read and update operations, governed deletion or lifecycle actions, filtered lists, search and user-specific queues.
A form binds entered values to the application's schema, validation, policy and mappings. Those values can become the proposal later analyzed, reviewed and acted on by the Control Plane.
Explore typed records and governed querySupplier change request
SupplierSupplier referenceTyped entity · current tenant
New payment accountProposed account detailsValidated fields · permitted edits
VerificationSupporting documentSource reference · classification
Explicit application bindings
Connect each component
to a defined capability.
Bind the interface to platform contracts so its data, context, actions and status remain connected to the application underneath.
Record list or detail pageCollections + governed queries
Form and application actionSchema + validation + APIs + mappings
Case status and work queueExecution Graph + durable state
AI or reviewer panelContext + Feature Store + policy
History and evidence viewProvenance + decisions + reported effects
02 / AI & human work
Put assistance and judgment
where the work happens.
Place AI interaction inside the active record, case or task. Let people investigate eligible information, understand a business fact, prepare a proposal and move into governed action from the same application.
The Data Plane supplies scoped context; the Control Plane governs tool calls, policy decisions and the work that follows.
Contextual AI & knowledge experiences
Ask about the record
you are already working on.
Bring identity, application state, permitted knowledge, calculated facts and current workflow context into the interaction. Help users explore evidence, summarize information, investigate relationships or identify what is missing.
Combine search over eligible documents and records, contextual AI and evidence views with forms, cases and human review. A useful answer can lead to the next permitted business step.
Explore governed knowledge and context
SUP-204Finance reviewEligible context
Why does this change need another review?
The recent-change rule matched.
The decision-time fact records two bank-account changes in the rolling 30-day window. The configured policy requires finance review before this proposal can proceed.
Feature value · v3Policy conditionSource history
Inspect the underlying fact and policy before making the
decision.
Integrated HITL & FIDO2
Give the reviewer the context
and controls the decision
needs.
Use the ready-made HITL Inbox for internal reviews or design a task-specific workbench. Reviewers see the exact proposal, eligible facts and policy together; the case thread keeps their discussion with the decision.
Require FIDO2 step-up when policy calls for stronger assurance. Approval stays bound to the exact revision reviewed, and the next business action still passes its authority and policy checks.
Explore human decisions and step-up assurance Explore the HITL Inbox
BEHIND A MEANINGFUL APPROVAL
01Who may decide?
Reviewer role, tenant, resource scope and required assurance.
02What is being approved?
The proposal and revision the waiting execution is reviewing.
03What supports the decision?
Eligible evidence, business facts and the applicable policy conditions.
04What happens next?
Record the decision, revalidate the required conditions and continue the governed workflow.
Durable human work
Close the browser.
Keep the case.
Reopen the case and see where the work stands—whether it is waiting for a person, document, callback or verification step. The interface reconnects to the Control Plane's persisted execution state under your current authority.
AssignedAwaiting evidenceWaiting for reviewExceptionCompleted
Evidence inside the application
Understand the outcome in the
application where you work.
Authorized users can inspect decision evidence, context provenance, approval history and execution lineage, including the attempted action, destination response and any unresolved outcome.
Connect the application to Behavior Intelligence and governed replay so teams can inspect the original context and versions of a historical execution.
Explore execution evidence03 / Identity & tenancy
One application model.
The right experience for each user.
Build employee applications, customer and partner portals, and tenant-aware SaaS on shared identity and authorization. Let tenant, role, purpose, taxonomy and resource scope shape the experience from the first request.
The same model connects what a person may see, edit, submit or approve with the controls applied by the runtime.
01 / AUTHENTICATE
Use supported sign-in and assurance options.
Bring FIDO2/passkeys, MFA and enterprise SSO into the application's identity model. Request stronger assurance when policy calls for it.
02 / ESTABLISH SCOPE
Bind tenant and application context early.
Associate applications with their domain or subdomain and establish the active tenant, application and user context before application logic runs.
03 / COMPOSE THE EXPERIENCE
Align navigation and controls with authority.
Shape pages, fields, components, actions, evidence and required obligations using the active role, purpose, policy and process state.
Server-rendered application experiences
Compose the response
within the governed request.
Server-side rendering keeps composition close to identity, tenant, policy and data context. Determine eligible records and application elements before composing the response, and keep unnecessary protected data and sensitive application logic out of the browser.
Support public or resource-oriented pages that can be indexed where required, alongside authenticated operational experiences.
Rendering is one part of the architecture. Authorization and policy still apply to data access and operations at runtime, including requests made outside the displayed controls.
Explore identity and security
THE APPLICATION REQUEST
Identity + tenant + purposeEstablish the active application scope
Eligible data + policy + execution stateCompose the permitted application experience
Pages + fields + available controlsPresent the view appropriate to this user and case
A subsequent action enters its own governed execution path.
04 / Extend & publish
Build visually.
Extend where your product needs it.
Reuse layouts, navigation, templates, forms, record views and evidence panels across applications. Keep room for the specialized interactions, integrations and proprietary logic your business requires.
Engineering teams can add supported custom components, visualizations and integrations while retaining the application's identity, permissions and governed workflow.
REUSE THE PATTERN
Standardize the common work.
Start from reusable application pieces, then bind them to the schemas, roles, policies and actions of the specific business process.
EXTEND THE CAPABILITY
Keep custom engineering first class.
Add supported code, custom visualizations, specialized components and application integrations through defined platform contracts.
Explore developer extensibilityVersioned publication
Evolve the application.
Keep its history explainable.
Publish the application experience as versioned software. Connect the interface definition to the schemas, policies, mappings, workflow definitions and capabilities governing its work.
Recorded executions remain associated with their application versions. Inspect what happened under those definitions and use the evidence to guide the next release.
-
01
Compose
Define the experience and its platform bindings.
-
02
Publish
Release a versioned application definition.
-
03
Execute & inspect
Connect recorded work to its definitions and evidence.
-
04
Improve
Use the observed behavior to inform the next version.
Who builds it
Built visually. Extended in code. Governed either way.
Operations and business analysts
Compose pages, forms, workbenches and dashboards visually around the records and workflows of the business.
Developers
Add custom components, visualizations and integrations through explicit platform contracts.
Security and platform teams
Define identity, tenancy, roles and policy that applications use through the shared execution model.
Start from available application templates, then adapt the records, roles, screens and actions to the process.
For SaaS founders and SI partners
Your product. Your IP. Your revenue.
Build a branded, tenant-aware product around your domain expertise. Keep your customer relationships, pricing and subscription revenue while Frozion provides the governed application, execution and data infrastructure.
- Your brand
- Your customer relationships
- Your pricing
The value of the connected platform
Bring the experience
and execution together.
Each screen can use the application's existing records, permissions, context, state and evidence. The benefit is less application meaning to recreate between the interface and the process.
| Application need | How Frozion connects it | Operational benefit |
|---|---|---|
| A form that starts real work | Bind input to the business schema, validation, policy, mappings and workflow. | Keep what the person submitted connected to what the execution will evaluate. |
| A meaningful human decision | Present the proposal, eligible facts, evidence, policy and required assurance. | Reviewers can inspect why they are being asked to decide and what the decision permits. |
| Work that spans sessions | Display durable workflow state in case pages, task lists and queues. | Users return to the active process with its current status and obligations. |
| AI grounded in the application | Use the active record, permitted context, Feature Store facts and workflow. | Assistance stays relevant to the task and can lead into governed follow-up work. |
| Inspectable business outcomes | Expose decision history, approvals, tool attempts, reported effects and versions. | Give authorized users an explanation in the application where they work. |
| Decide a case together | A real-time case thread connects participants to the proposal and eligible evidence. | Keep questions and decisions with the case. |
Start where the user needs an application
Build one useful experience.
Expand from there.
-
01
Choose a role and a business task.
Start with a reviewer workbench, supplier portal, operational queue, knowledge application or complete business product.
-
02
Connect its records and governed process.
Bind the experience to eligible data, forms, policy, context, permitted actions and the workflow state.
-
03
Publish and inspect the whole journey.
Walk from request to decision, action and reported outcome under the intended roles and scopes.
Work with your existing investments
Add the application experience
where it brings value.
Keep ERP, CRM, databases and specialized operational systems authoritative for their records. Connect existing APIs, identity providers and model services through supported platform capabilities.
Existing agents can keep calling governed workflows. Specialist frontends and workflow systems can coexist where they remain the right fit; App Builder adds the experience around work Frozion governs.
Explore private and hybrid deploymentQuestions application teams ask
Before you build.
No. Existing agents can continue calling Frozion workflows
as tools over HTTPS. App Builder can add the portal,
forms, review workbench, queues and evidence views around
those workflows. You can also build native agents and
complete applications on the same platform from the
beginning.
App Builder composes the user experience. The Control
Plane governs agents, policy, human decisions and durable
workflows. The Data Plane provides operational data,
knowledge, calculated facts, context and provenance. They
share the application model, so screens can use the same
proposal, scope, state and evidence as the process.
Yes. Build experiences for employees, customers, partners
and separate SaaS tenants, with tenant, application,
identity, role, purpose and resource boundaries
participating in composition and execution. Applications
can use their own domain or subdomain and supported
authentication options.
No. The interface reflects the active user's eligible
data, actions and obligations. Server-side composition can
reduce what reaches the browser, while data access and
business operations remain subject to runtime
authorization and policy. A direct request must still
satisfy those controls.
The Control Plane preserves the case independently of the browser session. An authorized reviewer returns through the HITL Inbox or the application, opens the current proposal and continues under current permissions. Approval remains bound to the exact revision reviewed.
Yes. Extend the application through supported custom
components, visualizations, services and integrations.
Existing specialist interfaces can coexist with the
Frozion experience. Use explicit contracts and governed
execution paths to preserve the application's identity,
permissions and workflow semantics.
You retain your application IP, brand, customer
relationships, pricing and subscription revenue. Frozion
provides the governed platform through infrastructure
subscriptions and usage, supporting SaaS founders and SI
partners building their own products and accelerators.
App Builder connects the interface to the same identity, policy, workflow state and evidence used by the agents and business process. Forms start governed work; case views show its state; reviewer decisions return to the execution that requested them.
Operations teams and business analysts compose applications visually. Developers extend them with code and integrations. Security and platform teams define the identity, tenancy and policy model the application uses.
Bring one business task and the people who own it
See the application
your workflow could become.
We'll map the screens, records, roles, decisions and actions
that connect your users to the governed process.