Vercel alternatives for Next.js: where they run, what they cost, what you give up.
Leaving Vercel means choosing between two ways of running Next.js. Render, Railway, Fly.io, DigitalOcean, a server of your own and Canner run it as a normal Node server, which Next.js documents as supporting every feature. Netlify, Cloudflare and AWS Amplify translate it to their own serverless platforms through an adapter, and each adapter has gaps. For Canada: Netlify, Amplify, Fly.io, DigitalOcean and Canner can run your app here; Render and Railway cannot.
Facts checked
Node server or adapter
A Node server is what you get with next build and next start, or the output: "standalone" build. The Next.js self-hosting guide says image optimization and proxy (formerly middleware) work with zero configuration this way, and ISR works on a single instance with persistent disk. The cost is that the server runs where you put it, in one region, and you handle caching across instances yourself if you run more than one.
An adapter rebuilds your app for a platform’s functions: server rendering goes to a serverless function, middleware to an edge function, images to the platform’s image service. You get scale-to-zero and, on Cloudflare, execution near every visitor. You also get whatever the adapter does not support yet, listed in the second table. What changes on any non-Vercel host, adapter or not, is covered in Deploy Next.js without Vercel.
Nine alternatives, side by side
Vercel is in the table for reference. Entry prices are the cheapest listed option that runs a server-rendered Next.js app. The US vendors print prices with a bare “$”; Cloudflare’s page says USD. Canner bills in Canadian dollars.
| Option | Canadian region | How it runs Next.js | Entry price | Pricing model |
|---|---|---|---|---|
| Canner | Montréal, the only region | next start as a long-running Node process; standalone builds also work | Starter free (apps sleep after 3 h idle); Live $9/mo or $99/yr | Flat per organization; Live keeps two projects always on and includes 1 TB of traffic a month (Starter 250 GB), no per-GB charge |
| Vercel † † | Montréal (yul1) as a Functions execution region since January 20, 2026 | Native | Hobby free, for personal, non-commercial use; Pro $20 per developer seat | Seat fee with $20 of included credit, then usage, uncapped |
| Netlify † † † | yul, listed as Canada (Central), selectable for Functions; the default is Ohio | OpenNext adapter: a serverless function for rendering, ISR and Server Actions, an Edge Function for middleware | Free (300 credits); Personal $9/mo; Pro $20/mo | Credits: 10 per GB-hour of compute, 20 per GB of bandwidth, 15 per production deploy |
| Cloudflare Workers † † † † | No region to pick; a request runs in the data centre closest to where it was received | OpenNext adapter (@opennextjs/cloudflare) on the Workers Node.js runtime; Cloudflare now recommends vinext, which is in beta | Free: 100,000 requests a day; Paid from $5/mo | Paid includes 10 million requests and 30 million CPU-ms, then $0.30 per million requests and $0.02 per million CPU-ms; no bandwidth charge |
| AWS Amplify Hosting † † † | Canada (Central), ca-central-1 | Amplify’s managed SSR compute, documented for Next.js 12 to 15 | Pay as you go; free tier for 12 months | $0.01 per build minute, $0.15/GB served, $0.30 per million SSR requests plus $0.20 per GB-hour |
| Render † † † † | None (Oregon, Ohio, Virginia, Frankfurt, Singapore) | Node web service: your build command, then yarn start | Free instance, spins down after 15 min idle; $7/mo for 512 MB | Fixed per instance; Hobby workspace $0, Pro $25/mo; Hobby includes 5 GB of bandwidth, then $0.15/GB |
| Railway † † † | None (California, Virginia, Amsterdam, Singapore) | output: "standalone" run with node .next/standalone/server.js, or your Dockerfile | Hobby $5/mo, includes $5 of usage | Per second: about $10 per GB of RAM and $20 per vCPU a month; egress $0.05/GB |
| Fly.io † † † | Toronto (yyz) | A Docker image from fly launch; standalone recommended, run with node server.js | $3.69/mo for 512 MB at the Ashburn rate; prices vary by region | Usage, no platform fee; $0.02/GB outbound in North America |
| DigitalOcean App Platform † † † † | Toronto (TOR) | Node.js buildpack: runs your build script, the app listens on PORT | $5/mo, 512 MiB, 50 GiB of transfer | Fixed per container; shared plans run one container, no autoscaling; $0.02/GiB over the allowance |
Self-hosted (next start, Coolify) † † | Wherever you rent the server | next start or standalone on your own server | Coolify self-hosted is free; Coolify Cloud $5/mo for two servers | You pay for the server, and run it |
† Competitor details come from each vendor’s own published pages on the dates shown; prices and plans change, so check the vendor before you decide. Vercel (2026-11-10) · Vercel (2026-11-10) · Netlify (2026-11-10) · Netlify (2026-11-10) · Netlify (2026-11-10) · Cloudflare Workers (2026-11-10) · Cloudflare Workers (2026-11-10) · Cloudflare Workers (2026-11-10) · Cloudflare Workers (2026-11-10) · AWS Amplify Hosting (2026-11-10) · AWS Amplify Hosting (2026-11-10) · AWS Amplify Hosting (2026-11-10) · Render (2026-11-10) · Render (2026-11-10) · Render (2026-11-10) · Render (2026-11-10) · Railway (2026-11-10) · Railway (2026-11-10) · Railway (2026-11-10) · Fly.io (2026-11-10) · Fly.io (2026-11-10) · Fly.io (2026-11-10) · DigitalOcean App Platform (2026-11-10) · DigitalOcean App Platform (2026-11-10) · DigitalOcean App Platform (2026-11-10) · DigitalOcean App Platform (2026-11-10) · Self-hosted (`next start`, Coolify) (2026-11-10) · Self-hosted (`next start`, Coolify) (2026-11-10)
Which Vercel features you keep
The first three columns are Next.js features; previews are a platform feature. For the Node-server hosts, the ISR, image and proxy cells are what Next.js documents for next start, since those hosts run it as is.
| Option | ISR and revalidation | Image optimization | Middleware or proxy | Pull request previews |
|---|---|---|---|---|
| Canner | Works; one process per project, cache on local disk | Runs in the app; .next/cache is kept between builds, runtime-optimized images are regenerated after each deploy | Runs in the same process, in Montréal | One per pull request |
| Netlify † † | Supported, time-based and on-demand | Through Netlify Image CDN | Runs as an Edge Function; headers and redirects are evaluated after middleware; Node middleware has no filesystem or C++ add-ons | A Deploy Preview per pull request |
| Cloudflare (OpenNext) † † † | Supported | Supported, through Cloudflare Images, set up separately | Middleware supported; Node.js middleware (Next.js 15.2+) not yet, and Next.js 16’s proxy.ts defaults to the Node.js runtime | Version URLs, and Previews for branch or pull request testing |
| AWS Amplify † † | Time-based only; on-demand ISR is not supported | Supported; each optimized image is capped at 4.3 MB | Supported, but not on static assets or optimized images; edge API routes, streaming and unstable_after are not supported | Web previews per pull request; restricted for SSR apps in public repositories |
| Render † † † | As next start on each instance | As next start | As next start | Single-service previews on Hobby; full-stack previews on Pro |
| Railway † † † | As next start on each instance | As next start | As next start | PR environments, turned on in project settings |
| Fly.io † † | As next start on each Machine | As next start; install sharp if <Image> fails | As next start | Not covered in the Next.js guide |
| DigitalOcean App Platform † † | As next start | As next start | As next start | Not covered in the Next.js guide |
| Self-hosted † † | Works on one instance with persistent disk; several need a shared cache handler | Zero configuration under next start | Zero configuration under next start | Coolify: per pull request; a bare server: you build it |
† Competitor details come from each vendor’s own published pages on the dates shown; prices and plans change, so check the vendor before you decide. Netlify (2026-11-10) · Netlify (2026-11-10) · Cloudflare (OpenNext) (2026-11-10) · Cloudflare (OpenNext) (2026-11-10) · Cloudflare (OpenNext) (2026-11-10) · AWS Amplify (2026-11-10) · AWS Amplify (2026-11-10) · Render (2026-11-10) · Render (2026-11-10) · Render (2026-11-10) · Railway (2026-11-10) · Railway (2026-11-10) · Railway (2026-11-10) · Fly.io (2026-11-10) · Fly.io (2026-11-10) · DigitalOcean App Platform (2026-11-10) · DigitalOcean App Platform (2026-11-10) · Self-hosted (2026-11-10) · Self-hosted (2026-11-10)
Canadian region, Canadian owner
A Canadian region keeps execution in Canada. It does not change who runs the platform. Every hosted option above except Canner is a US company, and a US provider can be ordered under the CLOUD Act to hand over data it controls, wherever that data sits. Vercel itself now has a Montréal region, so if the region is your only requirement you may not need to move at all; Canner vs Vercel covers that case.
Under Quebec’s Law 25, sending personal information outside Quebec, Toronto included, calls for a privacy assessment first (section 17). Fly.io and DigitalOcean run in Toronto. Netlify’s and Amplify’s regions are listed only as Canada (Central). Canner runs in Montréal. Our Law 25 guide explains the assessment.
When each one is the better pick
- Stay on Vercel if you need a global edge, Fluid compute or Skew Protection, and a US provider is acceptable. The Montréal region covers execution in Canada.
- Netlify for the closest serverless equivalent, with ISR, images and previews handled by its adapter and a Canada (Central) functions region.
- Cloudflare Workers if your users are spread out and you want rendering near each of them, and you can live with the adapter’s gaps and no fixed region.
- AWS Amplify if the rest of your stack is on AWS in
ca-central-1and you don’t use on-demand ISR or streaming. - Fly.io or DigitalOcean App Platform for a Node server in Toronto. See Canner vs Fly.io and Canner vs DigitalOcean.
- Render or Railway for a Node server with previews, if US or EU hosting is fine. See Render alternatives and Railway alternatives.
- Self-hosted, with or without Coolify, if you want full control and will patch, back up and monitor the server yourself.
- Canner for a Canadian-owned, managed Node host in Montréal with Postgres, preview deploys and a flat price. Background jobs go in a separate Worker project. Plans are on the pricing page.
Questions
What is the best Vercel alternative for Next.js?
It depends on whether you want a Node server or a serverless adapter. Hosts that run next start (Render, Railway, Fly.io, DigitalOcean, Canner, your own server) support every Next.js feature on one instance. Netlify, Cloudflare and Amplify scale to zero and run closer to visitors, with gaps listed by each adapter.
Is there an open-source alternative to Vercel?
Coolify is open-source and free to self-host on your own server, with preview deployments for pull requests. OpenNext is the open-source adapter Netlify and Cloudflare use. And next start itself runs on any Node host.
Which Vercel alternatives have a Canadian region?
Canner (Montréal), Netlify (yul, Canada (Central)), AWS Amplify (ca-central-1), Fly.io (Toronto) and DigitalOcean App Platform (Toronto). Render and Railway have none. Cloudflare runs Workers wherever the request lands, with no region to choose. Vercel has its own Montréal region, yul1.
Does ISR work off Vercel?
Yes on a single next start instance with persistent disk; with several instances you need a shared cache handler. Netlify and Cloudflare’s adapter support it. Amplify supports time-based ISR but not on-demand revalidation.
Try your Next.js app in Montréal, for free.
Starter costs nothing and includes a Postgres database. Move to Live when you need a custom domain or an app that never sleeps.