283 posts tagged with "Migration"
Migrating off hosted platforms like Render, Heroku, Railway, and Fly.io

Heroku Wants $140+/mo for Your Django App. Fly.io Does It for $15–$35: Pricing a Django Exit in 2026
A production Django stack — web, Celery worker, scheduler, Postgres, Redis — bills $140+/mo on Heroku against $15–$35 on Fly.io. A line-by-line recompute across Render, Railway, Fly.io, and flat-rate Hetzner, plus the migration costs and sensitivity cases that move the ranking.

Heroku to Kubernetes With Near-Zero Downtime: What Migration Services Sell vs. What the Cutover Requires
A service-by-service read of Qovery's modernization roundup: consultancies and hyperscalers run the cutover, platforms own day two, and the only honest downtime number is a minutes-long database write pause — plus what the same stack costs on owned hardware.

Koyeb vs Sevalla in Late 2026: Serverless Scale-to-Zero vs $5 Instances vs a Flat Hetzner Box
The same small production app — web service, Postgres, Redis, 100 GB egress — priced on Koyeb, Sevalla, and a Hetzner box: ~$184 vs ~$209 vs ~$7 a month, plus the workload shapes where scale-to-zero beats flat instances and the crossover that flips the winner.

Railway's Second Managed HA Database Changes the Migration Math: MySQL HA Goes GA
Railway's MySQL HA went GA five months after HA Postgres. This breakdown works the cost math for renting both managed databases versus running both on owned hardware — and names the three things the HA checkbox still leaves unanswered.

Fly.io Killed GPUs on August 1: Where the Workloads Go and What They Cost Now
Fly.io shut down its entire GPU line on August 1, 2026 — not because it is failing, but because GPUs were never its core business. A side-by-side cost comparison with owned Hetzner hardware and hourly GPU markets, plus a migration map by workload shape.

Railway's May 2026 GCP Blackout: What an 8-Hour Outage Reveals About a Control Plane That Never Actually Left Google Cloud
Google suspended Railway's production account and healthy bare-metal workloads went dark for eight hours — because the control plane routing them never left GCP. A timeline of the cascade and a seven-question audit for your own platform.

Railway Retired Nixpacks for Railpack: What Changed in the Zero-Config Build Path
Railway replaced Nixpacks with Railpack after 14 million builds exposed the cost of approximate versions and monolithic image layers. A before-and-after of the auto-detect build path, why Cloud Native Buildpacks lost twice, and what platform builders should steal.

From $7,000 on AWS to $780 on Hetzner: An Honest Accounting of an 89% Cost Cut
A team swapped a $7,000+ AWS Kubernetes bill for four €179 Hetzner servers — then listed what the $780 doesn't cover. A line-by-line audit of managed control planes, load balancing, backups, and on-call, plus the decision rule for when the 89% saving is real.

Render Never Ran Your Heroku Buildpacks — Here's What Rebuilding That Compatibility Costs With Paketo vs Nixpacks
Render never executed your Heroku buildpacks — it absorbed them behind a generated Dockerfile. Here is what rebuilding that compatibility on machines you own actually costs, with Paketo and Nixpacks priced head-to-head.