Deployment

Four deployment models.

Managed cloud, customer VPC, on-premise, or hybrid. Region pinning available. Provisioning SLAs and rollback guarantees written into the SOW. Choose the model that matches your data residency, network, and procurement requirements.

The Enterprise clause · on engagement

Private, air-gapped deployment in your own cloud.

Under an Enterprise engagement, the entire system is designed to be packaged into containers and deployed privately inside your own VPC on AWS or Azure — or fully air-gapped behind your firewall — so your documents and data never leave your perimeter.

In that mode the platform runs against locally hosted, adapted models instead of a shared cloud provider, which keeps inference inside your environment and supports strict data-sovereignty regimes such as GDPR and HIPAA (HIPAA-ready under an Enterprise engagement).

This is configured per engagement and written into the SOW, with the controls and residency commitments your procurement and security teams require.

“Your data sovereignty, your perimeter, your compliance regime — engineered into the deployment, not bolted on after.”

Model 01 · Default

Managed cloud

We host the tenant on our infrastructure (Render + AWS). Fastest path to production. Standard for Quick Start engagements.

Provisioning: < 5 minutes
Region: us-east-1 default
Multi-tenant DB: no

Model 02

Customer VPC

Deployment runs inside your AWS / GCP / Azure account. Network controlled by you. We retain operational responsibility via a least-privilege role.

Provisioning: 5–10 business days
Region: your choice
Network access: your IAM

Model 03

On-premise

Docker Compose or Kubernetes Helm chart for self-hosted deployment behind your firewall. Air-gapped operation supported with a pinned LLM provider or local inference.

Provisioning: 2–4 weeks
Air-gap: supported
Update cadence: customer-controlled

Model 04

Hybrid

Sensitive data layer (documents, audit log) stays on-prem; orchestration plane is managed by us. Useful when data residency rules out cloud but ops capacity is limited.

Provisioning: 3–6 weeks
Data plane: on-prem
Control plane: managed

Capability matrix

What each model gives you.

CapabilityManagedVPCOn-premHybrid
Region pinningus-east-1✓ any✓ any✓ any
Customer KMS / BYOK
VPC peering / PrivateLinknative
Air-gapped operation
Local LLM inferencescopedscoped
Customer-managed updatesopt-inpartial
Multi-region failoveron engagementcustomer's responsibilityon engagement
SOC 2 audit boundaryour boundaryyour boundaryyour boundaryshared

Provisioning

From SOW signature to live tenant.

T+0
SOW signed
50% invoice issued
T+1d
Tenant config
firm_id · industry · RBAC roles
T+2d
Workflows loaded
vertical template pack provisioned
T+3d
Integrations wired
Gmail / O365 / Slack / IdP
T+5d
Cutover
production keys · monitoring on

Above timeline assumes managed-cloud. VPC: add 5–10 business days for network access and IAM role review. On-prem: add 2–4 weeks for environment validation. All commitments are written into the SOW with explicit milestones — no vague "soon".

Rollback & change management

Every change is reversible.

Workflow definitions are versioned per tenant. Promoting a new version does not delete the previous — operators can revert with a single call (POST /api/v1/workflows/{firm_id}/{wf_id}/rollback). The Operational Time Machine records intent, params, and decision context for every approval, so post-incident review reconstructs exactly what an operator (or agent) saw.

Platform upgrades on managed cloud are blue-green: traffic shifts only after the new revision passes health checks. Managed-cloud customers get a 24-hour change window opt-out; VPC and on-prem customers control their own upgrade cadence.

Tenant-level "freeze" is available — pauses all agent action while keeping read APIs live. Used during sensitive periods (M&A diligence, year-end close, regulator visits).

Service-level commitments

Written into the SOW.

MetricQuick StartProfessionalEnterprise
Uptime target (managed)set in SOWset in SOWset in SOW + credits where agreed
Provisioning timelinetarget: ~5 business daystarget: ~5 business daysnegotiated
Incident handlingAuto-classified (P1/P2/P3)Auto-classified (P1/P2/P3)+ response targets in SOW
Backup & restoredaily · 30d retentionhourly · 90d retentioncontinuous · custom
Audit log retention1 year3 years7+ years