Skip to main content
All articles

10 Best Vercel Alternatives for 2026 (Free + Paid)

HostingVercelNetlifyRenderRailwayFly.ioStatic SitesComparison

The Deploy button on Vercel asked me to connect a GitHub organization to publish a 12 KB HTML file. One file. A bit of CSS, two SVGs. That was the moment I closed the tab and started writing this. If you're looking for a Vercel alternative because the workflow stopped fitting the work, you're not alone.

Vercel is the best place to ship Next.js. That's not the question. The question is what you do when your site has zero functions, no build pipeline, and no reason to live next to a Git repo. Or the opposite - you do have a backend, and Vercel's function meter is eating your margin.

TL;DR - the short answer

Ten Vercel alternatives I actually recommend in 2026, sorted by how much workflow tax they ask you to pay:

  • Hostsmith - drag-and-drop, no build, no CLI, no GitHub account required. Zero workflow tax.
  • Cloudflare Pages - unlimited bandwidth on the free tier, hard to beat if you're fine with Git or Wrangler.
  • Netlify - Vercel's twin in features and pricing. Switching here mostly buys you a different bill.
  • Render - good when you'll eventually need a small backend.
  • Railway - full-stack starter with predictable usage billing. The platform people pick when they leave Vercel for an actual app.
  • Fly.io - global edge for things that aren't just static. Micro-VMs, real regions, real latency.
  • GitHub Pages - free, Jekyll-shaped, fine for docs and personal sites.
  • AWS Amplify - the right call if you're already deep in AWS.
  • DigitalOcean App Platform - predictable monthly pricing, no surprise meter.
  • Coolify - self-hosted. Own the box, own the bill.

The Vercel-specific pain that pushes people to look around isn't really about money. It's about a static site being treated like a full-stack platform problem, or a full-stack app being metered into a panic attack. You shouldn't need a CI pipeline to publish a resume. You also shouldn't need a finance meeting to ship a side project.

Vercel alternatives at a glance

PlatformFree tier (real numbers)Workflow taxCustom domain on free?Best for
Hostsmith1 site, 5k visits/mo, 5 GB BW, 5 MB storageNone (drag-drop)No (subdomain only)Drag-and-drop static, AI-builder output
Cloudflare PagesUnlimited bandwidth, 500 builds/moLow (Git or CLI)Yes, up to 100Static at scale, devs OK with Git
Netlify300 credits/mo (~15 GB bandwidth)Low (Git or CLI)YesVercel-style workflow, smaller traffic
RenderFree static tierMedium (Git + config)YesStatic now, backend later
Railway$5 trial credit, then usage-billedMedium (Git + Dockerfile-ish)YesFull-stack apps with Postgres
Fly.ioPay-as-you-go, small free allowanceMedium-High (CLI, regions)YesEdge apps, global latency
GitHub PagesFree, soft 100 GB limitLow-Medium (Jekyll or Actions)YesDocs, personal Jekyll sites
AWS Amplify12-month free tier, then meteredHigh (AWS console)YesTeams already in AWS
DigitalOcean App Platform3 free static sitesMedium (Git + spec file)YesPredictable monthly bills
CoolifyFree software, you pay the VPSHigh (self-host)YesOne box, many services

Workflow tax is the column most listicles skip. It's also the one that decides whether you finish the migration.

Why teams leave Vercel

Most Vercel migrations trace back to one of four issues: function-shaped pricing on non-function sites, mandatory Git integration, bandwidth math at scale, and a Hobby tier that excludes client work. Vercel itself documents some of the pricing friction on their own pricing page, with features like spend caps, recursion protection, and Attack Challenge Mode. The fact that those features exist tells you something.

Now the friction points in detail.

The Hobby tier is personal use only. That's in the terms. Plenty of indie devs technically violate this without realizing it. Any client work, any monetized side project, any portfolio that promotes paid services is supposed to be on Pro. So your $0/month plan has a license question mark hanging over it.

Function-shaped pricing for not-function-shaped sites. Hobby includes 1 million Vercel Functions invocations and 4 hours of Active CPU per month. Pro starts at $20/month and ships with a $20 included usage credit. Overage after that is $0.60 per million invocations. If your site has zero serverless functions, you're paying nothing for those. But you're on a billing model that exists to meter them. Mental tax.

