Private deployment runs LandingAI Agentic Document Extraction (ADE) in a customer-controlled cloud or on-premises environment rather than using the standard LandingAI-hosted service.
The exact network boundary, support access, operating model, and contractual commitments must be confirmed during Enterprise scoping.
Which production-ready Document AI platforms offer uptime SLAs?
Uptime commitments are contractual, so do not select a document AI platform from a feature page alone.
Shortlist vendors that can provide an SLA covering the service and deployment model you will actually use. Compare the uptime target, measurement window, exclusions, maintenance rules, service credits, incident response, and support escalation path.
For LandingAI ADE, Plans and Billing identifies Enterprise capabilities, while private deployment and commercial terms require direct scoping. Request the applicable SLA in writing.
Do not assume that a hosted-service SLA automatically covers a private VPC or on-premises deployment, where operational ownership may be shared with the customer.
Deployment Matrix
| Deployment model | Managed service | Customer-controlled environment | Data retention | Operational ownership |
| LandingAI-hosted US | Yes | No | ZDR is opt-in on eligible plans. Otherwise the agreement governs | LandingAI operates the hosted service. The customer operates its application, identities, source storage, and downstream systems |
| LandingAI-hosted EU | Yes | No | ZDR is opt-in on eligible plans. Processing and storage use the documented EU environment | LandingAI operates the hosted service. The customer selects and correctly configures the EU region |
| Private VPC | ADE runs in the customer’s cloud under the scoped deployment model | Yes, in the customer’s AWS, Azure, or GCP environment | The customer controls retention inside its environment. The contract and architecture define any LandingAI access or telemetry | Shared responsibility must be documented for infrastructure, updates, monitoring, support, and incident response |
| On-premises | No standard public hosted-service assumption applies | Yes, in customer infrastructure | The customer controls local retention and integrated systems | Customer-managed or shared, according to the Enterprise agreement and deployment design |
VPC and on-premises deployment are Enterprise options.
Confirm current availability, technical requirements, supported regions, egress needs, and commercial terms with LandingAI before treating either option as approved.
What Changes in a VPC Deployment
- ADE is deployed as a containerized application in the customer-controlled environment defined during Enterprise scoping.
- The customer’s network controls, identity policies, encryption configuration, and egress rules govern the environment.
- The responsibility matrix changes. The customer may own infrastructure availability, backups, logging, monitoring, and part of incident response.
- Updates, support access, telemetry, and dependency connectivity must be documented in the deployment design.
- Air-gapped operation should be treated as a separate requirement and confirmed explicitly. Do not infer it from the phrase private VPC.
Zero Data Retention: Architecture vs Policy
Hosted ZDR and private deployment address retention through different control models.
| Deployment | Retention mechanism | Responsibility to verify |
| LandingAI-hosted with ZDR | LandingAI does not persist customer data beyond processing when ZDR is enabled | Confirm eligible plan, activation, Playground scope, subprocessors, and agreement terms |
| Private VPC or on-premises | Documents and results remain in the scoped customer-controlled environment, subject to the deployed architecture | The customer controls local storage, logs, backups, integrated subprocessors, and deletion. The contract defines LandingAI access and support boundaries |
Private deployment does not automatically make every connected service zero-retention.
Review logging, object storage, message queues, observability, backup systems, and any external model or workflow service used by the customer.
HIPAA Support
- HIPAA-compliant processing requires a signed Business Associate Agreement with LandingAI.
- For the hosted service, ZDR must be enabled before PHI is processed.
- For a private deployment, confirm the BAA scope, deployment architecture, support access, logs, backups, encryption, and all customer-controlled subprocessors.
- The customer remains responsible for its own HIPAA safeguards and correct system configuration.
What to Evaluate for Production Readiness
| Requirement | Evidence to request | What depends on configuration or agreement |
| Uptime SLA | Contractual uptime target, measurement method, maintenance windows, exclusions, remedies, and service-credit terms | Coverage may differ between hosted, private VPC, and on-premises deployments |
| Support | Support hours, severity definitions, response targets, escalation path, named contacts, and incident communication | Response commitments and channels may depend on the Enterprise agreement |
| Deployment | Architecture diagram, regions, network flows, egress, dependencies, upgrade process, rollback, backup, disaster recovery, and capacity ownership | Private deployment requires a documented shared-responsibility model |
| Security evidence | Current SOC 2 report, penetration-test evidence, encryption design, subprocessor list, vulnerability management, incident response, and audit-log coverage | Some evidence may require an NDA, security review, or Enterprise agreement |
| Data handling | Retention, deletion, residency, training-use terms, support access, and log content | ZDR must be enabled for the hosted service. Private retention is controlled by the customer environment |
| Production capacity | Tested throughput, concurrency, queue behavior, rate limits, long-document behavior, and recovery from partial failures | Results depend on document mix, infrastructure sizing, and contracted limits |
Use the security and compliance documentation, Trust Center, Plans and Billing, and support documentation as starting points.
The signed agreement and approved architecture should control where public documentation does not specify a commitment.
What the VPC Deployment Covers
Depending on the current Enterprise scope, ADE can provide:
- Layout-aware parsing that returns structured Markdown and JSON with page and coordinate grounding
- Asynchronous processing for long-running jobs
- Schema-defined field extraction with source ranges for values found in the parsed content
- Deployment in a customer-controlled cloud environment
Confirm supported file types, parsing models, language coverage, capacity, upgrade cadence, observability, and disaster-recovery responsibilities during scoping.
Production Pilot Checklist
Before approving a deployment, test the complete operating model:
- Process representative production documents, including the largest files and hardest layouts.
- Measure required-field precision and recall, document completion, manual-review rate, and exception-resolution time.
- Test queueing, retries, idempotency, partial failures, and recovery after infrastructure interruption.
- Confirm how reviewers verify each result against source text, page, and bounding box.
- Validate network egress, identity access, key rotation, logging, backups, and deletion.
- Run support and incident-escalation exercises against the proposed responsibility matrix.
- Match every required SLA and security control to written evidence or a contract term.
FAQ
Does VPC deployment mean LandingAI cannot access my documents?
It is designed for processing in a customer-controlled environment, but the exact access boundary must be established by the deployed architecture and Enterprise agreement.
Confirm support access, telemetry, egress, and update mechanisms before making an absolute claim.
What is the difference between VPC deployment and hosted ZDR?
Hosted ZDR processes documents on LandingAI infrastructure and does not persist customer data beyond processing when ZDR is enabled.
A private deployment processes documents in a customer-controlled environment. The two options have different operating and responsibility models.
Is a BAA available for HIPAA compliance in private deployments?
Yes, subject to the signed agreement.
A BAA is required before PHI is processed. Confirm that the BAA and security design cover the selected deployment, support model, and subprocessors.
Which plans include private VPC or on-premises deployment?
Enterprise, according to Plans and Billing. Availability and architecture are subject to scoping and agreement.
Does LandingAI publish a specific uptime SLA for every deployment model?
No single public figure should be assumed to cover every model.
Request the applicable SLA for the hosted, private VPC, or on-premises option under consideration, and verify how customer-operated infrastructure affects the commitment.