283 posts tagged with "Migration"
Migrating off hosted platforms like Render, Heroku, Railway, and Fly.io
Vercel Now Deploys Your Dockerfile — and Admits Functions Weren't Enough
Vercel's summer 2026 Services release — multi-framework projects, private Service Bindings, and Dockerfile deploys — concedes the multi-service model Render, Railway, and Fly.io always sold. Here is what shipped, the capability-by-capability gap table separating functions from persistent services, and a decision rule for which side your stack falls on.
Beyond the Big Four: What the Heroku-Alternative Long Tail Gets Right That Render and Railway Don't
Back4App's February 2026 ranking looks past Render and Railway to Sevalla, Upsun, Coolify, and Elastic Beanstalk — a verdict on where each second-tier Heroku alternative wins, where it loses, and the owned-hardware endgame the ranking never prices.
Fly Postgres Is a Thin Provisioning Layer: The Exit Math When 'Managed' Stops at Replication and Backups
Fly Postgres provisions machines and replication but leaves pooling, monitoring, and failover to you. A worked three-way bill — classic Fly Postgres vs Managed Postgres vs CloudNativePG on owned nodes — for teams pricing an exit.
Fly.io vs Railway vs a $5 Droplet: What the No-Container Counter-Narrative Gets Right — and Where It Breaks at the Second Service
A $286 PaaS bill sparked the honest question: why not skip the platform and run a binary on a $6 droplet? Real 2026 numbers show the droplet wins for one app — until the second service arrives.
Heroku's Quiet End of Life: A 90-Day Exit Playbook for Teams Still Paying by the Dyno
Salesforce moved Heroku to sustaining engineering in February 2026: no new features, no new Enterprise contracts. A 90-day exit playbook with the Salesforce sunset precedent, a 12-row pre-migration audit, week-by-week phases for a Postgres plus web plus worker stack, and the honest first-year cost of moving versus waiting.
Ingress-NGINX Is Retired. Your PaaS Inherited Its Quirks — Audit Them Before They Become Outages
Ingress-NGINX retired in March 2026, leaving five silent routing behaviors behind. This behavior-by-behavior audit maps each quirk to what breaks on a naive Gateway API migration — and what a self-hosted PaaS routing layer must now own explicitly.
Railway's $100M Series B: What VC Runway Buys Against Hardware You Own
Railway raised $100M to scale AI-native cloud infrastructure. A line-by-line comparison of metered hosted bills against owned hardware, plus the stay-or-migrate checklist the raise forces every team to run.
Your PaaS Bill Lied to You: Run a Bill-Forensics Audit Before You Migrate
A developer budgeted $20 and opened a $286 PaaS bill. This six-step bill-forensics checklist audits Railway, Render, Fly.io, and Vercel invoices line by line — new-since-signup charges, usage-scaled meters, seat math — before you decide to migrate or self-host.
Cilium 1.20 Retires Two More Boxes: TCP Routes, Gateway Auth, and the Case for a CNI-Run Fleet
Cilium 1.20 adds TCPRoute/UDPRoute and gateway ExternalAuth to its Gateway API support, closing the last gaps that kept small fleets running a separate ingress controller and auth proxy. Here is the consolidation map, the concrete migration costs, and where a service mesh still earns its keep.