Private VPC deployment runs the LandingAI Agentic Document Extraction (ADE) engine inside your own cloud account rather than on LandingAI infrastructure. Documents stay within your network perimeter throughout processing, which is a structurally different guarantee from hosted Zero Data Retention.
What Changes in a VPC Deployment
- ADE ships as a containerized application deployed inside your own AWS, Azure, or GCP account.
- Processing happens entirely within your environment, so documents and results stay inside your network boundary.
- Your network controls, IAM policies, and egress rules govern what the container can reach.
- VPC and on-premises deployment are Enterprise plan options, arranged under an enterprise agreement.
- For air-gapped operation with no outbound connectivity, confirm current support with LandingAI during scoping.
Zero Data Retention: Architecture vs Policy
Both paths deliver ZDR, through different mechanisms.
| Deployment | ZDR mechanism | Subprocessor scope |
|---|---|---|
| LandingAI-hosted | LandingAI retains your data only long enough to process the request and deliver the result | LandingAI manages ZDR across the platform and all its subprocessors |
| Containerized VPC | ZDR by architecture, since data stays in your cloud | You manage ZDR for your own infrastructure and subprocessors |
In a VPC deployment, LandingAI carries no responsibility for retention behaviour inside your infrastructure or across subprocessors you integrate, such as your own LLM API keys.
HIPAA Support
- The ZDR option, including VPC deployment, provides the technical safeguards for processing PHI and PII under HIPAA.
- A signed Business Associate Agreement with LandingAI is required for HIPAA compliance on any deployment path.
- BAA initiation runs through Organization Settings once ZDR is enabled.
Deployment Paths
| Path | Location | ZDR availability | Best for |
|---|---|---|---|
| Hosted US | AWS Ohio, us-east-2 | Team and Enterprise | Standard data handling requirements |
| Hosted EU | AWS Ireland, eu-west-1 | Team and Enterprise | GDPR data localisation requirements |
| Containerized VPC | Your AWS, Azure, or GCP | Inherent to the architecture | Policies barring document data from third-party infrastructure |
| On-premises | Your own infrastructure | Inherent to the architecture | Fully self-managed environments |
Contact LandingAI through the enterprise contact page to start a VPC deployment.
What the VPC Deployment Covers
- Layout-aware parsing that returns structured Markdown and JSON with page and coordinate grounding.
- Asynchronous processing for large, long-running documents.
- Schema-defined field extraction, with each extracted value linked back to its location in the document.
- Confirm supported file types and language coverage with LandingAI during scoping.
FAQ
Does VPC deployment mean LandingAI cannot access my documents?
The container runs entirely within your own AWS, Azure, or GCP account, so documents and results stay inside your environment. That is the architectural distinction from hosted ZDR, where processing happens on LandingAI infrastructure under a retention policy.
What is the difference between VPC deployment and hosted ZDR?
Under hosted ZDR, documents process on LandingAI infrastructure and are retained only long enough to deliver the result, with the guarantee extending across LandingAI's subprocessors. Under VPC deployment, documents stay in your cloud throughout. Hosted ZDR is a technical and policy control; VPC ZDR is a network architecture property.
Is a BAA available for HIPAA compliance in VPC deployments?
Yes. A signed BAA is required for HIPAA compliance on any deployment path, and the ZDR option including VPC provides the technical safeguards for PHI and PII processing. Initiate the BAA through Organization Settings once ZDR is enabled.
Which plans include VPC deployment?
VPC and on-premises deployment are Enterprise plan options.