docs-mintlify/admin/deployment/dedicated/index.mdx
Cube offers two flavors of single-tenant deployment: Dedicated Infrastructure managed by Cube in our cloud accounts, and Bring Your Own Cloud (BYOC) managed by Cube inside your own cloud account. Both options give you isolated compute, the ability to route traffic over private networks, and integrations with services in your VPC or VNet.
<Note>Available on the Enterprise plan with the Dedicated Infrastructure add-on.
</Note>With Dedicated Infrastructure, Cube provisions and operates a single-tenant cluster for you in a Cube-managed account on AWS, GCP, or Azure. Single-tenant means the cluster — VPC/VNet, compute, storage, and the Cube data plane that runs your deployments — is dedicated entirely to your organization and not shared with any other customer. The cluster lives in a Cube Region, can be peered or PrivateLink/PSC-connected to your own networks, and can optionally expose Cube's APIs to your network so that no Cube traffic ever crosses the public internet.
On the Enterprise plan, Cube is also available as Bring Your Own Cloud: all components that interact with your private data are deployed inside your own AWS, Azure, or GCP account and managed remotely by the Cube Control Plane via the Cube Operator. This keeps all data plane resources within your boundary while preserving the managed-service experience. Contact us for details.
There are two distinct directions in which Cube exchanges traffic with your network, and each has its own connectivity story:
Most enterprise deployments end up using both: a backend PrivateLink/PSC/peering into the customer's data network, plus a frontend private API endpoint so the Cube UI and BI tools talk to Cube over the same private fabric.