OxyPages

A Zeabur Alternative Before The 31 December Shutdown

A Zeabur Alternative Before The 31 December Shutdown

Zeabur shuts down on 31 December 2026. A Zeabur alternative for each half of your project, the API and the front end, plus a dated migration checklist.

The OxyPages Team · · 9 min read

You got the email on 17 October, or you saw the banner, and now there's a date in your calendar you didn't put there. Zeabur is shutting down, and December 31 is the final day.

If you run a small SaaS on it, you probably set it up the easy way: one Zeabur project holding the front end, the API and a Postgres database. That convenience is what makes the move feel big.

Here's the thing I'd tell a friend in that spot. You don't need a Zeabur alternative that does everything Zeabur did. You need two homes, one for the code that runs on a server and one for the files a browser downloads, and the second one is the easy half.

That split is how we run our own product: the API on a server, the front end on a separate host.

Below: the dates, six places worth moving to, and a dated checklist. Zeabur details come from its shutdown post; prices are as of November 2026.

TL;DR: Zeabur announced on 17 October 2026 that it is winding down. New servers and domains stopped selling straight away, servers go offline on their expiry dates from 1 December, shared-cluster services pause on 1 December, and 31 December is the final shutdown date. The data deletion date isn't set yet, so don't wait for it. Treat a full-stack project as two moves: the API and database go to a platform that runs servers (Railway, Render, Northflank or Fly.io), and the built front end goes to a static host (Cloudflare, Netlify or similar). For one solo app, that's roughly $5 to $15 a month.

If you only ever ran a static site on Zeabur, the simpler question is covered in a static hosting comparison across every option. This post is for the people with a server in the mix.

What Is Happening To Zeabur, And When?

Zeabur is closing for good on 31 December 2026, with parts of it switching off from 1 December. The founder's post gives two reasons: growth that ran into limits, and two security incidents in 2026, in late August and on 14 October.

The dates that matter, from that post:

  • 17 October 2026: no new dedicated servers or domains can be bought. Balance refunds and migration help go through Zeabur Support.
  • 1 December 2026: server renewals are switched off, and each dedicated server shuts down on its own expiry date between 1 and 31 December. Every running service on a shared cluster is paused, though you can restart one by hand to back up data.
  • 31 December 2026: every dedicated server and shared cluster stops.
  • To be announced: the data deletion date, the final export deadline and the day support closes.

That last line is the trap. "Not announced" is not the same as "later". Plan as if your data is gone on 31 December, because nothing says otherwise.

One useful detail: domains bought through Zeabur can be transferred out from the dashboard yourself. Do that early, since a domain transfer can take several days to finish.

What Zeabur Got Right

Zeabur's real strength was one project for everything. A front end, a backend, Postgres and a message queue sat side by side, and a Git push redeployed the lot.

That's hard to replace with a single product. If your project has five or six services talking over a private network, keep the stack together on Railway or Render, the closest match.

For a solo developer with one front end, one API and one database, though, the all-in-one shape was a convenience, not a requirement. Which brings us to the split.

Split The Project Before You Pick A Host

Split The Project Before You Pick A Host - OxyPages

A full-stack app is two kinds of thing, and they want different hosting. The API is a program that has to keep running, take requests and talk to the database. The front end, once built, is a folder of HTML, JavaScript and images that never runs on a server at all.

Run npm run build on a Vite, React, Vue or Astro front end and look at the dist folder. That folder is the whole front end, and any static host can serve it, usually free or close to it.

Why bother splitting at all? Three reasons:

  1. The front end stops eating server bandwidth and compute, which is metered on most app platforms.
  2. A slow API deploy no longer takes the marketing pages down with it.
  3. Next time a platform closes, you only move one half.

The cost is one new thing to understand: your front end and API now sit on different addresses, so the API has to allow requests from the front end's address. That's called CORS, and it's one setting on the API. MDN's guide to cross-origin resource sharing explains it in plain terms.

Picking A Zeabur Alternative For Each Half

The short answer: a server platform for the API and database, a static host for the built front end. Here are six options, all checked on the vendors' own pages in November 2026. Prices are monthly.

HostTakes which halfFree tierReal starting priceThe catch
RailwayAPI + databaseFree plan with $1 of usage credit a month after a 30-day, $5 trialHobby, $5 a month minimum, includes $5 of usageNo custom domain on Free; egress billed at $0.05/GB
RenderAPI + database1 free 512 MB web service; free Postgres$7 a month for the smallest always-on serviceFree service sleeps after 15 minutes; free Postgres expires after 30 days
NorthflankAPI + databaseSandbox: 2 services, 2 jobs, 1 database, always on, no cardFrom $12 a month (0.5 vCPU, 1 GB)Two-service cap; commercial use not addressed on the pricing page
Fly.ioAPI + databaseNone; $1 trial credit for 7 daysSmallest always-on VM $2.19 a month, plus egressDocker and a command line; managed Postgres from $38 a month
CloudflareFront endUnlimited static requests, 500 Pages builds a monthWorkers Paid, $5 a month, if you add server codeTwo overlapping products, Pages and Workers
OxyPagesFront end only1 non-commercial site on a subdomainLite, $5 a month or $48 a year, commercial use and custom domainsNo servers, functions or databases; page-view quotas

Railway

Railway is the closest thing to Zeabur's "everything in one project" feel. Services and databases sit together, builds are free, and billing is by the second. The $5 Hobby fee is a minimum, not a cap, and egress is metered.

