Load balancing
for your custom domain
Point the same domain at multiple applications and Square Cloud's edge distributes the traffic with automatic failover. Included with custom domains, with no per-request billing.
- Round-robinEach request goes to the next application in the group, so the load is split evenly.
- Automatic failoverReplica 2 went down. Requests that would go to it are served by the other applications in the group.
- Back in rotationOnce Replica 2 responds again, it starts receiving requests again, with no action on your part.
Up to 10 applications per domain
How many applications can serve one domain depends on your plan. Load balancing comes with custom domains, starting on the Standard plan. Compare plans
Standard
Up to 2 applications per domain
Pro
Up to 5 applications per domain
Enterprise
Up to 10 applications per domain
High availability without a proxy to maintain
A load balancer on Square Cloud is simply the same custom domain on more than one application. The edge does the rest.
Round-robin at the edge
Each request can land on a different application in the group, spreading the load across your deployments with no proxy or extra layer to configure.
Automatic failover
If an application goes offline (connection refused), any request, including POST, is answered by another application in the group.
Updates without downtime
Restart or deploy one application at a time: while one comes back, the others keep serving.
US$ 0 per request
Load balancing is part of your plan: no per-request billing and no add-on to buy.
No req/s limit
The load balancer sets no requests-per-second ceiling, so traffic spikes are not throttled by it.
Self-service in the dashboard
Add the same custom domain to another application and the balancer exists. The Load Balancing page shows every group, its applications and your plan's limit.
Up and running in three steps
No dedicated infrastructure to provision: the balancer comes from your applications' network settings. New to custom domains? See how they work
- 1
Configure a custom domain
Set your domain on an application and create the DNS records shown in the dashboard. TLS certificates are automatic.
- 2
Add it to another application
Set the same domain on a second application, from the network settings or the Load Balancing page, up to your plan's limit.
- 3
The edge balances the traffic
Requests are distributed round-robin with automatic failover. Removing the domain from an application shrinks the group at any time.
A plan for every stage of your project
Start small and scale when you need to, with no loyalty contracts.
Standard
RecommendedFor production, with databases and custom domains
From R$44.99/mo ≈ $8.10
- 4 GB RAM
- 4 vCPU
- Up to 16 projects
- Scales up to 8 GB on the same plan
Pro
For high scale, with daily application snapshots and advanced analytics
From R$124.99/mo ≈ $22.50
- 12 GB RAM
- 6 vCPU
- Up to 48 projects
- Scales up to 24 GB on the same plan
Enterprise
For large operations, with a dedicated account manager
From R$299.90/mo ≈ $53.98
- 32 GB RAM
- 16 vCPU
- Up to 128 projects
- Scales up to 1024 GB on the same plan
Load balancing is available from the Standard plan.
Compare all plans4.9 out of 5 · 402 reviews on Google + TrustpilotTrustpilot
Load balancing FAQ
What is load balancing on Square Cloud?
It is one custom domain served by more than one of your applications. Square Cloud's edge sends the requests for that domain to those applications in round-robin and stops sending them to an application that goes offline. There is no separate balancer to create: setting the same domain on a second application turns it on.
Which plans include load balancing?
Every plan with custom domains: Standard balances up to 2 applications per domain, Pro up to 5 and Enterprise up to 10. The Hobby plan does not include custom domains.
Is there a charge per request?
No. Load balancing is included in your plan, with no per-request billing and no requests-per-second ceiling set by the balancer.
Are sessions sticky?
No. Traffic is distributed round-robin, without sticky sessions: each request can land on a different application. Applications that keep state in memory (local sessions, local cache) need shared state, such as a database or Redis.
What happens when an application goes down?
If an application is truly offline (connection refused), any request, including POST, fails over to another application in the group. In the rarer case where the cluster node answers a timeout page instead, only requests without a body (GET, HEAD) are resent; a POST receives an error and must be retried by the client. Once the application responds again, it returns to the rotation automatically.
Which applications can share a domain?
Any of your website applications. Every application in the group serves the same hostname, so they should serve the same site or service. Typically the same application deployed multiple times.
How do I remove an application from a balancer?
Remove the domain from it, in its network settings or on the Load Balancing page. The other applications keep serving the domain; removing it from the last one releases the domain.