It arrives at your own edge
A dedicated edge zone with a rule builder: custom rules to challenge, block or allow by path, IP, country or header, and per-path cache rules. Traffic views show the top IPs and paths.
LaravelCloud
With PlanetScale
A product story
The same Cloud.
A building of its own.
Laravel Private Cloud runs your applications in a dedicated Kubernetes cluster, inside a dedicated AWS account and VPC that Laravel provisions and manages on your behalf, with no other tenant. The dashboard, the deploys and the framework integration are the ones you already know.
Walk the floors
The idea in one line Same dashboard, same deploys. Nobody else in the building.
One tenantLaravel Private Cloud
Address: static outbound IPs, yours alone
05Edge zone · custom rules, cache rulesDedicated
04Cluster · three nodes across AZsDedicated
03Data · RDS MySQL or Postgres, ElastiCacheInside
02Network · NAT gateways, private links outPrivate
01Account · dedicated AWS account and VPC, run by LaravelSingle tenant
Ground floor: Laravel operates the building. Your team ships the product.
Includes: Laravel Cloud Enterprise, the Advanced support plan
Custom quote
When it is the right choice
Five reasons
to move in.
If none of these describe your team, shared Cloud is the better answer, and cheaper. If one of them is a hard requirement, Private Cloud is how Laravel meets it without your team building the perimeter.
Regulated data
Health records, medical intake forms, government work. The question an auditor asks is whose infrastructure sits inside the scope. On Private Cloud the answer is only yours.
- Shared Cloud
- SOC 2 Type 2, ISO 27001; tenant isolation in the cluster
- Private Cloud
- Dedicated account, VPC, cluster and nodes; HIPAA with a signed BAA; PCI-DSS readiness and custom compliance auditing
- Still yours
- Encrypting PHI at the model, gates and policies, an application audit log
Monitor 552; Private Cloud FAQ (BAA, PCI-DSS readiness)
Private systems
Your application needs an internal API, a vendor database or a service in another AWS account, and that traffic must not cross the public internet.
- Shared Cloud
- Connects over the public internet, behind TLS
- Private Cloud
- VPC Peering (self-service) and Transit Gateway to your existing AWS; the docs add PrivateLink and VPC Lattice, set up with the Cloud team
- Ask yourself
- Do our CIDR ranges overlap with anything we want to peer with
A known address
A bank, a payment provider or a government API will only accept calls from IP addresses you register in advance. A building of your own has its own front door.
- Shared Cloud
- Outbound traffic shares platform addresses
- Private Cloud
- Dedicated NAT gateways with static outbound IPs
- Worth knowing
- NAT gateway traffic is billed in both directions; IPv6 routes without it
Predictable performance
Dedicated nodes mean no noisy neighbours. Three always-on nodes across availability zones give automatic failover. Scheduled autoscaling raises the floor before a known peak.
- Shared Cloud
- Autoscaling replicas; scheduled autoscaling on Business and Enterprise
- Private Cloud
- Dedicated compute nodes, three across AZs, plus the same scheduling
- Ask yourself
- Is our latency problem the platform, or the database
Monitor 497 (29 January 2026), 586 (scheduled autoscaling, 25 March 2026)
The size of the bill
Private Cloud starts at a platform fee of approximately $2,500 a month, plus the cost of your minimum compute and managed database, and is priced by custom quote. The docs add that it is typically cost-effective for workloads spending $2,000 or more a month on infrastructure.
- Pricing
- Platform fee of about $2,500 a month plus compute and database; custom quote after an architecture consultation
- On the bill
- Data Transfer, VPC, ELB, NAT Gateway and CDN appear as AWS line items
- Ask yourself
- What does finance need to see to sign it off
Private Cloud FAQ (platform fee, read 8 October 2026); Private Cloud docs (cost-effective threshold); Monitor 586 (AWS cost line items)
Use cases are Laravel's own list from the Private Cloud docs: security and compliance, private system access, performance-sensitive workloads, enterprise architecture, dedicated IP requirements.
Inside the building
One request,
floor by floor.
Floor 05
It lands on your own nodes
A private Kubernetes cluster with dedicated compute nodes, three always on across availability zones. Internal networking lets your apps call one another without leaving the cluster.
It reads from data in the same building
RDS MySQL 8.4 or Postgres 18 inside the dedicated VPC: Multi-AZ, up to 15 read replicas, point-in-time recovery. ElastiCache in Valkey or Redis OSS, up to multi-AZ with automatic failover. Laravel MySQL and Serverless Postgres remain available, but outside the VPC.
It calls out from a known address
A partner API sees your static outbound IPs. Calls into your existing AWS accounts go over VPC Peering or Transit Gateway, and IAM roles in those accounts replace static access keys.
It shows up on the bill as itself
Data Transfer, VPC, ELB, NAT Gateway and CDN costs appear as AWS line items rather than a single figure, so procurement can audit what the building costs to run.
Sources: Private Cloud, edge network, RDS, ElastiCache and private networking docs and the Private Cloud FAQ, read 8 October 2026; Monitor 494 (RDS replicas, Postgres and MySQL, 2 March 2026), 479 (ElastiCache, 10 June 2026), 586 (AWS line items, 25 March 2026).
Who chose it, and why
Four tenants.
Four reasons.
Each team below runs on Private Cloud, and each had a different reason for wanting the building. The figures are the customers' own, from their published stories.
Trybe
3separate Private Clouds: staging, playground, production- Regulated medical data kept off shared infrastructure
- A 1.6 TB MongoDB Atlas database left in place over VPC peering
GovAI
2production regions, US and Canada, in separate single-tenant AWS accounts- Compliance settled the decision, the story says
- Cost per 1,000 messages from about $22 to $16
Shoptimised
42%lower infrastructure cost- Microservices that need private connections
- Deploys from over an hour to one or two minutes
Superscript
30%infrastructure saving in the first month; 50% expected- Needed ISO 27001, SOC 2 and private networking
- Five apps moved; the 80 GB database took about six hours
“The ability to have the private networking aspect could have become a deal breaker.”Colin Bradford, COO, Superscript · Monitor 998
Shared Cloud for most.
A building when you need one.
Three questions before the consultation: which of your data would an auditor want walled off; which systems must your application reach without touching the public internet; and who outside your team needs to know your IP address in advance.