283 posts tagged with "Migration"
Migrating off hosted platforms like Render, Heroku, Railway, and Fly.io
Railway's $100M AI-Native Cloud vs a $42 Hetzner Box: A Worked Bill Recompute
Railway's $100M AI-native cloud pitch promises 50% savings over hyperscalers, but a line-by-line recompute of a steady API, worker, and Postgres puts the per-second meter at $106.50/month against $42.60 for a flat Hetzner box, with the crossover near 25% utilization.
Django's Go-To Hosting List Now Says: Rent the Server, Run the Platform Yourself
A September 2026 commit to awesome-django added Deployment Services and Self-Hosted Deployment sections, making bring-your-own-server PaaS a first-class answer. Here's the before/after taxonomy, the cost math behind it, and what it means for your next Django deploy.
The Fly-Plus-Neon Stack: What an 8,700 km Gap Between App and Database Really Costs
A real 2026 production stack ran Fly.io compute in Johannesburg against Neon Postgres in Frankfurt. We total both bills, budget the 150 ms latency floor, and price the consolidated alternative.
Ingress2Gateway 1.0: A Scripted Migration Path Off the Now-Read-Only Ingress-NGINX
Ingress-NGINX is archived and unpatched — ingress2gateway 1.0 converts existing Ingress objects to Gateway API automatically. What converts cleanly, what needs hand-migration, and the five behaviors that break silently.
Should You Run Plain Docker Compose in Production in 2026? Where the Single-Host Ceiling Actually Sits
A May 2026 Hacker News thread's verdict on Docker Compose in production, turned into a three-gap accounting: which of zero-downtime deploys, self-healing, and multi-host have cheap single-host fixes, where the real ceiling sits, and what a Cluster-API-managed fleet closes.
Heroku Is Frozen, the Guide Says Fly.io: What 'Regions Plus a Great CLI' Costs on Rented VMs vs. Two Hetzner Boxes
FlightFormation's October 2026 guide steers teams off frozen Heroku toward Fly.io's regional VMs and excellent CLI: a three-way priced teardown of the same two-region reference stack on Heroku, Fly.io, and owned Hetzner hardware, with the Postgres, egress, and region-count sensitivities that decide between per-unit meters and flat boxes.
Gateway API v1.5 Is Stable: What a Self-Hosted Fleet Gains by Leaving Ingress Behind, and What the Move Costs
Gateway API v1.5 and v1.6 graduated TLS passthrough, CORS, mTLS, and TCP/UDP routing to stable while ingress-nginx went unpatched. A self-hosted fleet's migration guide: an annotation mapping table, a worked Ingress-to-HTTPRoute rewrite, and the real cost of the move.
Railway Won the Default for Small Projects in 2026 — Here Are the Edge Cases That Push Growing Teams Off It
Railway won the small-project default with metered pricing, the fastest deploys, and a $5 trial. This inventory names the five edge cases that push growing teams off it — always-on billing, preview costs, ephemeral storage, containerized Postgres, per-seat teams — and works the bill-size threshold where a fixed box wins.
Railway Killed Prepaid Billing. That's Your Migration-Timing Signal.
Railway now requires a post-paid card, ending prepaid credits. A prepaid balance is lock-in; post-paid is month-to-month exit freedom — plus a 5-check migration-timing checklist and a cost anchor for the same workload.