Velox DataEngineering & human things
English
Menu

Zeabur Alternatives Compared: Choose by Service Type, and Stop Putting Everything on One Platform

The easiest destination for static sites, backend APIs, databases and self-hosted tools such as n8n. We only list conditions we verified, such as Vercel's free plan being non-commercial and Cloudflare now recommending Workers for new projects.

Elian Lu · Velox Data ·

Key points

  • Static sites → Cloudflare; backends → Cloud Run; PostgreSQL → a managed service; n8n and similar → a VPS + Docker Compose.
  • Vercel's free Hobby plan is for personal, non-commercial use only.
  • Cloudflare's official docs recommend Workers for new projects.
  • Keep DNS and backups somewhere other than your host, so you can move next time.
How was this verified? (3 tested, 1 from official docs)
Tested ourselves
  • Cloud Run source deploys (deployed for real; see the Cloud Run post)
  • n8n on a VPS with Docker Compose + Caddy (tested locally; see the n8n post)
  • Vercel Hobby being non-commercial, Cloudflare recommending Workers for new projects, and Pages build settings: checked against official docs (2026-10-17)
Written from official docs, not run ourselves
  • Railway, Render, Neon, Supabase, Coolify and Dokploy: we did not sign up and test them this time, only describe what they are; prices and free tiers change often, so check their sites
Contents (3 sections)
  1. Everything in one table
  2. Cloudflare build settings for frontends
  3. The lesson from this

Everything in one table

Your serviceSuggested destinationWhyWatch out for
Static sites, React/Vue/Vite frontendsCloudflare (Pages or Workers)Deploys automatically from GitHub; a great fit for static sitesCloudflare’s docs now recommend Workers for new projects
Next.js (with server-side rendering)VercelMade by the company behind Next.js, with the most complete supportThe free Hobby plan is personal, non-commercial use only; company sites need a paid plan
Backend APIs, chatbotsGoogle Cloud RunDeploys without a Dockerfile, regions across Asia, no compute charge when idleThe filesystem is temporary. Tested guide
The experience closest to ZeaburRailway, RenderConnect GitHub and spin up a database in a few clicksStill a single platform; back up your data yourself
PostgreSQLManaged services such as Neon or SupabaseNo maintenance on your sideAdd --no-owner --no-acl when restoring. Database post
Self-hosted tools such as n8n or DifyVPS + Docker ComposeOne small VPS runs several tools at a fixed priceBackups are on you. n8n, tested
A GUI on your own VPSCoolify, DokploySelf-hosted deployment platforms that feel similar to ZeaburYou maintain and update the platform itself too

Cloudflare build settings for frontends

Cloudflare Pages’ official framework presets:

FrameworkBuild commandOutput directory
React (Vite)npm run builddist
Vuenpm run builddist
Astronpm run builddist
Next.js (Static HTML Export)npx next buildout

Environment variables your frontend needs (such as VITE_API_URL) must be added separately in the Cloudflare project settings.

The lesson from this

Zeabur was convenient because it bundled deployment, databases, domains and AI services together. That also meant that when it had problems, everything had problems at once. While you move, do at least these three things:

  1. Keep DNS somewhere you control (Cloudflare, for example), not with your host. Next time you move, you only change a few records
  2. Back up your database daily to a different provider. If your host is platform A, store backups in platform B’s object storage
  3. Before choosing a platform, make sure you can take all your data with you. Can you download a full backup in a standard format such as .sql at any time? That matters more than the free tier