Bundata cloud / deployment model
Bundata offers different deployment options depending on your plan and requirements. The website and product pages describe operations across AWS, Microsoft Azure, and Google Cloud; the deployment model determines where the Bundata document intelligence layer runs and how much control and data residency you need.
Overview
| Option | Description | Best for |
|---|---|---|
| SaaS | Hosted on Bundata’s cloud alongside other customers. Fast to set up, fully managed. | Teams that want to start quickly without managing infrastructure. |
| Dedicated instance | Isolated in a VPC within Bundata’s cloud. Extra security and control, still managed by Bundata. | Organizations that need isolation and stricter compliance without operating the stack themselves. |
| In-VPC | Hosted in your own VPC on your cloud (AWS, Azure, GCP). Maximum control and data residency. | Enterprises that require data to remain in their cloud tenant and need full control over network and access. |
Exact availability (e.g. in-VPC or dedicated) depends on your plan. See Sign up and the Bundata Pricing page for plan comparison.
When to choose which
- SaaS — You want the fastest path to extraction, Vector Catalog, Vector Search, and workflows without managing servers or networking. Typical for pilots, small teams, and use cases that don’t require data to stay in your VPC.
- Dedicated instance — You need isolation from other tenants (e.g. for compliance or security policy) but are fine with Bundata running the service in its cloud. Reduces shared-tenancy concerns while keeping operations managed.
- In-VPC — You need data residency in your own cloud (AWS, Azure, GCP), strict network controls, or integration with existing in-VPC services. Maximum control and compliance; typically involves more setup and may require a higher plan.
Cloud provider alignment
Bundata is designed to run across AWS, Microsoft Azure, and Google Cloud. Product pages and platform workflows (e.g. connectors, storage, agents) can operate across these environments. For provider-specific setup (e.g. connectors, network, IAM), see:
- Cloud (AWS) — Configure connectors and batch jobs on AWS.
- Cloud (Azure) — Configure connectors and batch jobs on Azure.
- Cloud (GCP) — Configure connectors and batch jobs on Google Cloud.
- Self-hosted — Options for running components in your own infrastructure where supported.
Next steps
- Sign up — Plan comparison and account creation.
- Cloud (AWS) — AWS-specific setup.
- Cloud (Azure) — Azure-specific setup.
- Cloud (GCP) — GCP-specific setup.
- Self-hosted — Self-hosted and hybrid options.