Agent Factory
Open console

Transform cyber and risk operations with AI you can govern.

Agent Factory helps organizations turn established cyber and GRC procedures into controlled, production-ready workflows. It brings together AI agents, enterprise data, deterministic tools and human oversight to improve operational capacity while maintaining accountability, traceability and control.

3execution patterns for controlled workflows
6layers of runtime protection
1reviewable record for every run
experienceCanvasAgent builderDeploy theater
lifecycleRegistryBenchmarksDeploy stamps
Work planeJournalProvenanceArtifacts
controlGatesKill switchFinOpsEvals
knowledgeRetrievalRecordsEnginesTaint rules
partnersA2A discoverHand-offTainted replies
modelsPer-node routingLocal modelsFrontier models
foundationsVaultInjection filtersYour tenancy
journal entry no. 29approval recorded by reviewerclassified on entryusage recordedrouted to local model

An AI-enabled workflow has completed its work.

The platform has recorded the steps performed, the sources used, the controls applied and the decisions made.

Effective oversight starts with visibility. Agent Factory is designed to make workflow activity reviewable at every layer.

01 / 08How are workflows designed?

Turn established procedures into governed workflows.

Describe a process in plain language or configure it visually. The builder creates a structured specification with defined inputs, outputs, permissions and review points, then applies the same validation used at deployment.

02 / 08How are workflows validated?

Build confidence before deployment.

Design, evaluation, deployment and monitoring each produce their own record. The registry maintains a current inventory of workflows, models and tools so teams can assess readiness using evidence from the platform.

03 / 08How is activity recorded?

Maintain a complete record of execution.

Execution journals capture what ran, which sources and tools were used, what changed and which outputs were produced. Provenance links each step to the information and decisions on which it relied.

04 / 08Where do people remain accountable?

Keep people responsible for consequential decisions.

Defined steps can pause for an authorized person to review the evidence and decide how the workflow should proceed. Approval, refusal and operational intervention are retained with the execution record.

05 / 08How is access constrained?

Limit access to what each task requires.

Each workflow step declares the sources, records and tools it may use, with scope limits applied within those permissions. External content remains identified as untrusted as it moves toward consequential actions.

06 / 08How do external agents participate?

Apply consistent controls across agent boundaries.

Partner agents connect through standard interfaces and participate within the same identity, permission and provenance model. Their responses are treated as external content and remain identifiable throughout the workflow.

07 / 08How are models selected?

Select models according to the task.

Workflow steps state their model requirements and the deployment maps those requirements to approved models. Routing can reflect data sensitivity, policy, performance and cost.

08 / 08What applies across the platform?

Embed governance throughout the operating model.

Identity, policy and audit apply across every layer. Credentials are resolved at the point of use, inputs are screened for manipulation attempts and the runtime is designed to operate within the organization’s environment.

One architecture for governed execution.

Each layer contributes the visibility, oversight and operational controls required for enterprise workflows.

Designed for accountable operation.

Deployed within your environment and governed throughout execution.

Turn established procedures into governed workflows.

Describe a process in plain language or configure it visually. Agent Factory translates the procedure into a structured workflow with defined inputs, outputs, permissions and review points, then records the evidence and decisions produced during execution.

Describe the process
typing…
SR
DLP-Triage-SOP.pdfattached
scroll to explore

Combine reusable capabilities with controlled execution patterns.

Reusable capabilities support activities such as evidence extraction, policy analysis and assessment review. Three execution patterns determine whether the next step is defined in advance, selected through inference or dependent on an external decision.

Each capability has a declared contract for its inputs, outputs and permitted tools, helping teams assemble workflows without rebuilding the underlying runtime.

