How ADE supports distributed enterprise teams processing documents across departments and regions through shared infrastructure and regional data residency.
Global enterprises run document workflows across legal, finance, procurement, and compliance simultaneously, often in different regions with different data residency requirements. ADE's API-first architecture supports this through organisation-level access control, multi-key API management, EU and US regional endpoints, and rate limits that scale by plan tier.
Shared Infrastructure, Separate Access Control
Multiple teams within the same organisation can access ADE through the same account or separate accounts depending on the isolation required. Within a single organisation, ADE supports multiple API keys with individual revocation capability on Team and above plans, as documented in organisation and members administration.
For teams requiring full account isolation (separate billing, separate rate limit pools, or separate ZDR configurations), separate LandingAI organisations provide complete separation.
Regional Data Residency
ADE is available in two hosted regions:
- US region. AWS Ohio (us-east-2), with ZDR available on Team and Enterprise plans.
- EU region. AWS Ireland (eu-west-1), with ZDR available on custom pricing plans. See EU documentation for endpoint configuration.
Both regions expose the same Parse API, Extract API, and Parse Jobs API with identical schemas and outputs.
Rate Limits Across Teams
Rate limits are set at the organisation level and distributed per minute across all API keys in the organisation; on Enterprise plans, limits are customisable. See rate limits documentation for current per-plan thresholds.
The List Parse Jobs endpoint returns all jobs associated with an API key, supporting per-team monitoring when teams use separate keys.
Extraction Schema Management Across Teams
Extraction schemas are stored and versioned in the calling application, not in the ADE platform. Centralising schema definitions in a shared schema repository enables multiple teams to share schemas for common document types while maintaining per-team extensions for team-specific fields.
Schema changes that add required fields or modify field types should follow a versioned migration pattern; see extraction schema documentation for design guidance.
FAQ
Can different departments use separate API keys with separate rate limit pools? Rate limits are set at the organisation level and apply across all API keys within it; they are not separately pooled per key. For complete rate limit isolation between departments, separate LandingAI organisations provide separate billing and rate limit pools.
Within a single organisation, multiple keys with individual revocation support team-level access control.
How does ADE support EU data residency requirements? Documents processed through the EU endpoint (AWS Ireland, eu-west-1) remain within the EU during processing; ZDR is available on custom pricing plans for EU organisations. See EU documentation for endpoint configuration.
Can the same extraction schema be used across US and EU endpoints? Yes. Extraction schemas are client-side configuration that works identically across regions; the same schema submitted to either endpoint produces equivalent structured output.
How should organisations manage schema versioning across multiple teams? Store extraction schema files as versioned code alongside application code and maintain a shared schema repository for common document types. See extraction schema best practices for guidance.
Is VPC deployment available for organisations requiring data to remain entirely within their own infrastructure? Yes. VPC deployment runs ADE within the customer's own AWS, Azure, or GCP environment; no document data transits LandingAI infrastructure during processing.
VPC deployment requires an enterprise agreement; contact LandingAI through the enterprise contact page.