Bandwidth math gets weird at scale. Hobby has a Fast Data Transfer cap of 100 GB/month. Pro lifts that to 1 TB. Past 1 TB on Pro, you're paying $0.15 per GB. Reasonable for an app. For a static portfolio that briefly hits the front page of Hacker News, it's the kind of bill that makes the news.

Builds run on metered machines on paid plans. Standard build machines on Pro cost $0.014 per minute. Not a lot per build. But not a lot compounds.

Mandatory Git integration. You connect a GitHub, GitLab, or Bitbucket repo, or you use the Vercel CLI. There is no drag-and-drop in the Vercel dashboard for plain HTML. If your designer hands you a folder, your only options are "set up Git" or "set up the CLI." Which, again - for one HTML file?

Password protection is a paid-tier feature. Vercel's Deployment Protection (the password / SSO gate on a preview URL) is bundled into paid plans, not the Hobby tier. If your only reason to upgrade is to gate a client preview, the Vercel password protection alternatives page walks through cheaper paths, and the broader password protect a website guide covers the same problem from the host-agnostic side.

None of this is Vercel being evil. It's Vercel optimizing for a different customer than someone shipping a static page - or someone shipping a Postgres-backed side project that just happens to have a marketing page bolted on.

When you should stay with Vercel

Vercel is the right answer when:

  • You're shipping a Next.js app and using ISR, RSC streaming, or middleware. Vercel ships Next.js features first; it's the reference host.
  • You actually use Edge Functions in production. The DX is genuinely good.
  • Your team is already on Vercel and the switching cost outweighs the bill.
  • You need preview deployments tied to PR comments and your reviewers depend on them.
  • You're on Pro and your bill is predictable. A predictable $20-$50/month for a working production app is a fine deal.

If none of those apply, the rest of this Vercel alternatives list is for you.

How to choose a Vercel alternative

Every "best Vercel alternative" post I've read just lists logos. The actual choice depends on five questions. I'd answer these first, then look at the list.

  • What's the workload shape? Pure static (HTML, CSS, a Vite dist/), full-stack (an app with a database), edge-flavored (you actually need multi-region latency), or self-hosted (you own a VPS and want a control plane). The right Vercel alternative depends entirely on which of those you are.
  • Drag-and-drop or Git-first? If your "build" is a designer Slacking you a zip, Git-first hosts add real friction. If you live in a terminal, drag-and-drop feels weird. Pick the workflow you already have.
  • What does the free tier actually let you do? Not the marketing copy. The real numbers: bandwidth in GB, visitors per month, custom-domain support, surprise-bill protection. I rewrote a draft of this article after a free tier I'd called "generous" silently moved to credits.
  • Lock-in. Can you take your config to another host in an afternoon? Vercel and AWS Amplify both have config files that don't translate cleanly. Plain HTML on Hostsmith or static files on Cloudflare Pages move in five minutes.
  • EU data residency. If your client is in the EU or you sell to EU customers, you want files that physically sit in the EU. Some hosts have "EU edge" but not EU residency. Different thing.

If you answer those five, the choice usually narrows to two or three platforms before you even open the listicle.

The 10 best Vercel alternatives in 2026

The first four picks are best for static or static-leaning sites. The middle three are for full-stack work. The last three are for AWS-heavy teams, predictable billing, and self-hosters respectively. Pick the lane first, then the host.

1. Hostsmith - the drag-and-drop one (zero workflow tax)

Hostsmith is what I reach for when somebody DMs me a zip file at 11pm and wants a live URL by midnight. If you came here because Vercel asked you to connect a GitHub org for a 12 KB HTML file, this is the inverse of that experience.

You drag the folder into the dashboard. You get back a URL. There is no build step, no vercel.json, no GitHub connection. It hosts plain HTML, single-page apps, PDFs, images, zips - anything static. If you want Vercel-style hosting without GitHub, this is the shortest path. You can host a static site without a build pipeline on Hostsmith or Neocities.

The free tier is honest about its numbers. You get 1 site, 5,000 visits per month, 5 GB bandwidth, 5 MB storage, and a region-prefixed subdomain (your-site.us.hostsmith.link or your-site.eu.hostsmith.link depending on residency). No custom domain on free. Starter covers 10k visits, 10 GB, 50 MB storage, and Private Sites (password or email whitelist) - so you don't bounce to a higher tier just for gating client previews. Pro covers 5 sites, 100k visits, and custom domains on top.

