Skip to main content
Hybrid VPC deployment provides a balance between data sovereignty and operational simplicity. Your data stays in your cloud account while Reducto manages all compute infrastructure.

Overview

In a Hybrid VPC deployment:
  • Data stays in your cloud account: Documents you upload, intermediate artifacts, and results are stored in your storage
  • Compute runs on Reducto’s infrastructure: GPU processing and model inference are handled by Reducto
  • You control retention: Objects stay in your storage until your lifecycle rule or retention policy deletes them
  • Multiple storage providers: AWS S3, Azure Blob Storage, Google Cloud Storage, and Box are supported
  • Three regions: US, EU, and AU, each with its own API endpoint

AWS S3

Cross-account IAM role with ExternalId protection. Optional PrivateLink for private-only API access.

Azure Blob Storage

A managed identity in your tenant with no stored secret, or a Storage account connection string. Reducto signs read-only SAS links.

Box

Box enterprise app with Client Credentials Grant. Ideal for organizations already using Box for document management.

Google Cloud Storage

A service account key that you scope to one bucket. Configure it yourself in Studio.

Key benefits

Regions

Each Reducto region has its own API endpoint. Send each request to the region whose storage it should use. A request fails if it selects storage in another region’s area, for example an EU bucket on platform.reducto.ai. For EU processing guarantees, see EU data residency.
The AU region runs /parse on the R-1 model only. For most organizations, /extract, /split, /classify, /edit, and /pipeline return 403 REGION_UNAVAILABLE on au.platform.reducto.ai, and so do parse options that need OCR or other models. Contact Reducto before you plan an AU deployment to confirm what your organization can use.

Architecture

Data flow

  1. You upload documents to your storage (or use Reducto’s /upload endpoint, which writes to your storage)
  2. You call the Reducto API with a reference to your document
  3. Reducto uses your configured credentials to access the document
  4. Processing occurs on Reducto’s compute infrastructure
  5. Results and artifacts are written back to your storage. Large results and images come back as links to objects in your storage (see your provider guide for the link format and expiry)
  6. Objects expire based on the lifecycle rule you configure on your storage
Reducto’s database keeps a record of each job, such as its status, request settings, and where its result is stored. GET /job/{job_id} reads an async job’s result from your storage.

Choosing a Storage Provider

Best choice if your organization uses Azure. Reducto signs in as a user-assigned managed identity in your tenant through a federated credential, so you give Reducto no secret and can disable shared key access. A Storage account connection string with an account key is also supported. Terraform configuration provided for automated setup.
Best choice if your organization already manages documents in Box. Uses Box enterprise app authentication (Client Credentials Grant). No Terraform provider available — setup is done through the Box Admin Console.
Best choice if your organization uses GCP. Reducto accesses your bucket with a service account key that you create and scope to the bucket. You add the environment and verify access in Studio.

Document Handoff

There are multiple ways to provide documents to Reducto APIs, regardless of which storage provider you use: Document handoff is a trust boundary. Only trusted services should submit document URLs or uploads to Reducto. If a caller can submit arbitrary URLs, that caller can ask Reducto to fetch any network location reachable from the deployment or hybrid worker environment. Use your gateway, storage policy, and egress policy to limit what callers can request.
Use Reducto’s /upload endpoint to upload documents directly. Files are stored in your configured storage:
/upload has no request settings, so it writes to your default environment. To upload into a named environment, pass the hybrid_vpc_environment query parameter, and select the same environment on the request that reads the file:
For production workflows:
  • Prefer direct uploads, reducto:// file IDs, or tightly scoped storage-provider URLs.
  • Keep presigned URLs short-lived and scoped to a single object.
  • Do not pass URLs containing long-lived credentials.
  • Restrict worker egress to expected document sources when your workflow allows it.
  • Block cloud metadata endpoints and internal admin services from document-fetching egress.
For PrivateLink connections (AWS only), specify the region-specific hybrid endpoint as base_url:
  • US: https://hybrid.platform.reducto.ai
  • EU: https://hybrid.eu.platform.reducto.ai
  • AU: https://hybrid.au.platform.reducto.ai

Integration Contract

Reducto registers your storage as a Hybrid VPC environment for your organization. For AWS S3 and Google Cloud Storage, an organization admin can add, verify, and edit environments in Studio under Settings → Hybrid VPC once Reducto turns this on for your organization. For Azure and Box, or if you do not see the Hybrid VPC tab, send the values below to Reducto, along with the region (US, EU, or AU) that processes each environment’s documents.

Multi-Region Setup

For organizations needing storage in multiple regions for latency or compliance requirements, register one environment per region and set a default environment for each region you use. A request that does not select an environment uses the default for the region it is sent to (US, EU, or AU). See the provider-specific setup guides linked above for region-specific credentials.

Multiple Environments

If one Reducto organization needs multiple dedicated storage locations, Reducto can register named Hybrid VPC environments under the same org. Each environment points to one bucket, container, or folder, with its own credentials and region. Then select the environment per request:
The field that selects the environment depends on the endpoint:
On /extract and /split, a top-level settings.hybrid_vpc is ignored and the job uses your default environment. Put the environment under parsing.settings:
A request without an environment uses the default environment for its region. A request fails if it names an environment that is not configured, or one whose storage region is outside the API region’s area. Use separate Reducto orgs only when you need separate API keys, admins, billing, quotas, or customer-visible tenancy. For client-specific buckets inside the same customer account, named environments are the recommended path.

Security

All storage integrations follow least-privilege principles:
  • AWS: ExternalId prevents confused deputy attacks; IAM policy limits access to S3 operations only
  • Azure: A managed identity whose federated credential trusts only your Reducto organization, with no stored secret; or an account key in a connection string for a dedicated Storage account. Responses carry read-only SAS links that expire within 12 hours
  • Google Cloud Storage: A service account key that you scope to the bucket and rotate on your own schedule. Responses carry signed links that expire after 12 hours
  • Box: An App Access Only service account that sees only the folders you invite it to; enterprise admin approval required
  • All providers: Configure a lifecycle rule or retention policy on your storage to delete Reducto objects after processing