Vercel is the default deploy target for JavaScript frameworks. It’s where Next.js lives, and the ecosystem pushes you there by default.
But Astro isn’t Next.js. Astro was built to ship zero JavaScript. It renders HTML at build time, strips out client-side bundles, and produces static files by default. Vercel’s entire platform is optimized for the opposite – serverless React with edge functions and ISR.
That’s a mismatch. Here are 5 hosting options that make more sense for Astro projects.
Why Not Vercel for Astro?
Vercel works with Astro. Nobody is saying it doesn’t. But there are tradeoffs worth thinking about:
Adapter lock-in. To deploy SSR on Vercel, you need @astrojs/vercel. That adapter compiles your routes into serverless functions. Move to a different host later? You’re swapping adapters and retesting everything.
Cold starts for content pages. If you’re using Astro SSR for a blog or docs site, Vercel runs each page render as a serverless function. Functions that haven’t been called recently need to cold-start. For a content site that should just serve HTML, that’s unnecessary overhead.
Static hosting is free elsewhere. Vercel’s static hosting is solid, but you can get the same thing (unlimited bandwidth, global CDN) on Cloudflare Pages for free. No card required.
Pricing for content sites. Vercel’s Pro plan is $20/user/month. That makes sense for a SaaS with a team of five shipping a Next.js app. For a personal blog or documentation site built with Astro, it’s hard to justify.
Astro doesn’t need serverless. The framework was designed to ship minimal JS. The standard @astrojs/node adapter runs on any Node.js server. You don’t need Vercel’s serverless infrastructure to serve mostly-static pages.
1. Cloudflare Pages – Best Free Option for Static Astro
If your Astro site is fully static (no SSR), Cloudflare Pages is the best free option, period.
What you get: Unlimited bandwidth, unlimited requests, global CDN, automatic HTTPS. Connect your GitHub repo and every push triggers a build. Preview deployments for pull requests. Custom domains with free SSL.
For SSR: Cloudflare Workers support is available via @astrojs/cloudflare, but it comes with limitations. Workers have a different runtime than Node.js – some npm packages won’t work. The execution model has CPU time limits. It’s improving fast, but it’s not a drop-in Node.js replacement.
Best for: Static Astro sites where you want zero hosting costs. Documentation sites, blogs, marketing pages, portfolios. If your astro.config.mjs uses output: 'static' (the default), Cloudflare Pages handles it perfectly.
Price: Free for most use cases. Workers Paid plan ($5/mo) if you need SSR.
2. InstaPods – Best for SSR Without Complexity
InstaPods gives you a real Linux server with the standard @astrojs/node adapter. No serverless functions, no cold starts, no platform-specific adapters.
What you get: Run instapods deploy my-site and it detects your Astro project, sets up the server, installs dependencies, and gives you a live URL. Full SSH access if you need to debug anything. Git deploy from GitHub for push-to-deploy workflows.
For SSR: The @astrojs/node adapter runs your Astro site as a standard Node.js process. No vendor lock-in – the same adapter works on any Node.js host. Your site stays warm, no cold starts.
For static: Works equally well. Build locally or on the server, nginx serves the output. Same one-command deploy.
Best for: Developers who want SSR without the serverless complexity. Side projects and client sites where $3/mo flat pricing beats usage-based billing. Read our full Astro hosting comparison for a deeper breakdown.
Price: $3/mo flat. No bandwidth charges, no usage surprises.
3. Netlify – Good Middle Ground
Netlify sits between Cloudflare’s free tier and Vercel’s enterprise focus. Good developer workflow, reasonable free tier, solid build pipeline.
What you get: Git-connected deploys, branch previews, form handling, split testing. The build system handles Astro well. Custom domains, automatic HTTPS, CDN distribution.
For SSR: Netlify Functions (via @astrojs/netlify) compile routes into serverless functions – similar to Vercel. Same cold start concerns apply, though Netlify’s function runtime has gotten faster.
For static: Strong. The free tier gives you 100GB bandwidth/month and 300 build minutes. That’s enough for most content sites.
Best for: Teams already using Netlify for other projects. Static Astro sites that might add light SSR later. Developers who want more features than Cloudflare (forms, identity) without Vercel’s pricing.
Price: Free tier for static. Pro at $19/mo for teams.
4. Railway – Dev-Friendly SSR
Railway runs your Astro SSR app as a real Node.js process, not serverless functions. That means no cold starts and no adapter lock-in beyond @astrojs/node.
What you get: Connect a GitHub repo, Railway auto-detects Node.js, installs dependencies, and deploys. Clean dashboard with real-time logs and resource monitoring. Preview environments for PRs.
For SSR: Real runtime, always warm. Railway uses Nixpacks for auto-detection, so you don’t need a Dockerfile. The @astrojs/node adapter works out of the box.
The catch: Usage-based pricing. The $5/mo Hobby plan includes $5 of compute credits. A small Astro SSR app running 24/7 costs roughly $3-8/mo in compute on top of that. If traffic spikes, your bill spikes. There’s no ceiling.
Best for: Developers who want a real Node.js runtime with a modern dashboard and don’t mind watching usage costs.
Price: $5/mo + usage. Typical Astro SSR app: $8-13/mo total.
5. Self-Hosted VPS – Full Control, Cheapest at Scale
A $4/mo Hetzner VPS or $6/mo DigitalOcean Droplet gives you complete control. Install Node.js, run your Astro build, point nginx at the output. Done.
What you get: Full root access. Install anything. Run multiple sites on one server. No platform limits, no adapter lock-in, no usage billing. The @astrojs/node adapter for SSR or just serve static files with nginx.
The catch: You’re managing everything. Nginx config, SSL certificates (Let’s Encrypt), process managers (PM2 or systemd), firewall rules, OS updates, domain setup. Every time you add a new site, you’re writing another nginx server block, generating another SSL cert, configuring another systemd service. For a single Astro site, that’s a lot of overhead. At our agency, we’ve done this enough times to have it scripted, but it’s not beginner-friendly.
Best for: Developers comfortable with Linux who want the absolute cheapest hosting at scale. Running 5+ Astro sites on one $4/mo VPS beats paying per-site on any platform.
Price: $4-6/mo for the server. Free everything else (your time excluded).
Quick Comparison
| Platform | Static | SSR | Starting Price | Astro Adapter | Cold Starts |
|---|---|---|---|---|---|
| Cloudflare Pages | Excellent | Limited (Workers) | Free | @astrojs/cloudflare | Yes (Workers) |
| InstaPods | Yes | Yes (Node.js) | $3/mo flat | @astrojs/node | No |
| Netlify | Excellent | Serverless | Free / $19 Pro | @astrojs/netlify | Yes |
| Railway | Yes | Yes (Node.js) | $5/mo + usage | @astrojs/node | No |
| VPS (Hetzner/DO) | Yes | Yes (Node.js) | $4-6/mo | @astrojs/node | No |
| Vercel | Yes | Serverless | Free / $20 Pro | @astrojs/vercel | Yes |
Bottom Line
For static Astro sites, Cloudflare Pages is the easy answer. Free, fast, unlimited bandwidth. Hard to beat.
For SSR, it depends on your budget and how much you want to manage. InstaPods gives you a real Node.js runtime at $3/mo flat with no cold starts and one-command deployment. Railway is solid if you don’t mind usage-based billing. A self-hosted VPS is cheapest at scale but requires the most setup.
For a deeper dive into all the tradeoffs, check out our full Astro hosting comparison.
The one thing all five alternatives share: they don’t force you into a platform-specific adapter that ties your Astro project to a single vendor. That portability matters more than most developers realize – until the day they need to migrate and discover their entire build pipeline is coupled to one platform’s proprietary runtime.