Cloudflare vs Vercel vs VPS for an Astro Website

Astro is the framework. Where it runs is a separate decision, and the right answer depends on the project, not on a favourite. This guide compares three common choices so you can see what each asks of you.

Platform features, limits and prices change often. Treat this as a way to think, and check each provider’s current documentation and pricing before you commit. Names are used as examples; there is no partnership implied.

Start from the workload

Before comparing platforms, answer these:

1. Is the site mostly static pages, or does it need server code for forms, accounts or live data?
2. Where are your visitors, and does data have to stay in a particular region?
3. Who will deploy and look after it day to day?
4. What happens to your traffic costs if the site is busy for a week?
5. Which services (database, email, storage, analytics) must it connect to?

How the three compare

	Cloudflare	Vercel	Managed VPS
Suits	Mostly static or edge-friendly sites with a global audience	Teams that rely on its Git-based previews, integrations and team accounts	Projects needing server control, custom services or a specific data location
Server code	Supported through its adapter and edge runtime, with runtime differences to plan for	Supported through its adapter and serverless functions	Full control: a Node server or anything you can run
Upkeep	Little server to look after	Little server to look after	You or a provider handle patching, backups and monitoring
Cost shape	Plan limits, plus any added Workers or storage features	Usage-based pricing that follows traffic and features	Predictable monthly server cost, plus the time to run it
Main risk	Runtime differences from standard Node when you use server features	Cost growth with usage; coupling to its workflow	Security and uptime become your responsibility

When Cloudflare is a good fit

• The site is mostly static, with a few server routes.
• You want global delivery with little to manage.
• You already use Cloudflare for DNS, and want fewer vendors.

Check before launch: which Workers, database or storage features you use, and the limits and prices of your plan.

When Vercel is a good fit

• Your team already works in Vercel, with preview deployments for every change.
• You depend on its integrations or team permissions.
• The site uses server-rendered routes and you want a smooth deployment path.

Check before launch: expected traffic against usage-based pricing, and what features you rely on that are specific to the platform.

When a managed VPS is a good fit

• You need to run services that managed platforms do not support.
• Data has to sit in a particular country or data centre.
• You want a predictable monthly cost and are willing to take on, or pay for, the work.

Check before launch: who patches the server, who owns backups, who is alerted at 3 a.m., and what is written down. With a VPS, those answers must be explicit. Our maintenance and support service can take some of that on if scoped.

Common mistakes

• Choosing the platform before knowing whether the site needs server code.
• Picking the cheapest plan and discovering a limit after launch.
• Putting secrets in the repository instead of the platform.
• No preview environment, so changes are tested in production.
• No rollback plan.

What to set up on any platform

Whatever you choose, aim for the same basics: a domain and DNS you control, https, separate preview and production environments, secrets stored on the platform, uptime alerts, and a written way back to the last working version.

Getting a recommendation

If you are not sure, describe your site and your constraints. We will recommend a platform, explain the reasons and the expected cost, and configure it in accounts you own. See deployment and infrastructure.