A FIELD GUIDE TO LARAVEL · VOLUME II · THE ECOSYSTEM
ENTRY II.44 · DEDICATED INFRASTRUCTURE
Private Cloud
Product · first recorded 29 January 2026, on Laravel Cloud
Laravel Cloud with nobody else in it: a dedicated Kubernetes cluster, VPC and AWS account for one customer, managed by Laravel and deployed to from the same Cloud dashboard. A platform fee from about $2,500 a month plus resources; HIPAA with a signed BAA.
Specification
Kind Product. An isolated Laravel Cloud, operated by Laravel
Engine Private Kubernetes cluster, dedicated nodes, dedicated AWS account and VPC
Runs on AWS. Three always-on nodes across availability zones, automatic failover
Installed by contact sales → consultation → custom quote → provisioning
Voice none. The Cloud dashboard, API and CLI
Scales by Cloud autoscaling on dedicated nodes; optional RDS and ElastiCache
Range Cloud: this is Cloud, isolated: same deploy flow, a dedicated account
Forge, VPS: n/a: the self-managed alternative, not a host
Vapor: n/a: a different product; nothing is shared
Neighbours
Laravel Cloud is the same platform on shared infrastructure, with the same dashboard and deploy flow. Vapor also runs in an AWS account, but the customer's own, and is closed to new sign-ups. Private Cloud's distinction: a dedicated AWS account and cluster that Laravel operates for one customer.
Laravel Cloud II.38Vapor II.19
Field marks
Private network card on the canvas
dedicated egress IPs from onboarding
IAM role per environment
cloud@laravel.com for a BAA
Fig. II.44.1 · One tenant, nobody else
Parts
1 Cloud dashboard. The same console, API and CLI as shared Cloud. Your apps deploy from here into an environment that is only yours.
2 Edge. A dedicated edge zone with its own rules and cache rules; a managed WAF and DDoS layer through Cloudflare.
3 Cluster. A private Kubernetes cluster on dedicated nodes, three across availability zones, failing over on their own.
4 Private networking. VPC peering, PrivateLink, VPC Lattice or Transit Gateway to the AWS resources in your own accounts.
5 Static egress. Dedicated NAT gateways with fixed outbound IPs, so a bank or a partner API can allow-list you by address.
6 Managed data. Optional RDS databases and ElastiCache caches provisioned inside the same private environment.
Hidden joinery
Docs give a typical lead time of four to six weeks, the FAQ as fast as two; provisioning needs your AWS account IDs and VPC CIDR ranges up front. IAM roles give an environment expiring credentials for a role in your account, not static keys. A BAA is offered on Enterprise and Private Cloud only, before any PHI is deployed.
Every claim checked against the Private Cloud docs, FAQ, changelog and Monitor 497, 552 on 2026-10-08.
TITLE
Private Cloud · one tenant only
SOURCES
laravel.com/cloud/docs/private-cloud · laravel.com/cloud/private-cloud · laravel.com/cloud/docs/private-cloud/edge-network · laravel.com/cloud/docs/private-cloud/private-networking · laravel.com/cloud/docs/private-cloud/iam-roles · laravel.com/cloud/docs/private-cloud/rds · laravel.com/cloud/docs/private-cloud/elasticache · laravel.com/cloud/docs/private-cloud/build-configuration · laravel.com/cloud/docs/compliance · laravel.com/cloud/docs/changelog · Monitor 497, 552, 556, 604
STATUS
Verified · 2026-10-08
SHEET
II.44 of 48
REV
A · 2026-10-08
DRAWN
BS
FINISH
All faces, including the back