High-Traffic Cloud Hosting

CloudPloy deploys your app to a server in your own AWS account, or to a fresh server you connect over SSH. How much traffic it handles depends on the server you pick and how well the app caches, not on a CloudPloy plan. Here is what you can do today, and what is coming.

What you can do today

Pick a bigger server

Choose the EC2 instance size when you create the server, and resize it later. Plans cap the size CloudPloy will manage: up to 16 vCPU / 16 GB on Starter, 32 vCPU / 64 GB on Pro, and uncapped on Scale. You pay AWS for the compute directly.

Run more replicas

On a paid plan you can run up to 10 replicas of an app on its server. Traefik spreads requests across them, which uses every CPU core and keeps the app up while one replica restarts.

Put Cloudflare in front

Connect your Cloudflare account and CloudPloy creates the DNS record for your custom domain, with the Cloudflare proxy on if you want it. Cloudflare's CDN then caches static assets and pages you mark cacheable, and absorbs DDoS traffic before it reaches your server.

Cache in the app

Most of the gain at high traffic comes from caching: full-page caching for public pages, Redis for sessions and object cache, and a database sized for the read load.