Render

Render suits anyone who wants to test free first. The free web service sleeps after 15 minutes and takes about a minute to wake, which a paying customer will notice. For production, budget $7 a month for the API plus a paid database from $6.

Northflank

Northflank's free Sandbox is the most generous always-on option here: enough for an API, a worker and Postgres, with no sleeping and no card. Read its terms yourself if the app is commercial, since the pricing page doesn't say.

Fly.io

Fly.io suits people happy with Docker who want control over regions. A personal account's bill under $5 a month is waived with a card on file. Compute is cheap; managed Postgres is not, so many people pair Fly with a separate database provider.

Cloudflare For The Front End

Cloudflare suits a front end that may grow, because static requests are free and unlimited, and its terms carry no non-commercial clause. The confusion is that Pages and Workers overlap, and Cloudflare now tells new projects to start on Workers.

OxyPages, For The Front End Only

We fit the front-end half and nothing else. You connect the GitHub repo, we build the Vite or React output and serve it with SPA routing, or you upload the built folder. A SaaS is commercial, so the free plan doesn't apply; it starts at Lite. We don't run servers, functions or databases, so the API has to live on one of the four platforms above.

A Worked Example: One Front End, One API, One Database

Say you run a small booking tool. A Vite React front end at app.yourdomain.com, an Express API at api.yourdomain.com, and Postgres, all in one Zeabur project. Here's the move, about an afternoon of work.

  1. Back up the database first. Run pg_dump against the Zeabur Postgres and keep the file somewhere that isn't Zeabur. If it's after 1 December and the service is paused, restart it by hand to do this.
  2. Stand up the API and database on the new platform. Create Postgres, restore the dump with psql or pg_restore, deploy the API from the same repo, and copy every environment variable across.
  3. Test the API on the platform's own address before touching DNS. Log in, create a booking, check it lands in the new database.
  4. Point the front end at the new API. In a Vite app that's usually one variable, such as VITE_API_URL, set in the new host's build settings. Build and deploy the front end to the static host. If the app's routes 404 on refresh, the host needs single-page app mode turned on; deploying a Vite app step by step covers that.
  5. Allow the front end's new address in the API's CORS settings. Skip this and every request fails with a CORS error in the browser console.
  6. Lower the DNS TTL to 300 seconds a day ahead, then switch api and app to the new hosts. Keep Zeabur running until both answer correctly on a phone on mobile data.

Step 5 is the one that bites. The app loads, the login button does nothing, and the console is full of red.

A Dated Migration Checklist

A Dated Migration Checklist - OxyPages

Work backwards from the earliest date that applies to you, which may be well before 31 December.

  • By 23 November: find your dedicated server's expiry date in the Zeabur dashboard. That date, not 31 December, is your real deadline.
  • By 25 November: start any domain transfers out of Zeabur, and request a balance refund through support.
  • By 30 November: take a full database backup and copy every environment variable into a password manager. Shared-cluster services pause the next day.
  • First week of December: run the new API and front end side by side with the old ones, then switch DNS.
  • Before your server's expiry date: confirm the old project gets no traffic and nothing still calls it.
  • By 31 December: everything is off Zeabur. Watch for the announced data deletion date and download anything you missed before it.

What To Do Next

Open your Zeabur project and sort every service into one of two piles: runs on a server, or is a built folder of files. That ten-minute exercise decides everything else.

Put the server pile on Railway, Render, Northflank or Fly.io, whichever matches your budget. Put the files pile on a static host. If you want the front end on a flat price with no bandwidth meter and you're fine with no server code, compare the plans. If your front end needs server rendering, choose a platform that runs it, such as Render or Railway, and keep both halves there.

In the end, any Zeabur alternative beats the one you're still setting up when your server expires. Start with the database backup today.

FAQ

When Exactly Does Zeabur Shut Down?

December 31, 2026 is the final shutdown date. Before that, dedicated servers stop renewing from 1 December and each one goes offline on its own expiry date, and shared-cluster services are paused on 1 December. The data deletion date and export deadline hadn't been announced as of 18 November 2026.

Can I Move My Whole Zeabur Project To One Platform?

Yes, if it runs servers. Railway and Render both host a front end, an API and Postgres in one place, which is the closest match to how Zeabur worked. Splitting the front end onto a static host is optional, but it usually cuts cost and means a future move only touches the API.

What Happens To A Domain I Bought Through Zeabur?

You can transfer it out yourself from the Zeabur dashboard. Start early, because registrar transfers can take several days, and new domain sales stopped on 17 October 2026. Once it has moved, point its records at the new hosts.

Is There A Zeabur Alternative That's Free For A Full-Stack App?

Northflank's free Sandbox runs two services and a database, always on, with no card. Render has a free web service and free Postgres, but the service sleeps after 15 minutes and the database expires after 30 days. For a paying product, expect to spend about $5 to $15 a month on any Zeabur alternative once both halves are covered.

Try It Now

Still Here? Drop It In.

The whole pitch fits in one sentence: your HTML, on a link, in seconds.

Drag and drop your HTML files, a folder, a ZIP, your app's build folder, a PDF or an image

or ·

No account needed. Your unclaimed website stays live for 30 minutes on a free subdomain. Claim it to your account to keep it permanently.

  • No Account Needed
  • Free SSL
  • 30-Minute Unclaimed Link, Claim To Keep It