SaaS
Zeabur
Zeabur, the cloud application-deployment platform (a Railway/Render-style PaaS), is winding down: new purchases stopped immediately, dedicated-server renewals are disabled and shared-cluster services pause on 1 December 2026, and all dedicated servers and shared clusters are shut down on 31 December 2026
departs 31 Dec 2026
Quick answers
- Is it true that Zeabur is shutting down its deployment platform on 31 December 2026?
- Yes. Zeabur has officially announced it, effective 31 Dec 2026. Zeabur is a cloud platform-as-a-service for deploying applications, databases and services from a Git repo — the same category as Railway, Render and Fly.io.
- When does it take effect?
- 31 Dec 2026. Verified against the vendor's own announcement.
- What should I use instead?
- Plan a migration off Zeabur before 31 December 2026, and don't wait for the paused state on 1 December to force the issue.
What this means for you
Zeabur is a cloud platform-as-a-service for deploying applications, databases and services from a Git repo — the same category as Railway, Render and Fly.io. In an official blog post, founder Yuanlin Lin says Zeabur Inc. is winding down operations, citing security incidents in August and October 2026 together with architectural complexity, slowing growth and operational challenges. Three dates matter if you run anything on Zeabur. **Effective immediately:** new purchases are halted. **1 December 2026:** renewals for dedicated servers are disabled and shared-cluster services are paused. **31 December 2026:** all dedicated servers and shared clusters are shut down — the hard end of the platform. Zeabur says the data-deletion date, the final data-export deadline, and the date its support channel closes are **not yet finalised**, so those are watch items rather than firm dates today. Anything you host on Zeabur — web services, APIs, databases, cron jobs — needs a new home before the end of the year, and any custom domains pointed at Zeabur need to be moved.
Where to go
Plan a migration off Zeabur before 31 December 2026, and don't wait for the paused state on 1 December to force the issue. Export your data and configuration now while the platform is fully running; Zeabur has published a "migrate from Zeabur" guide (with Markdown versions aimed at AI coding agents) and offers self-service domain transfers, account-balance refunds, and case-by-case help through its support channel. Re-deploy your services on another PaaS — **Railway**, **Render**, **Fly.io** and **Koyeb** are the closest like-for-like Git-push platforms; **Coolify** or **Dokploy** are self-hosted options if you'd rather run your own. For databases, take a dump and restore it on the new host rather than relying on a platform-to-platform transfer. Because the final export deadline and data-deletion date are not yet announced, treat your own data export as the safe deadline and get it done well before 31 December.
- Railway — Git-push PaaS, closest like-for-like for Zeabur app + database deploys
- Render / Fly.io / Koyeb — managed deployment platforms with databases and services
- Coolify or Dokploy — self-hosted, open-source PaaS if you want to leave managed hosting entirely
Zeabur has announced it is shutting down its deployment platform on 31 December 2026. In an official blog post, founder Yuanlin Lin says Zeabur Inc. is winding down operations, pointing to security incidents in August and October 2026 alongside architectural complexity, slowing growth and operational challenges. Zeabur is a Railway/Render-style platform-as-a-service for deploying apps, databases and services straight from a Git repository.
The dates that matter
- Effective immediately — new purchases are halted.
- 1 December 2026 — renewals for dedicated servers are disabled, and shared-cluster services are paused.
- 31 December 2026 — all dedicated servers and shared clusters are shut down. This is the hard end of the platform.
The company says the data-deletion date, the final data-export deadline, and the date support closes have not yet been finalised — so those remain open, and we’ll update this entry when Zeabur publishes them.
What to do
Everything you host on Zeabur needs a new home before the year ends, and because services pause on 1 December, treat that as the real cut-off rather than the 31st. Export your data and configuration now, while the platform is fully up. Zeabur has published a migration guide and offers self-service domain transfers, balance refunds, and case-by-case support. The closest like-for-like destinations are Railway, Render, Fly.io and Koyeb; if you’d rather stop depending on a managed platform, Coolify and Dokploy are self-hosted options. For databases, take your own dump and restore it on the new host. With the final export deadline still unannounced, your own completed export is the only deadline you control.
Entry changelog
- — last reviewed.
- — Entry created from Zeabur's official "Zeabur is shutting down" blog post (zeabur.com/blogs), which our fetcher reads cleanly. Dates quoted directly from the announcement: new purchases halted immediately, dedicated renewals disabled and shared clusters paused 1 December 2026, full shutdown of all dedicated servers and shared clusters 31 December 2026. The post states the data-deletion date, final export deadline and support-close date are not yet finalised — recorded as watch items, not inferred (Constitution §3.2). detect left empty: Zeabur usage lives in a platform dashboard and optional zeabur.json/zbpack.json config, with no single literal safe to fingerprint without false-firing.
Put this countdown in your README
Building on Zeabur? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/zeabur-shutdown)Spot an error or a changed date? Tell us and it’s corrected the same night.