Short answer: the Netlify alternatives worth comparing differ mostly in how they handle the backend your site grew. For everything on one global network, look at Cloudflare. If the site has turned into a Next.js app, Vercel is the natural home. To keep the static site, an API, workers and Postgres in one dashboard, look at Render or DigitalOcean App Platform. Firebase App Hosting suits Next.js or Angular apps built on Firebase Auth and Firestore. Out Plane runs the API and workers in Germany next to managed PostgreSQL, and the static pages can stay where they are.
The story is a common one. A marketing or docs site starts on Netlify, then gains a signup form, user accounts, a headless CMS, a nightly import or a database. Netlify has added its own answers to that, so this guide starts with what it covers now. Then it compares six platforms for the grown-up site, and a split setup that moves only the backend. Out Plane is our product; it is one option here, and we say where the others fit better.
Before you move: what Netlify covers in November 2026
- Plans and credits. Free comes with 300 credits a month, Personal is $9 per month with 1,000 credits, and Pro is $20 per month with unlimited members and 3,000 credits. Enterprise is custom. A production deploy costs 15 credits, compute 10 credits per GB-hour, bandwidth 20 credits per GB and web requests 2 credits per 10,000.
- Running out. When a team's credits are used up, all of its projects pause and show a "Site not available" page. On paid plans, credit packs or auto recharge bring them back, and auto recharge is off by default.
- Functions. Synchronous functions stop at 60 seconds, scheduled functions at 30 seconds and background functions at 15 minutes. Buffered payloads are capped at 6 MB.
- Netlify Database. A managed Postgres built into the platform, on credit-based plans. Migrations live in your repository, and each deploy preview gets its own database branch with a copy of production data.
- Netlify Server. A long-lived Node.js server with WebSockets, in Early Access since November 10, 2026. It runs up to 3 instances (1 on Free and Personal), scales to zero when idle, and is free during Early Access, which Netlify scopes to evaluation, experimentation and low-volume production use. Next.js, Astro and Nuxt do not run on it yet.
If your new backend is a few form handlers and a small database, staying on Netlify may be the cheapest move. There are four common reasons to look further: a server that must hold connections in production today rather than in Early Access, jobs that run longer than 15 minutes, a backend written in Django, Laravel or Rails, which Netlify does not run as a server, or a shared credit pool where one busy project can pause every other one.
Netlify alternatives at a glance
| Option | Static site | Backend | Database | Starting price (Nov 2026) |
|---|---|---|---|---|
| Netlify (reference) | Included in every plan | Functions (60 s; background 15 min); Server in Early Access | Netlify Database (Postgres) | Free with 300 credits; Personal $9; Pro $20 with unlimited members |
| Cloudflare | Static asset requests free and unlimited | Workers; Containers on Workers Paid | D1 (SQLite); Hyperdrive to your own Postgres or MySQL | Free; Workers Paid from $5/month |
| Vercel | Hobby free for non-commercial use | Functions up to 800 s on Pro; containers and daemons in beta | Marketplace: Neon, Supabase, Upstash | Pro $20 per developer seat |
| Render | Free static sites on a CDN | Web services, background workers, cron jobs | Render Postgres from $6; Key Value from $10 | Hobby $0 plus compute; compute from $7/month |
| DigitalOcean App Platform | 3 static sites free, then $3/month each | Web services, workers and jobs | Dev Postgres $7/month | Containers from $5/month |
| Firebase App Hosting | Next.js and Angular apps on Cloud Run | Cloud Run on the Blaze plan | Firestore and other Firebase products | Pay as you go, with monthly no-cost amounts |
| Out Plane | Serve it from your app, or keep it on Netlify | Long-running containers; workers as apps with no ports | Managed PostgreSQL 14 to 18, $6 per database | Starter $9/month, 14 day free trial |
Facts checked on 11 November 2026 against each provider's own pages: Netlify pricing, credits, function limits, Database, Server and Server changelog; Cloudflare Workers pricing, limits, Pages, D1, Hyperdrive and Containers; Vercel pricing, function limits, Daemons and storage; Render pricing, free tier and regions; DigitalOcean App Platform pricing; Firebase App Hosting and costs; GitHub Pages limits. Prices change, so check before you decide.
1. Cloudflare
What it is. Cloudflare's developer platform, where Workers serve both your static files and your backend code from its global network. Pages still works, but Cloudflare now tells new projects to start with Workers, which it says covers most Pages use cases.
Pricing as of November 2026. The Free plan allows 100,000 requests a day with 10 ms of CPU per request. Workers Paid has a $5 monthly minimum that includes 10 million requests and 30 million CPU milliseconds. Requests to static assets are free and unlimited, and there is no charge for egress on Workers.
For a site that grew a backend.
- API routes run as Workers, with up to 5 minutes of CPU per request on Paid and 128 MB of memory per isolate.
- D1 is a serverless database with SQLite semantics. Its free allowance is 5 million rows read and 100,000 rows written a day, with 5 GB of storage.
- Hyperdrive connects Workers to a PostgreSQL or MySQL database you already run, on Free and Paid plans.
- Cron Triggers and queue consumers run for up to 15 minutes.
- Containers, on Workers Paid, can run a framework backend from any image. They start on demand from Worker code and their disk is ephemeral by default.
Choose it if most of the site is still static, visitors are worldwide, and the new backend is small enough to live in Workers.
Look elsewhere if the backend is a framework app that expects an ordinary server and Postgres. Containers can run it, but they start on demand and keep no disk.
2. Vercel
What it is. The company behind Next.js, with hosting built around it: Git deploys, preview deployments and functions, plus containers, background daemons and WebSockets, which are in beta.
Pricing as of November 2026. Hobby is free and limited to personal, non-commercial use. Pro is $20 per month per developer seat with $20 of usage credit, and includes 1 TB of data transfer, then from $0.15 per GB. Viewer seats are free.
For a site that grew a backend.
- Functions run for up to 300 seconds on Hobby and up to 800 seconds on Pro.
- Container functions scale to zero when idle. Daemons keep workers running, but during the beta they run only in production, take no inbound traffic and keep no persistent local storage.
- Postgres, Redis and other databases come from Marketplace providers such as Neon, Upstash and Supabase. Vercel Blob stores files.
Choose it if the site has become a Next.js app and its backend is API routes and server actions.
Look elsewhere if the site earns money and Hobby is no longer allowed, the team is large enough that per-seat pricing hurts, or the backend needs a server that stays up today. Our Vercel alternatives guide compares the options from that side.
3. Render
What it is. A managed platform where static sites, web services, background workers, cron jobs, Postgres and Key Value (Redis-compatible) sit in one workspace. Services run in Oregon, Ohio, Virginia, Frankfurt or Singapore, and static sites are served from a CDN.
Pricing as of November 2026. Static sites are free. Workspaces cost $0 on Hobby (1 seat, up to 25 services, 5 GB of bandwidth) and $25 per month on Pro (unlimited seats, 25 GB of bandwidth), plus compute from $7 per month. Postgres starts at $6 per month and Key Value at $10. Free web services sleep after 15 minutes without traffic and take about a minute to wake, and free Postgres expires after 30 days.
For a site that grew a backend. The static site, an API, a nightly cron job and Postgres fit in one workspace, with health checks, a pre-deploy command for migrations and instant rollbacks on every plan. Pro adds full-stack preview environments and autoscaling.
Choose it if you want Netlify-style static hosting and the new backend under one roof, with previews and rollbacks.
Look elsewhere if a free API that sleeps is not enough and $25 a month for the workspace plus compute is more than a small project needs. More detail in our Render alternatives guide.
4. DigitalOcean App Platform
What it is. DigitalOcean's managed platform for static sites, web services, workers and jobs.
Pricing as of November 2026. Three static-site apps are free, each with 1 GiB of transfer, and further static-only apps are $3 per month. The smallest container is $5 per month (shared, 1 vCPU, 512 MiB, 50 GiB of transfer). A dev Postgres database is $7 per month and can only be used by the app that owns it. Extra transfer is $0.02 per GiB.
For a site that grew a backend. The static site, an API and a worker can live in one app. Autoscaling is only available on dedicated instances, not on shared ones.
Choose it if your team already uses DigitalOcean and wants a low fixed price for a small API next to the site.
Look elsewhere if you need autoscaling on the smallest instances. More detail in our DigitalOcean App Platform alternatives guide.
5. Firebase App Hosting
What it is. Google's hosting for server-rendered web apps, with built-in support for Next.js and Angular. It deploys when you push to a GitHub branch and runs on Google Cloud: Cloud Run, Cloud Build, Artifact Registry, Secret Manager and Cloud Logging.
Pricing as of November 2026. It requires the pay-as-you-go Blaze plan. Each billing account gets monthly no-cost amounts, including 10 GiB of outgoing bandwidth, 2 million Cloud Run requests, 180,000 vCPU-seconds, 360,000 GiB-seconds of memory and 2,500 build-minutes. Bandwidth beyond that is $0.20 per GiB uncached and $0.15 per GiB cached.
For a site that grew a backend. It integrates with Firebase Authentication and Cloud Firestore, so a site that added sign-in and user data on Firebase gets its server code next to them. The App Hosting docs do not cover background workers.
Choose it if your app already uses Firebase Auth and Firestore and is built with Next.js or Angular.
Look elsewhere if you want a fixed monthly price instead of pay-as-you-go billing.
6. Out Plane
What it is. A managed platform where every app is a long-running container, deployed from a Git push (GitHub) or a Docker image, with managed PostgreSQL next to it. Apps run in Germany.
Pricing as of November 2026. Starter is $9 per month and Pro is $29 per month, both with a 14 day free trial. Growth is $299 per month, and Enterprise is custom. Compute is billed per minute, and managed PostgreSQL is $6 per database. There is no free plan. See pricing for details.
For a site that grew a backend.
- The API runs in any language that fits in a container, such as a Node.js, Django or Laravel app. It stays running, so there are no cold starts.
- A nightly import or queue consumer runs as an app with no ports (docs).
- Managed PostgreSQL 14 to 18 comes with automated backups, point-in-time recovery, read replicas and connection pooling, in 8 regions with Frankfurt as the default.
- A headless CMS such as Strapi, Directus or Ghost deploys as a one-click template. Redis, MySQL and MongoDB are templates too, and you operate them yourself.
- S3 compatible buckets hold uploads. Custom domains such as
api.example.comget automatic TLS, and IP allow lists are available. - Scale each app to 1, 5 or 10 instances depending on the plan.
- The static pages can stay on Netlify or Cloudflare, as in the split setup below.
Choose it if your visitors and data are mostly in Europe and the backend has outgrown functions: a framework API, a CMS and workers, with PostgreSQL managed for you.
Look elsewhere if you want the static site and the backend to share one preview per pull request: Render's full-stack preview environments on Pro cover that.
The split setup: keep the site on Netlify, move only the backend
You do not have to move everything at once. The static pages can stay on Netlify, with their CDN and deploy previews, while the backend moves to a platform that runs servers: Render, DigitalOcean App Platform or Out Plane. The site calls the API on its own subdomain, such as api.example.com.
A Netlify function usually becomes one route in a small server. This is the same signup handler, rewritten with Hono so that it runs as a long-lived process:
// server.ts
import { serve } from '@hono/node-server';
import { Hono } from 'hono';
import { cors } from 'hono/cors';
const app = new Hono();
// Only the Netlify site may call the API from a browser
app.use('/api/*', cors({ origin: 'https://www.example.com' }));
app.post('/api/subscribe', async (c) => {
const { email } = await c.req.json();
// Write to PostgreSQL with the connection string from DATABASE_URL
return c.json({ ok: true });
});
// Listen on all interfaces, not localhost, so the platform can reach the app
serve({ fetch: app.fetch, port: Number(process.env.PORT ?? 3000), hostname: '0.0.0.0' });The trade-offs are real. You now deploy two things, and a pull request preview on Netlify talks to the production API unless you run a second backend for previews. In return, the backend can hold connections, run jobs as long as they need and keep its database next to it, while the site keeps Netlify's workflow.
Which Netlify alternative should you choose?
- The site is still static: stay on Netlify, or move to Cloudflare, where static asset requests are free and unlimited. GitHub Pages works for docs and project sites (1 GB per site, 100 GB a month soft bandwidth), but its terms rule out running an online business on it.
- The site became a Next.js app: Vercel, or Netlify if per-seat pricing is the issue.
- Static site, API, cron jobs and Postgres in one dashboard: Render, or DigitalOcean App Platform if you already use DigitalOcean.
- Built on Firebase Auth and Firestore: Firebase App Hosting.
- A framework backend, a CMS and workers in Europe, with managed PostgreSQL: Out Plane, with the static site staying on Netlify or Cloudflare.
Frequently asked questions
Is Cloudflare Pages still a good Netlify alternative?
Pages still works, but Cloudflare now recommends Workers for new projects and says Workers supports most Pages use cases. If you are leaving Netlify today, start with Workers and its static assets.
Which Netlify alternatives have a free plan?
Cloudflare Workers (100,000 requests a day), Render (free static sites, plus web services that sleep and Postgres that expires after 30 days), DigitalOcean App Platform (three static sites) and Vercel Hobby for non-commercial use. Firebase App Hosting needs the Blaze plan but has monthly no-cost amounts. Out Plane has no free plan; Starter and Pro start with a 14 day free trial.
Can I keep my Netlify site and add a database somewhere else?
Yes. Keep the site on Netlify and connect it to an API that owns the database, as in the split setup above. Calling the database straight from the browser would expose its credentials, so the API in between matters.
Next steps
If Out Plane fits your backend, start a 14 day free trial on Starter or Pro and deploy the API from GitHub or a Docker image. For a Next.js frontend, see Vercel alternatives for full-stack apps and How to deploy a Next.js application, or browse every comparison on the alternatives page.