Where this wins over Vercel for me:

  • No function-invocation meter to read - there are no functions to invoke.
  • No vercel.json, no framework preset to argue with.
  • If your build already produced a dist/, Hostsmith starts where Vercel's build would end.
  • AI-builder output ships as-is. If you exported a site from Lovable, Bolt, or v0, or downloaded a Claude artifact as HTML, you can drop it in and get a public URL. No build config to convince.
  • US and EU partitions for data residency if that matters for a client.

Where it doesn't fit: if you need serverless functions, an SSR Next.js app, or a build pipeline that runs on every Git push, Hostsmith isn't trying to be that. It is deliberately static-only.

See more on drag-and-drop website hosting and hosting a single HTML file online.

2. Cloudflare Pages - the bandwidth king (low workflow tax)

Cloudflare Pages is the answer if you want a free tier that genuinely doesn't get in your way at scale and you're OK with a Git or Wrangler workflow.

Free tier numbers: unlimited bandwidth and unlimited static requests, 500 builds per month, 1 concurrent build, up to 100 custom domains per project. That bandwidth number is real, not asterisked.

The constraint is the workflow. Pages wants a Git connection or the Wrangler CLI. There's no drag-and-drop in the dashboard for casual use. If you live in a terminal, this is a non-issue. If you're a designer or marketer who just wants a URL, you'll feel it.

Pick Cloudflare Pages if: you're comfortable with Git, your site might go viral, and you want zero bandwidth anxiety.

3. Netlify - Vercel's twin (low workflow tax)

If you like Vercel's mental model but want a different vendor, Netlify is the closest match. Same Git-first workflow, same preview deploys, similar branded subdomains.

The free tier moved to Netlify's 2025 unified credit system. You get 300 credits per month. Bandwidth burns 20 credits per GB. Compute burns 10 credits per GB-hour. Web requests burn 2 credits per 10,000 requests. Production deploys cost 15 credits each.

Quick math: 300 credits / 20 credits per GB = 15 GB of monthly bandwidth before you hit the wall on a pure-static deploy. That's lower than Vercel's 100 GB Hobby cap. And that 15 GB is before deploys and compute eat into the same bucket - a few production deploys a week (15 credits each) meaningfully shrink the bandwidth you actually get.

The good news: the free plan has hard limits. You will not get a surprise bill. Hit the cap and the project pauses until next month or you upgrade. The bad news: 15 GB is not a lot if you have any decent traffic, and "credits" is a confusing unit to budget against. Netlify Pro is $19/member/month, which adds up fast for small teams.

If you're looking for a free Netlify alternative because 300 credits doesn't cover your traffic, Cloudflare Pages is the natural step.

Netlify Drop, their drag-and-drop product, is also worth knowing about if you only need it once in a while - though it has its own quirks. I've written about Netlify Drop alternatives separately if you want the comparison.

Pick Netlify if: you want a one-for-one Vercel swap and you trust the credit math for your traffic.

4. Render - the "I might need a backend" pick (medium workflow tax)

Render is the platform I'd suggest if you're hosting a static site today but you suspect you'll need a real backend within six months.

Static sites on Render are free. Their docs cover the specific limits at render.com. The moment you need a backend, you spin up a Web Service. Paid web services start around $7/month for the smallest instance, with most production setups landing closer to $19/month.

What Render gets right is the gradient. You start with a free static deploy that looks like Vercel's, then add a Postgres database, then add a background worker, all in the same dashboard with the same auth and the same billing. No second account, no second mental model. Render's free Postgres expires after 30 days, so plan around that.

What Render gets less right is build time on the free tier. Cold builds are slow. If you're iterating fast, that pause between push and live URL becomes a thing you notice.

Don't bother with Render if you're absolutely sure your site is and will always be static - the other picks here are simpler and cheaper for that.

5. Railway - the full-stack starter (medium workflow tax)

Railway is the Vercel alternative I'd pick if I were starting a new full-stack side project today. Not a marketing page with one form. An actual app, with a database, with background jobs.

