Vercel alternatives in 2026: why teams move to Cloudflare and Supabase

If you want what Vercel does (serverless functions, a global CDN, git-push deploys and first-class Next.js) without Vercel's bill or limits, the closest alternative in 2026 is Cloudflare Workers, with Supabase when you need Postgres. Workers give you the same serverless, global model, billed on CPU time with no charge for egress, in an account you own. Supabase gives you the Postgres, auth and storage that Vercel now resells through its Marketplace. Other alternatives are better fits for other shapes of app: Netlify if you want a hosted platform much like Vercel, Render or Railway for long-running containers, Coolify or Dokploy if you want to run your own servers.

This post goes through the options, then looks at the Cloudflare and Supabase pair in detail: why teams choose it, how the bills compare, and what you give up.

Why do teams look for a Vercel alternative?

Vercel is a good product, and for a small project inside its included usage it is hard to beat. Teams start looking when one of these happens:

• A limit they cannot raise. Every build stops at 45 minutes on every plan. Hobby is for non-commercial personal use only, and a Hobby project that uses up its allowance is paused until its 30-day window resets.
• A bill that grows with traffic. On Pro, data transfer, CDN requests, function compute, image transformations and build minutes are each billed once the $20 monthly credit is used. Bots and crawlers count too.
• Seats. Each person who deploys is a $20 seat.
• Ownership. The app, its data and its secrets live in Vercel's account. Some teams want them in their own.

We go through each limit, and what to do about it on Vercel, in Hit a Vercel limit?.

What are the main Vercel alternatives?

The alternatives fall into four groups. Which one fits depends less on features than on the shape of your app.

If your app is a Next.js, Astro, Nuxt or SvelteKit site with API routes, which describes most apps on Vercel, a serverless platform keeps the model you already have. That narrows it to Netlify, Cloudflare Workers and AWS. Of those, Workers is the one that is global by default, bills CPU time rather than wall-clock time, and charges nothing for egress.

Why Cloudflare Workers?

• Global by default. A Worker runs in every Cloudflare location, close to each visitor. Vercel Functions run in one region unless you configure more.
• You pay for CPU, not waiting. Workers bill CPU time. A request that spends two seconds waiting on a database or an AI model and 20 ms computing is billed for the 20 ms. On the paid plan a request can use up to five minutes of CPU.
• No egress charges. Cloudflare does not charge for data transfer from Workers, and requests to static assets are free and unlimited. R2, its object storage, has no egress fees either.
• A small fixed price. Workers Paid is a $5 monthly minimum per account, including 10 million requests and 30 million CPU-milliseconds, with no seats.
• The pieces Vercel resells. R2 for files, Workers KV for key-value data, D1 for SQLite, Durable Objects for coordination, Cron Triggers, Queues, and Cloudflare Images.
• Framework support. Astro, Nuxt, SvelteKit and React Router have official Cloudflare adapters. Next.js runs through OpenNext, or vinext, Cloudflare's Vite-based Next.js, which it recommends for new apps and which is in beta.

Why add Supabase?

Workers do not include Postgres, and many Vercel apps need it. Supabase is the natural pair:

• Postgres, plus the things around it. Auth, file storage, realtime and row-level security, in one project.
• It works well from Workers. Cloudflare's Hyperdrive pools connections to Supabase and caches reads, so a Worker can use pg, Drizzle or Prisma without opening a new connection across the world on every request. supabase-js works over HTTPS for the rest.
• The same database Vercel offers. Supabase is one of the Postgres providers in Vercel's Marketplace, so moving to it directly cuts out a middle layer rather than changing databases.
• Clear pricing. The Free plan has a 500 MB database and pauses after a week without activity. Pro starts at $25 a month, with $10 of compute credit and 8 GB of disk.

If your app needs no Postgres, D1, KV and R2 cover most other storage, and you can stay on Cloudflare alone.

How do the bills compare?

There is no honest single number: it depends on your traffic, your functions and your team. What you can compare is what each line of the bill costs. These are list prices as published in November 2026, at their cheapest region where prices vary.

Sources: Vercel pricing, Vercel Pro plan, Vercel Functions pricing, Workers pricing, Cloudflare Images pricing, Supabase pricing, GitHub Actions billing.

How to read it:

• Bandwidth-heavy apps (media, downloads, big static sites) usually save the most, because that line drops to zero.
• Apps whose functions mostly wait on databases or AI models save on compute, because Workers bill the CPU, not the wait.
• Teams with several deployers save the seats.
• Small apps inside Vercel's included usage save little or nothing: $20 a month on Vercel against $5 to $30 on Cloudflare and Supabase. Move for ownership or limits, not for the bill.

To estimate your own, take a month of Vercel usage from your dashboard and price each line in the right-hand column.

What do you give up?

Moving is a trade. The main things Vercel does that you will have to replace or live without:

• Preview deployments per branch. Vercel gives every branch its own URL. On Workers you can upload a version and get a preview URL, or use Cloudflare's Workers Builds, but it is something you set up rather than a default.
• Zero-configuration Next.js. Vercel builds Next.js itself. On Workers, Next.js goes through an adapter, some features need a cache configured (ISR needs R2, on-demand revalidation a Durable Object), and Workers have limits of their own, such as 128 MB of memory per isolate.
• One dashboard. Analytics, logs, speed insights and billing in one place. On your own accounts, Cloudflare, Supabase and GitHub each have their own.
• The glue. Vercel's pipeline, from a push to a production deploy with the right variables, is something you now own: environments, provisioning, secrets, migrations and checks. That is the subject of Build your own Vercel on your own cloud.

Where does Orunbase fit?

Orunbase is the glue for the Cloudflare and Supabase pair, run on your own accounts. You connect Cloudflare (and Supabase) to a workspace, start from one of the Vercel templates already ported to Cloudflare or bring your own app, and get a repository with the app, its Terraform and its pipeline. CI in your own GitHub Actions checks every pull request, deploys stage on merge, smoke-tests it and then deploys prod. Cloudflare and Supabase bill you directly; Orunbase's Free plan covers up to three repositories.

See how it works, or go straight to the migration guide.

In short

• For a serverless web app, the closest Vercel alternative is Cloudflare Workers, with Supabase for Postgres: global, billed on CPU time, no egress charges, in accounts you own.
• Netlify is the like-for-like hosted option; Render, Railway and Fly.io suit long-running containers; Coolify and Dokploy suit teams that want their own servers.
• Compare line by line: bandwidth, waiting functions and seats are where Cloudflare saves; a small app inside Vercel's included usage saves little.
• You give up per-branch previews by default, zero-config Next.js and a single dashboard, and you take on the pipeline. That last part is what Orunbase is for.