CapabilityActivityReturnsValidation
Evidence extractionextractionTyped record + per-field citationBenchmark required
Control researchresearchFindings with source and recencyBenchmark required
Policy decisiondecisionDisposition + governing clauseBenchmark required
Report draftingdraftingDraft + change logBenchmark required
Assessment reviewreviewFindings with severityBenchmark required
Control mappingdecisionFramework crosswalk + rationaleBenchmark required
Vendor triageresearchRisk summary + evidence linksBenchmark required
Access certificationreviewEntitlement findings + ownerBenchmark required
Incident summarydraftingTimeline + affected assetsBenchmark required
Data classificationextractionLabel + matched policy termsBenchmark required
Human approvalgateApproval + reviewer identityReviewer decision
Declared contract

Typed inputs and outputs, explicit tool permissions and defined exception paths establish what each capability can receive, use and return.

inputsoutputstoolsexceptions
Evaluation before deployment

Representative cases help teams assess quality, cost and execution time before promoting a workflow into production.

representative casesdeterministic grading
Versioned releases

Version history and deployment records help teams understand what changed, what was tested and which specification produced an outcome.

spec digestdeployment recordchange history

Connect workflows to the systems your teams already use.

Declared connector contracts provide governed access to enterprise data, records, tools and services. Each workflow receives only the capabilities and scope required for its purpose, helping organizations extend automation without creating unrestricted access to operational systems.

governedaccess through declared contracts
extensiblefor organization-specific systems

Operate within your technology and control environment.

Agent Factory is designed for deployment within an organization’s cloud environment. Workflows can use approved model endpoints, private data sources and existing operational systems while execution records remain within the organization’s defined boundary.

Controlled connectivityConnect workflows through approved network paths and interfaces
Approved model accessRoute tasks to models made available by the organization
Reviewable recordsRetain run activity, decisions and source references for oversight
Amazon S3Your AWS account· eu-west-2
VPC · private subnets
ECS Fargate
harness containers
Amazon Bedrock
via VPC endpoint
S3 + KMS
audit records and artifacts
IAM roles
static keys not required
VPC endpoints, no internet gateway
external to your tenancy
Agent Factory control plane
workflow definitions and release metadata only
Your systems of record
accessed through declared connectors

Alert evidence, extracted fields and dispositions remain within the defined boundary. Agent Factory provides the workflow definitions; execution occurs in your account.

Deployment boundaryorganization-controlled cloud environment
Infrastructure reviewaligned to approved cloud controls
Operational readinessvalidated before workflow release
Illustrative reference architectureInfrastructure as codeDeployment tailored to the environment
Build plane

Reusable workflow patterns, connector definitions and evaluation capabilities support consistent design and validation.

templatesdata adaptorsIaC
Agent runtime

Workers execute workflow specifications using approved models and tools under defined runtime limits and controls.

ephemeral workersorchestratorapproved tools
Work plane

A durable registry and execution journal retain workflow state, provenance and the evidence associated with each run.

execution ledgerwatchdogprovenance
Control plane

Identity, permissions, policy decisions, human review and operational intervention are applied across workflow execution.

least privilegeguardrailsFinOpskill switch
Integration gateway

Standard interfaces connect enterprise platforms while controls govern the information and actions that cross each boundary.

MCPA2ARESTwebhooks
Model consumption

Model routing can reflect task requirements, data sensitivity, organizational policy, performance and cost.

model gardenself-hostedfrontier endpoints

Trace outcomes to the evidence and decisions behind them.

Agent Factory maintains a reviewable record of workflow execution. Teams can examine which information was used, how it moved through the workflow, where controls were applied and when human judgment affected the outcome.

Reviewers examining alert evidence together
Review each run with end-to-end traceabilityExamine the execution timeline and trace an outcome to the relevant policy, business record, source material and reviewer decision.
Least-privilege accessTools and data scope are assigned to individual workflow steps
Human oversightDefined decisions can pause for review by authorized people
Untrusted-content controlsExternal content remains identified as it moves through a workflow
Execution provenanceSources, tool activity, decisions and outputs are retained in the run record
Operational interventionAuthorized operators can stop active runs and record the intervention