TRUST & CONTROL

Governance around every workflow.

Make access roles, consent, customer keys, audit records and human responsibility part of your security and compliance review. Confirm the controls and evidence for your configured deployment.

SECURITY THROUGH THE STACK

01

Identity at entry

OAuth2 / OIDC · RBAC · tenancy

02

Keys under your control

Customer keys · Vault · scoped credentials

03

Rules around each action

Consent · PII guardrails · permitted tools

04

A record of the operation

Audit · agent versions · human decisions

Review trust & controls
Approved channel / API ingress
Customer-controlled cloud boundaryConceptual placement
KubernetesRuntime placement · not a live server monitor
Agent runtime

Orchestration · state · campaign engine

Connector execution

Permitted enterprise actions

Speech / reasoning placementApproved hosted or local model services
PostgreSQLRedisOpenSearch
DEPLOY & OPERATE
TerraformGitLabOpenTelemetryGrafana
Explicitly reviewed external connections
Telephony · messaging · email · hosted identity · external models if selected

Network routes, identity, data placement and provider connections must be agreed for the chosen cloud configuration. Controls shown here are from the reference architecture; implementation and security evidence are reviewed for your deployment.

Evaluate the evidence for your configuration.

These are controls described in the reference architecture, not a certification statement. Request approved security documentation, implementation evidence and an external-dependency review for your deployment.

START WITH ONE WORKFLOW

Bring your SOP. Let’s map the first process.

Define the task, connect the systems and agree what a useful pilot should prove.

Discuss a workflow pilot