283 posts tagged with "Migration"
Migrating off hosted platforms like Render, Heroku, Railway, and Fly.io
Fly.io Turned Off Its GPUs on August 1: Where GPU-Backed Tenants Go Now (With Real Numbers)
Fly.io shut off GPU Machines on August 1, 2026 after cutting its free tier and 17 regions. A workload-by-workload cost comparison of the five destinations — Modal, RunPod, Koyeb, hyperscaler serverless GPUs, and owned Hetzner hardware — with the bin-packing math that decides between them.
The Free Tier Is Dead in 2026 Except Render: What Zero-to-Free Now Costs a Side Project on Each PaaS
Heroku killed free in 2022, Fly.io and Railway followed — only Render still offers a free-forever tier. A platform-by-platform accounting of trial credits, minimum paid floors, sleep schedules, and 12-month totals for a typical side project, against the flat-rate Hetzner box that never sleeps.
Heroku Dyno Math in 2026: What $50 Standard-2X and $250 Performance-M Bills Buy Against Owned Hetzner Hardware
A line-by-line pricing of typical $50 Standard-2X and $250 Performance-M Heroku stacks against a $55 owned Hetzner server, with exit sketches for buildpacks, databases, and review apps — and the month each move pays for itself.
Heroku Is Frozen and Fir Can't Run Your Dockerfile: Which Workloads to Move First
Salesforce froze Heroku in February 2026 and the Fir generation still can't run Docker images, leaving containerized apps with no on-platform future. A concrete sequencing plan: move the Docker workloads first onto a Dockerfile-native target, and let buildpack apps ride out Cedar.
Heroku to Kubernetes in a Weekend: The $140-to-€11 Migration Playbook
Salesforce put Heroku in sustaining mode in February 2026. This weekend runbook moves a $140/month web + worker + Postgres + Redis stack to a €11.37/month Cluster API fleet on Hetzner — commands, cutover sequence, both invoices, and the rollback plan.
From Heroku to Render at 2,800 RPS: What a Rails Migration's Latency Trade-Off Reveals Before You Self-Host
A 2,800-RPS Rails app makes the Heroku-to-Render decision concrete: routing, timeouts, queueing math, and incident fate, plus a checklist for stopping at Render or self-hosting instead.
The Heroku-to-Kubernetes Exit Industry, Mapped: 4 Vendors, 6 Steps, and an Honest Downtime Budget
Qovery's September 2026 guide maps the Heroku-to-Kubernetes exit market into four buyable vendor categories and one repeatable six-step cutover. The honest version: stateless services move with zero downtime, but promoting a new Postgres primary needs a planned write pause of seconds to minutes.
Railway Edge Rules vs a Gateway You Own: What Each Rule Costs to Replicate
Railway's Edge Rules put allow, block, challenge, redirect, and cache policy in a vendor console with no CLI. A rule-by-rule mapping of what each one costs to rebuild on a gateway you own — plus the migration checklist for policy that lives outside Git.
railway.json vs render.yaml vs fly.toml: What Each PaaS Config File Actually Declares
Railway, Render, and Fly.io each ask for a config file, but only Render's Blueprint declares databases, cron jobs, and preview environments. A clause-by-clause comparison plus the exact render.yaml surface a Render-compatible platform must honor to absorb migrators without repo rewrites.