12 min
A guide to Bring Your Own Cloud (BYOC) for enterprise leaders
Learn what BYOC is and how Bring Your Own Cloud splits the control and data planes for enterprise workloads.

Enterprises moving mission-critical workloads to third-party software often hit a hard security boundary: sensitive customer data, proprietary code execution, and managed credentials cannot leave their cloud perimeter.
While standard SaaS simplifies operations, security and compliance teams increasingly reject multi-tenant hosting for sensitive pipelines, driving demand for Bring Your Own Cloud (BYOC).
By decoupling the management interface from workload execution, BYOC gives enterprise buyers full ownership of their data plane, network isolation, and infrastructure spend while relying on vendors for continuous orchestration and maintenance.
Buyers ask for agent infrastructure because agents execute code against credentials and customer data. Security leads want that execution inside an account they already audit.
Key takeaways
- Vendors push upgrades per deployment. You own the account, IAM, quotas, and the cloud bill.
- No regulation mandates BYOC. GDPR, HIPAA, and PCI DSS set conditions on data access and transfers instead.
- Keeping data in your account doesn't guarantee security. Vendors still assume an IAM role in your account to troubleshoot.
- Sandbox vendors define BYOC differently. E2B runs clusters in your VPC, while Daytona's BYOC means bring your own compute.
What is BYOC?
Bring your own cloud (BYOC) is a deployment model where a vendor's data plane runs inside the customer's cloud account. The vendor still operates the control plane and handles upgrades and monitoring. Your data and compute stay in your virtual private cloud (VPC).
The meaning of BYOC rests on one architectural split.
A BYOC vendor divides its product into a control plane and a data plane:
- The control plane handles provisioning, upgrades, monitoring, authentication, and billing.
- The data plane runs workloads and stores data.
In BYOC, only the data plane moves into your AWS, Google Cloud, or Azure account. ClickHouse's BYOC architecture is a clean example. Its control plane services orchestrate the deployment but do not store customer data.
The model began in data infrastructure. Redpanda says its BYOC first launched in 2022. Per its BYOC architecture docs, Redpanda deploys clusters into AWS, Azure, or Google Cloud. Customer data never leaves the data plane.
Clusters stay available if the link to the control plane drops. Confluent and StreamNative now ship versions of the same split. Confluent frames BYOC as a data sovereignty choice. Its BYOC explainer adds that the model isn't inherently more secure.
Bring your own cloud vs other BYOC meanings
BYOC has three common meanings. Context usually settles which one a document intends:
| Term | Meaning | Context clues | Typical vendors |
|---|---|---|---|
| Bring your own cloud | Vendor data plane runs in your cloud account under a vendor control plane | Control plane, data plane, VPC, cross-account roles | Redpanda, ClickHouse, E2B |
| Bring your own carrier | Your telecom carrier connects to a contact center over Session Initiation Protocol (SIP) trunks | SIP trunks, public telephone network, phone numbers, carrier contracts | Genesys Cloud, Twilio, Talkdesk |
| Bring your own certificate | You supply your own TLS certificate to a cloud service | TLS, CDN, managed certificates | Azure Front Door |
Genesys splits its carrier offering in two. BYOC Cloud runs SIP trunks into Genesys media resources in AWS. BYOC Premises runs trunks to on-site Edge hardware. Neither runs Genesys software in your cloud account.
In observability, one BYOC variant keeps data in your own bucket. Kloudfuse lists it as "your bucket, their compute," so data still travels to the vendor.
BYOC vs SaaS, self-hosted, on-prem, and air-gapped deployment
Procurement and security teams score deployment models on five axes. The security review row describes the scope of each review.
| Axis | SaaS | BYOC | Self-hosted | On-prem | Air-gapped |
|---|---|---|---|---|---|
| Data residency | Vendor's account and regions | Your cloud account, telemetry to vendor | Your cloud account | Your data center | Your facility, no outbound internet |
| Ops burden | Vendor runs everything | Shared. You own the account, IAM, and quotas | You run software and infrastructure | You also run hardware and power | Fully customer-operated |
| Upgrades | Vendor, all tenants at once | Vendor-pushed per deployment | You | You | Offline update bundles |
| Security review | Vendor certifications and questionnaire | Certifications plus cross-account IAM review | Your own controls | Your controls plus physical security | Accreditation of an isolated site |
| Cost | Infrastructure bundled into vendor price | Software fee plus your cloud bill | Cloud bill plus platform staff | Hardware, facilities, and staff | Offline tooling and specialists |
In BYOC vs SaaS pricing, cost turns on who keeps the infrastructure margin. A Kong-sponsored post on The New Stack argues that SaaS vendors hosting the data plane often mark up infrastructure. BYOC moves that spend into your account at your negotiated rates.
An Aiven-sponsored post on the same site sets a spend threshold. Below a few million dollars in annual cloud spend, BYOC may not make sense.
Why enterprises ask for BYOC
Regulations set conditions on access and transfers, but none mandates a deployment model.
Requests come from sovereignty strategy, regulation, and cloud spend commitments:
- Data sovereignty: Gartner predicts over 50% of multinationals will have digital sovereign strategies by 2029, up from under 10%.
- GDPR: Chapter V of the General Data Protection Regulation allows transfers under adequacy decisions or appropriate safeguards. The rules don't require storage in the EU.
- HIPAA: Under the Health Insurance Portability and Accountability Act, HHS treats cloud providers as business associates. The status applies when they maintain electronic protected health information, even without decryption keys. Covered entities need a business associate agreement (BAA) with cloud providers that maintain that information on their behalf.
- PCI DSS: The Payment Card Industry Data Security Standard's provider guidance requires a responsibility record. The record lists which requirements each provider manages and which remain your responsibility.
- Committed discounts: BYOC spend lands on your cloud bill. Vendors claim this spend counts toward AWS or Azure commitments. Confirm that with your cloud provider for direct infrastructure. For marketplace purchases, AWS says products deployed on AWS typically qualify.
Vendors also pitch faster security reviews, mainly to banks and healthcare teams with data in HIPAA-eligible accounts. The regulation that constrains your deployment decides whether BYOC changes anything. Your compliance team can name it.
How BYOC works at scale
BYOC splits access, connectivity, upgrades, and billing between you and the vendor:
- Cross-account access: On AWS, you create an identity and access management (IAM) role, and the vendor assumes it. AWS IAM guidance says the vendor generates a unique external ID per customer. The trust policy checks that ID. The check blocks the confused deputy problem, where another customer tricks the vendor into using your role. LangChain's LangSmith BYOC module follows this pattern with an
sts:ExternalIdtrust condition. - Outbound connections: InfoQ's cloud-prem analysis notes the data plane often opens connections out to the control plane. As a result, customers don't need inbound firewall rules. Many vendors run a "phone home" pipeline that pushes versions, resource usage, and heartbeats.
- Vendor-pushed upgrades: Redpanda's control plane runs rolling upgrades with health checks. You can schedule a maintenance window. Redpanda coordinates major upgrades with you, but it sets a final date you can't negotiate.
- Billing: The cloud provider bills you for compute, storage, and egress. The vendor bills its software fee separately. ClickHouse states that AWS bills infrastructure directly to your account, independent of the subscription.
By clearly dividing operational responsibilities, BYOC allows enterprise buyers to balance cloud-native management efficiency with strict internal security and account-level compliance standards.
BYOC drawbacks and tradeoffs
BYOC trades vendor-side simplicity for account-side responsibility.
The costs fall into four areas:
- Customer-side operations: Aiven's BYOC docs say BYOC deployments "are not automated" and add complexity to key management and security. You still own the VPC, quotas, and audit logs.
- Vendor access to your account: A Zilliz-sponsored New Stack post says hosting data in your account does not guarantee security. Vendors still log in to troubleshoot. A Cloud Security Alliance (CSA) research note on Qubole shows the failure mode. The system "could not distinguish between the vendor and the attacker" once an adversary held valid vendor credentials. The Qubole case involved a vendor role outside any BYOC deployment.
- Split support and narrower SLAs: ClickHouse offers no formal uptime service level agreement (SLA) for BYOC. Redpanda, in contrast, lists a 99.99% uptime guarantee in its BYOC docs. Redpanda's BYOC service terms disclaim backup and disaster recovery.
- Slower rollouts: The InfoQ analysis notes that vendors coordinate BYOC updates per customer or run them off-hours. BYOC rollouts move faster than on-prem but slower than multi-tenant SaaS.
Egress fees are the clearest example of costs that move onto your bill. As of November 2026, AWS charges $0.09/GB for the first 10 TB from US East (Ohio), after 100 GB free. Azure's rate from North America is $0.087/GB on Microsoft's premium network, after 100 GB free.
Google Cloud Premium Tier charges $0.12/GiB from Iowa (us-central1) to North America after the first GiB. AWS cross-zone traffic adds $0.01/GB each direction.
Model egress and cross-zone traffic for your workload before comparing BYOC and SaaS quotes.
Questions to ask a BYOC vendor
Add these questions to your security questionnaire and request written answers:
- Required IAM permissions: Which roles and trust policies does the vendor need? Which actions carry account-wide scope?
- Data leaving the account: Which metrics, logs, and traces reach the vendor, and through which endpoint?
- Incident ownership: Who responds when your cloud provider, your network, or the vendor's software fails? Which causes does the SLA exclude?
- Upgrade cadence: How often do upgrades ship, can you defer them, and do releases list new permissions?
- SLA terms: What uptime does the contract commit to for BYOC, and are credits the sole remedy?
- Exit and portability: Does the contract define data format, retention, scope, and deletion at termination, per CSA control IPY-04?
Securing clear, written commitments across these key areas ensures your security and procurement teams can thoroughly audit vendor access before committing infrastructure resources.
How AI agent sandbox vendors handle BYOC
Teams shopping for a BYOC sandbox for AI agents ask whether E2B, Daytona, and others support it. Answers come from official docs and pricing pages, checked in November 2026:
| Vendor | BYOC offered | Model | Plan |
|---|---|---|---|
| E2B | Yes, on AWS, Google Cloud, and Azure | E2B provisions and monitors a cluster in your VPC. Anonymized CPU and memory metrics go to E2B Cloud | Enterprise only |
| Daytona | Yes, as bring your own compute | Custom regions run on your machines. Daytona keeps the control plane | Enterprise |
| Modal | Not documented | Managed, with region pinning and outbound allowlists | Not applicable |
| Vercel Sandbox | Not documented. BYOC covers Functions | Secure Compute attaches sandboxes to a dedicated network with VPC peering | Secure Compute is an Enterprise add-on |
| Cloudflare Sandbox | Not documented | Runs on Cloudflare, driven by Workers | Workers Paid |
E2B also offers Embed, the single-machine package of its Apache-2.0 runtime, which you operate yourself. Daytona's GitHub README says core development moved to a private codebase in June 2026.
"Not documented" means the option is unavailable until the vendor confirms it in writing. A vendor's BYOC can also cover a sibling product instead of its sandbox. Vercel's BYOC, for example, covers Functions.
How Baseten Sandboxes helps you with BYOC
Baseten Sandboxes offer two Custom plan options for teams with residency or network requirements:
- Bring Your Own Metal: The sandbox runtime runs on your bare metal. A managed control plane connects over a private isolated network. This option requires real bare metal and excludes virtualized servers.
- Private networking: The managed cloud interconnects with your VPC through private endpoints. Dedicated egress IPs are in private preview.
In both options, Baseten Sandboxes retain control plane access. Fully air-gapped and fully self-hosted deployments aren't available. Security comes from layered controls.
Each sandbox runs in a Firecracker microVM with its own kernel, which isolates it from neighboring sandboxes. Domain filtering limits which domains each sandbox can reach, and proxy-based secret injection keeps credentials out of agent code.
Both are in public preview. Compliance covers SOC 2 Type II, HIPAA, and ISO 27001. Managed regions run in the US and EU.
FAQs about BYOC
What is BYOC in AI?
In AI infrastructure, BYOC places an AI vendor's data plane in your cloud account under the vendor's control plane. LangChain sells LangSmith BYOC this way on AWS. E2B documents BYOC for sandboxes on AWS, Google Cloud, and Azure.
Who pays for infrastructure in a BYOC deployment?
You do. Your cloud provider bills compute, storage, and egress to your account. The vendor bills a separate software or management fee. Confirm whether your cloud spend counts toward committed discounts before modeling savings.
Is BYOC more secure than SaaS?
Not automatically. BYOC keeps data in an account you control, which simplifies residency and audit. BYOC also grants the vendor scoped access to that account. Confluent, which sells BYOC, says the model isn't inherently more secure. Security depends on IAM scope, telemetry flows, egress controls, and isolation inside each workload.
What is the difference between BYOB and BYOC?
BYOB usually means bring your own bucket. The vendor stores data in your object storage, but compute and queries run in the vendor's cloud. BYOC moves the vendor's compute into your account too. In telephony, BYOC means bring your own carrier, which concerns SIP trunks and phone service.
Related articles

Guides
What is a computer use agent? How AI agents automate GUI workflows
Learn how a computer use agent operates software through screenshots, clicks, and keystrokes.
13 min read

Guides
How gVisor vs Firecracker compare for sandboxing AI agent workloads
Compare gVisor vs Firecracker on isolation, startup, I/O overhead, KVM needs, and Kubernetes fit to choose the right sandbox runtime.
12 min read

Guides
A developer's guide to the OpenAI Agents SDK
Learn how to build with the OpenAI Agents SDK in Python, from tools, handoffs, guardrails, and sessions to tracing, costs, and sandboxed code execution.
10 min read