Can you run Vercel in your own cloud account?
Vercel announced a way to deploy inside a customer-owned AWS account on June 16, 2026. This article covers what that feature does, as documented at the time of writing, and what it means for teams evaluating BYOC options.
- You can run Vercel in your own cloud account through Vercel's Bring Your Own Cloud (BYOC) on AWS, announced on June 16, 2026. It is currently in Private Beta and scoped to AWS only.
- With BYOC on AWS, compute, build artifacts, and application data run inside the customer's own AWS account and VPC, while Vercel operates the control plane on top of it.
- BYOC on AWS is not available as a self-serve option on standard Vercel plans.
- Teams that need BYOC as a generally available option today, across more than one cloud provider, typically look at platforms like Northflank built around that model from the start.
If you need self-serve BYOC that isn't locked behind a sales call or a waitlist, Northflank has offered Bring Your Own Cloud since 2019, available self-serve across plans, spanning AWS, GCP, Azure, Oracle Cloud Infrastructure, and CoreWeave, plus on-premises and bare-metal via BYOK.
Northflank is SOC 2 Type II certified and HIPAA compliant, and supports Business Associate Agreements (BAAs) under an Enterprise contract for handling protected health information.
See Northflank's Bring Your Own Cloud, get started (self-serve), or book a demo if you'd like to talk through your specific cloud setup first.
Vercel's Bring Your Own Cloud (BYOC) on AWS runs compute, build artifacts, and application data inside the customer's own AWS account and VPC.
The control plane, meaning the dashboard, build orchestration, and deployment logic, continues to run on Vercel's infrastructure. Apps and agents deployed this way reach private backends and internal systems the same way any other workload in that AWS account does.
The feature is framed around compliance requirements that go beyond private deployments: workloads that need to run on infrastructure the customer's security team owns and audits directly, rather than infrastructure operated on the customer's behalf.
BYOC on AWS controls where compute runs. It does not change other parts of the underlying platform.
- Scoped to AWS: BYOC is built for AWS accounts. Vercel doesn't offer it for GCP, Azure, or other providers.
- Private Beta: BYOC on AWS is in Private Beta and is not available as a self-serve option on standard Vercel plans.
Teams comparing Vercel alternatives beyond BYOC can find a fuller breakdown in the Vercel alternatives guide, which covers Northflank, Netlify, AWS Amplify, Cloud Run, Heroku, and Render by workload support, database options, and infrastructure model.
Northflank's BYOC provisions and manages Kubernetes clusters inside a customer's own cloud account, across AWS (EKS), GCP (GKE), Azure (AKS), Oracle Cloud Infrastructure (OKE), and CoreWeave, with Civo also supported. Multiple cloud accounts can be connected at once for multi-cloud or hybrid architectures, and existing clusters can be imported through Bring Your Own Kubernetes (BYOK), including on-premises and bare-metal installations.
The control plane, meaning orchestration, scheduling, CI/CD pipelines, and the developer-facing UI and API, manages deployments. All workloads and data, including services, databases, jobs, and preview environments, run inside the customer's VPC. Northflank has no access to workload data or secrets.
Security controls include:
- Private VPC deployment, with no public internet exposure required for cluster operations
- Configurable security groups and network policies, with integration into existing VPNs, Direct Connect, or ExpressRoute
- Sandboxed runtimes using Kata Containers or gVisor for isolation beyond standard Kubernetes namespacing
- Customer-managed encryption keys through AWS KMS, Azure Key Vault, or Google Cloud KMS
Keeping the runtime environment and data plane inside the customer's cloud account supports compliance with GDPR, HIPAA, SOC 2, ISO 27001, PCI DSS, FedRAMP, and other regulatory frameworks. Northflank is SOC 2 Type II certified and HIPAA compliant, with Business Associate Agreements (BAAs) for handling protected health information available under an Enterprise contract.
Existing cloud credits, reserved instances, savings plans, and enterprise discounts, including AWS EDPs, GCP commits, or Azure reservations, apply the same way they would to any other workload in that account. Cloud costs appear directly in the customer's own billing console.
See Northflank's Bring Your Own Cloud, get started (self-serve), or book a demo if you'd like a walkthrough. Use the pricing calculator to estimate costs for your own cloud account, and check the BYOC documentation for setup requirements and cluster configuration steps.
Only if you have access to Vercel's BYOC on AWS Private Beta. Standard Vercel plans, including Pro and standard Enterprise, run on Vercel-managed infrastructure.
Vercel's June 2026 announcement scopes BYOC to AWS. It does not include GCP, Azure, or other cloud providers.
Yes. Northflank supports BYOC deployment across AWS, GCP, Azure, Oracle Cloud, CoreWeave, and Civo as a generally available, self-serve feature. The control plane manages orchestration and deployments, while workloads and data run inside the customer's cloud account.
- What is BYOC in cloud computing? covers the control plane and data plane split, and the compliance, residency, and cost scenarios where BYOC is worth the added operational overhead.
- Bring your own cloud (BYOC): the future of enterprise SaaS deployment looks at why enterprises are moving toward BYOC over vendor-hosted SaaS.
- Best options for BYOC in cloud computing compares BYOC platforms beyond Vercel and Northflank.
- Is BYOC the future of software deployment? and Bring your own cloud app hosting cover the broader shift toward customer-controlled infrastructure for application hosting.
