Deployment roadmap and trust

Private cloud document AI on the roadmap.

Private VPC deployment, customer-managed keys, AWS PrivateLink, and Google Cloud Private Service Connect are roadmap capabilities. They are not generally available unless explicitly included in a signed deployment scope.

Why private cloud is on the roadmap

Regulated production workflows may require dedicated infrastructure, VPC peering, customer-managed keys, region pinning, strict data retention, and audit evidence. This page describes evaluation criteria and intended direction, not currently committed availability.

Private VPC roadmap

Planned capability for a dedicated network boundary with tenant-scoped ingress, egress, logs, and secrets.

Retention controls

Set document data retention by workflow, including zero data retention beyond request processing when the use case requires it.

Audit evidence

Export model version, region, reviewer, validation, and webhook evidence for compliance review.

Current and planned deployment options

OptionBest fitControls
Shared cloud tenantStandard API and portal workflowsTenant isolation, encryption, regional residency, configurable retention
Dedicated tenantEnterprise procurement and higher-volume workflowsDedicated keys, rate limits, stricter access controls, custom DPA terms
Private VPC deployment — roadmapRegulated buyers with requirements beyond shared SaaSPlanned private networking, BYOK/CMEK, and customer-specific boundaries
Controlled single-tenant cloud — roadmapCustomers evaluating operational isolationPlanned single-tenant compute and customer-specific observability boundaries

Zero data retention and audit retention are different

Zero data retention means source documents and extracted content can be discarded after request processing. Audit metadata is a separate record: request ID, timestamps, model version, validation status, reviewer activity, and export decisions can be retained under your contract so compliance teams can still reconstruct what happened.

Private cloud evaluation checklist

Ask every document AI vendor where inference runs, whether embeddings leave the selected region, whether document bodies appear in logs, whether LLM sub-processors use zero-retention APIs, how key revocation works, and whether the audit trail records deployment region and model version. For Cogneris, confirm current availability in a signed deployment scope rather than relying on roadmap language.

Related pages