The mental model: you connect a repo, Railway figures out how to build it (Nixpacks under the hood, or a Dockerfile if you've got one), and bills you for usage. Predictable in the sense that you can see the meter; less predictable than a flat monthly bill. They give you a small one-time trial credit to get going (check the current amount on their pricing page; the number has moved). Real production is usually $5-$20/month for a small app plus a Postgres.

What I like:

  • Postgres, Redis, MySQL spin up as templated services. No third-party signup.
  • The dashboard treats your front-end and back-end as the same project. None of the "front-end on Vercel, back-end on Render, database on Supabase" credential sprawl.
  • Logs and metrics that don't feel like an afterthought.

What I don't:

  • Usage billing is real billing. If you forget about a service, you pay for it. Set spend caps.
  • Edge it isn't. Your services live in a region. Pick the right one.

Railway is the wrong tool if your site is 12 KB of HTML. It's the right tool when "your site" is really "your app" and Vercel's function meter is starting to make your stomach hurt.

6. Fly.io - the global edge pick (medium-high workflow tax)

Fly.io is for apps that need to actually be close to users, not just say they are. Their thing is micro-VMs (Firecracker under the hood) that you can deploy to specific regions - Sydney, Frankfurt, São Paulo, the lot. You write a fly.toml, run fly deploy, and your app shows up in the region you asked for.

Pricing is pay-as-you-go on machines and bandwidth, with a small free allowance. A 256 MB shared-CPU machine running 24/7 lands around $3-$5/month, plus bandwidth. Their bandwidth pricing has tiers by region, which is honest but also a thing to read.

Where Fly wins over Vercel: real regions, real latency control, real control over how your app runs. You're not handing your code to a function abstraction. You're running a tiny VM.

Where it loses: workflow tax. You're writing a Dockerfile or letting Fly auto-detect, configuring health checks, picking regions, watching machine logs. If you wanted to skip all that, Hostsmith or Cloudflare Pages are sitting right there. Fly is for when you specifically need what Fly gives you.

7. GitHub Pages - the free forever one (low-medium workflow tax)

GitHub Pages is the classic. Free, public-facing, tied to a repo. It's been there for a decade.

It is also the most opinionated host on this list. The path of least resistance is Jekyll, which is fine for docs and blogs and awkward for single-page apps with client-side routing. You can fight it - publish a dist/ from a workflow, configure 404.html for SPA fallback - but you're fighting it.

GitHub Pages is the right answer for: open-source project docs, personal sites you'll never iterate on, simple Jekyll blogs, and class projects. It is the wrong answer for: anything where the publishing UX matters more than the price.

Quick note on the indie web. Neocities and Nekoweb live in the same "personal site, no build step" lane and have real free tiers and real character. Right answer for the page you make about your cat, wrong answer for client work. If you outgrew Neocities but want that vibe with a custom domain, Hostsmith covers it without GitHub in the loop.

I have a longer take on GitHub Pages alternatives if you've decided it's not for you.

8. AWS Amplify - if you're already in AWS (high workflow tax)

AWS Amplify is the Vercel alternative for teams that already have an AWS account, IAM, and a CloudFront story. If you're not one of those teams, you're going to feel every minute of the setup.

The pitch: Git-connected static and SSR hosting on top of CloudFront, with optional Lambda backends, optional Cognito auth, optional DynamoDB. The 12-month AWS Free Tier covers a lot, and after that pricing is metered like the rest of AWS - bandwidth, build minutes, requests, with each line item competitively priced and the bill harder to predict.

What you get: real AWS infrastructure, IAM you already trust, integration with everything else in your account.

What you pay: AWS console UX, slow first deploy, and a config story (amplify.yml) that locks you into AWS-shaped builds. Migrating off Amplify is harder than migrating off most platforms on this list.

Pick Amplify if your team is already in AWS and the answer to "where does this live?" is non-negotiable. Skip it if you're choosing freely.

9. DigitalOcean App Platform - the predictable bill (medium workflow tax)

DO App Platform is the Vercel alternative for people who liked the heroku-era flat monthly bill and want it back. App instances start at $5/month for a basic container, with managed databases extra. Bandwidth is included with your app instance up to a generous cap. The whole pricing page fits on one screen. Their static site tier has shifted over time, so double-check the current offer on their pricing page before you plan around it.

What it gets right: predictability. You know what next month's bill is. No usage meter to refresh anxiously. The Git-based deploy flow is straightforward, no surprises.

What it gets less right: feature ceiling. No global edge, no advanced traffic routing, no fancy preview environments. If you wanted those, you wouldn't be looking here.

Pick DO App Platform if you want a Vercel alternative whose bill you can explain to a non-technical partner in one sentence.

10. Coolify - own the box, own the bill (high workflow tax)

A note on self-hosting before the platform.

Self-hosting makes sense when you're already paying for a VPS for other reasons, when you have specific data-residency requirements no managed host meets, or when you're hosting more than a handful of small services and the per-platform free tiers don't add up to the convenience tax.

It does not make sense when you have one static site. It's the wrong tool for that, no matter how much fun the setup looks. The labor cost dwarfs the hosting cost.

With that out of the way: Coolify is a self-hosted PaaS that puts a Heroku-shaped dashboard on top of your own VPS. Connect a repo, give it a Dockerfile (or let Nixpacks figure it out), and you get auto-deploys, SSL, preview environments, database services - the works. The software is free. Your hosting bill is whatever Hetzner or Vultr or DO charges for the underlying box.

Realistic budget: $5-$10/month for the box, an afternoon to set it up, plus an hour or two a month thereafter for OS patches and Coolify updates - and whatever the box does at 2am the night something goes wrong.

What's good: total control. No usage meter. Host as many sites and services as the VPS can carry. No vendor can deprecate your stack.

What's not: you are now sysadmin. When the box runs out of disk at 2am, that's you. Coolify's a Vercel alternative for people who genuinely want to own the operating layer, not for people who think they want to.

Vercel alternatives by use case

Skim the list above by what you're actually shipping.

For a static site, plain HTML or a Vite dist/. Hostsmith if you don't want to touch Git. Cloudflare Pages if you do and you want unlimited bandwidth. GitHub Pages if it's a docs site or a personal page tied to a repo you already have.

For an AI-builder export. Hostsmith. Lovable, Bolt, v0, and Claude artifacts all produce static output that drops in without a build config. The Lovable deploy guide walks the specific flow.

For a client preview you need to gate. Hostsmith's Private Sites (password or email whitelist), available from the Starter plan up - pair with a custom domain on Pro. The password protect a website pillar covers the host-agnostic options.

For a full-stack app with a database. Railway for the smoothest dashboard. Render if you want to start static and grow into the backend. Fly.io if you genuinely need multi-region.

For an EU-resident site. Hostsmith EU partition for static. Fly.io with EU regions for apps. AWS Amplify in eu-central-1 if you're already there.

For "I own a VPS already." Coolify. Anything else is wasted spend.

For "we're already in AWS." Amplify. Don't fight your org chart.

Pricing reality check

Let's run real math across the use cases, not just static.

Scenario A: 50 MB static portfolio, 10,000 visitors/month, ~20 GB bandwidth. Classic portfolio site numbers.

  • Vercel Hobby: $0/month. Comfortably under 100 GB Fast Data Transfer. But you're technically violating the personal-use clause if this portfolio promotes paid services.
  • Vercel Pro: $20/month minimum. Includes 1 TB, so 20 GB is nothing. You're paying for headroom you don't use.
  • Netlify Free: 20 GB bandwidth = 400 credits. You're 100 credits over the 300 free limit, so the site pauses partway through the month or you upgrade.
  • Cloudflare Pages: $0/month. Unlimited bandwidth is unlimited.
  • GitHub Pages: $0/month, inside the soft 100 GB advisory limit.
  • Hostsmith: Starter at a few dollars/month covers 10k visits and 10 GB; Pro covers it comfortably with custom domain.
  • DigitalOcean App Platform: depends on the current static tier (see their pricing page) plus any add-ons; typically a few dollars a month at this scale.

Winner: Cloudflare Pages and Hostsmith. Vercel Pro works, just expensive for the workload.

Scenario B: small full-stack app, Postgres + Node API, ~500 daily users, modest bandwidth.

  • Vercel Pro + a third-party Postgres: $20/month Vercel + ~$10-$25/month Postgres elsewhere = ~$30-$45/month, with function invocation overage as a wild card.
  • Railway: ~$5-$15/month all-in for the app + Postgres, billed by usage.
  • Render: $7/month web service + $7/month Postgres after the free 30 days = ~$14/month.
  • Fly.io: ~$5-$10/month for two small machines + Postgres, region of your choice.
  • DO App Platform: $5/month app + $15/month managed Postgres = ~$20/month, flat.

Winner: Railway or Fly for usage-billed flexibility, DO for a flat bill you can predict.

Scenario C: globally-distributed app, real users in EU + US + APAC.

  • Vercel Pro: works, but you're paying for an Edge feature set whether you use it or not.
  • Fly.io: machines in 3 regions, ~$15-$30/month all-in for small apps.
  • AWS Amplify: technically works via CloudFront, but the latency story is less direct than Fly.
  • Cloudflare Pages + Workers: free tier covers a lot if your "app" is mostly static + lightweight edge functions.

Winner: Fly.io if it's a real app. Cloudflare if it's static with sprinkles.

The point of running three scenarios: the right Vercel alternative depends on what you're shipping. The platform tax that's reasonable for a Postgres-backed app is unreasonable for a portfolio, and vice versa.

FAQ

What is the best Vercel alternative? For a static site with no build step: Hostsmith. For a static site with Git: Cloudflare Pages. For a full-stack app: Railway. The "best" Vercel alternative is the one that matches your workload shape, not the one with the most features.

What is the best free Vercel alternative? For a Git-driven workflow with unlimited bandwidth: Cloudflare Pages. For a no-Git, drag-and-drop workflow: Hostsmith. Both have real free tiers with no surprise overages.

What's the best Vercel alternative for full-stack apps? Railway, with Render as a close second. Both bundle the app, the database, and the dashboard, and both bill on patterns that scale gently. Fly.io if you specifically need multi-region. Vercel itself if you're shipping Next.js and using its framework-specific features in earnest.

What's the best self-hosted Vercel alternative? Coolify on a $5-$10/month VPS. You get auto-deploys, SSL, and a dashboard close in feel to Vercel's, in exchange for being your own sysadmin. Dokploy and CapRover are honorable mentions in the same lane.

Vercel vs Netlify - which is cheaper? Not meaningfully. Netlify Pro is $19/member/month and Vercel Pro starts at $20/month, both with similar usage-based metering above that. If money is the issue, Cloudflare Pages or Hostsmith are bigger wins than swapping Vercel for Netlify.

What's the best Vercel competitor in 2026? Depends on the lane. For static: Cloudflare Pages on workflow and Hostsmith on simplicity. For full-stack: Railway. For self-hosters: Coolify. For AWS shops: Amplify. There isn't a single "best Vercel competitor" - there's a best one for each kind of project.

What's a good free Netlify alternative? Cloudflare Pages if you want a Git workflow with unlimited bandwidth. Hostsmith if you want drag-and-drop without Git. Both avoid Netlify's 300-credit ceiling and neither has a surprise-bill model.

What's the best Neocities alternative with a custom domain? Hostsmith. Pro plan supports up to 5 custom domains on static-only hosting with no build step required, which is the closest match for someone who liked Neocities' simplicity but outgrew the no-custom-domain limit.

How do I host a static site without GitHub? Hostsmith and Neocities both let you upload files directly through a dashboard - no repo, no CLI. If you want a Vercel alternative specifically without GitHub, Hostsmith is the closest match in workflow. Vercel, Netlify, Cloudflare Pages, and Render all expect Git or a CLI tool.

Why is Vercel so expensive at scale? Vercel meters function invocations, Active CPU, Fast Data Transfer, and build minutes separately. For a static site with no functions, you're still on a billing model designed for full-stack apps. Past 1 TB on Pro, bandwidth is $0.15/GB. Function overage is $0.60 per million invocations. None of these are unreasonable individually - they just compound for traffic-heavy or function-heavy sites.

What's the simplest way to host an HTML file online? Drag it into Hostsmith and copy the URL. Done. I wrote a longer guide on hosting an HTML file online with screenshots if you want the step-by-step.

Are there EU-hosted Vercel alternatives? Yes. Cloudflare has EU points of presence by default. Hostsmith has explicit EU partitions you can pick at upload time, so the files actually sit in the EU. Fly.io lets you pick EU regions for app workloads. Netlify and Vercel have EU edge but data residency guarantees usually require a paid plan.


Most people on Vercel today don't need Vercel. They need a host that matches the shape of the work. For one HTML file, the right answer was always going to be a host, not a platform. For a Postgres-backed app, the right answer is a platform that doesn't pretend the database is somebody else's problem.

Pick the workflow tax you're actually willing to pay. The Vercel alternatives list above sorts itself out from there.

If you're comparing hosts across adjacent categories, the Webflow hosting alternatives and Google Drive website hosting alternatives posts cover related decisions. If you're escaping Replit specifically, see Replit alternatives.