Angelo Saraceno
"Cloud hosting" is the broadest of the three terms. It covers everything from a Linode VM you SSH into and configure by hand, through a managed PaaS that runs your container and your Postgres on one bill, all the way to a Cloudflare Worker that exists for sixteen milliseconds at the edge. The platforms that win on this term in 2026 are not all doing the same thing. They sit at different points on an abstraction ladder, and a real "best" answer depends on which rung your team should be on.
We make Railway, so this is partisan. I will tell you, out loud, where the answer isn't us.
House rule: every claim in this post is sourced.
The 2026 cloud hosting ladder
Every platform in this post sits at one of five rungs.
Rung 1: VPS / IaaS. You rent a VM, you SSH in, you install everything yourself. Linode, AWS Lightsail, Vultr, DigitalOcean Droplets. Cheap and flexible; the ops cost is yours.
Rung 2: Managed VPS / shared hosting. Same as above but the host runs the OS updates and the database for you. Mostly the traditional hosts (Hostinger, Bluehost) and Lightsail's higher tiers. Cheap, low ceiling, fine for static sites and tiny apps.
Rung 3: Containers-as-a-service. You hand the platform a container, it gives you a URL. Cloud Run, AWS Fargate, App Runner before it began moving to maintenance mode (announced March 31, 2026; stops accepting new customers April 30, 2026; existing customers continue). Modern abstractions, but the integration story (database, queue, networking) is still yours.
Rung 4: PaaS. The platform owns the runtime, the buildpack abstraction, the database as a managed primitive, and the deploy story. Railway, Heroku, Render, Northflank, Fly, Vercel. Most of what gets called "modern cloud hosting" sits here.
Rung 5: Agentic PaaS. Same as a PaaS, but the deploy is increasingly driven by an agent (Claude Code, Cursor, Codex) over MCP or a CLI capability like the Stripe Projects CLI. Railway is betting the hardest on this rung; most platforms have not yet picked a position.
The higher you go, the less you operate, and the less escape hatch you have if your needs sit at a lower rung. Pick the rung that matches the work, not the one with the prettiest landing page.
The ten platforms, ranked
At a glance:
1. Railway
Best for full-stack apps that want PaaS and a path to agentic deploys.
I run Railway, so the bias declaration is up front. Railway is the PaaS where the runtime, the managed Postgres / MySQL / Redis / Mongo, the private networking, the cron jobs, and multi-region for stateless services all live on one surface and one bill. One-click high-availability Postgres on Patroni shipped in March 2026; agentic provisioning via the Stripe Projects CLI shipped a few weeks later. On the ladder, we sit at rung 4 by default and rung 5 increasingly.
Features: git-deploy, native Postgres / MySQL / Redis / Mongo, one-click HA Postgres (Patroni), private networking, MCP server and Claude Code-friendly DX, Stripe Projects CLI agentic provisioning, per-environment secrets, persistent volumes, multi-region stateless services.
Pricing: $5 Hobby with included usage credit, Pro at $20/seat with usage on top. Usage-based pricing has a real downside I'm not going to talk around: if you don't watch the dashboard, a viral weekend can grow your bill. Set spend alerts on day one. The trade-off is that you don't pay for what you aren't using.
Best for teams shipping a full-stack product that needs a real backend and a real database. Teams who want one platform instead of stitching several together. Teams who want agent-driven deploys to work end to end.
Honest trade-offs: cross-region multi-master Postgres writes aren't on the menu yet. Enterprise procurement (dedicated capacity, the deepest end of compliance attestations) is younger than AWS or Heroku.
Compare: Railway vs Fly, Railway vs Render, Railway vs Vercel.
2. Vercel
Best for frontend-flavored hosting.
Vercel sits at rung 4 for frontend-shaped workloads. If your product is mostly Next.js, this is the right answer; you can move on.
Vercel shipped a real answer to the long-running-cost critique in 2025: Fluid Compute with Active CPU pricing, which only charges for active CPU on idle-heavy or streaming workloads, can cut function bills by 80%+ on the right traffic shape. The compute cost story is now competitive on I/O-bound workloads.
Features: frontend-optimized CDN, native Next.js integration, Edge Functions, image optimization, preview deployments, Fluid Compute with Active CPU pricing, Vercel Postgres (Neon-backed), Vercel KV.
Pricing: Hobby free; Pro $20/seat with included credit, plus usage-based add-ons. Bandwidth and per-seat costs are the more legitimate 2026 critique; "Vercel cost me $286 on a $20 plan" is a genre of post for a reason.
Best for frontend-heavy applications. Static and ISR-heavy Next.js sites. Teams already standardized on Vercel's tooling.
Honest trade-offs: the backend story is still several primitives in one trench coat. For long-running stateful workloads, you are better served pairing Vercel with a real backend PaaS.
Compare: Railway vs Vercel.
3. Render
Best for predictable, monthly-bill hosting.
Render sits at rung 4 with predictable pricing as its identity. If you need a web service, a worker, a Postgres, and a flat invoice you can defend in a budget meeting, Render is, for most teams, exactly that.
Features: git-deploy, managed Postgres, Key Value (Redis-compatible), cron jobs, private networking, autoscaling on Standard tier and above, preview environments.
Pricing: instance-based tiers starting at $7/month for the first paid web service. Managed Postgres in the same neighborhood. No surprise usage spikes.
Best for small to mid-size apps that fit cleanly into "web service, worker, database." Teams who care more about a predictable bill than about scale-to-zero economics.
Honest trade-offs: free-tier services sleep aggressively (15-minute idle timeout). Multi-region is effectively one region per service, with Frankfurt as the only EU option.
Compare: Railway vs Render.
4. Heroku
Best for institutional Heroku gravity (with an asterisk).
Heroku invented rung 4. Every other modern PaaS on this list owes a design debt to Heroku's dyno + buildpack + add-ons model (I wrote that argument out at length earlier this year). In February 2026 Salesforce moved Heroku into sustaining-engineering mode and laid off roughly a thousand people across Heroku, Agentforce, and adjacent teams (reported Feb 2026).
There are still legitimate reasons to stay: procurement gravity, compliance review cycles measured in quarters, an existing add-on contract you can't unwind this fiscal year. A platform in sustaining mode does not change those constraints, it changes how long you have to plan the exit.
Features: buildpacks, the add-ons marketplace, Heroku Postgres, Redis, ten regions (Mumbai and Montreal joined in late 2025). The Fir runtime exists; I have not seen a single greenfield team pick it.
Pricing: per-dyno, per-add-on, Salesforce-flavored. The Eco tier ($5/mo, sleeps) replaced the free dyno.
Best for teams who already know Heroku, have legacy apps deployed there, and have no urgent reason or political ability to migrate.
Honest trade-offs: sustaining mode. No native cross-region. Pricing rose while the feature set did not.
Compare: Top Heroku alternatives.
5. DigitalOcean
Best for the VPS-to-PaaS bridge.
DigitalOcean is the only platform on this list that sits on multiple rungs at once. Droplets are rung 1, App Platform is rung 4. If your team is moving from "we run a couple of VMs" up toward "we want a PaaS abstraction" without changing vendor, DigitalOcean is the cleanest path.
Features: Droplets (VPS), App Platform (PaaS), managed Postgres / MySQL / Redis / Kafka (each separately billed), Spaces (S3-compatible), Kubernetes service.
Pricing: Droplets start around $4/mo, App Platform container web services from $5/mo, managed Postgres adds $7+/mo on top.
Best for small apps with predictable load, teams who want to start at rung 1 and move up without re-platforming, projects where budget legibility matters more than developer experience.
Honest trade-offs: App Platform's developer experience is years behind the modern PaaS bar. Support depth for production issues is the recurring complaint I hear when teams call to evaluate alternatives.
6. Cloudflare (Pages + Workers + R2)
Best for edge-first global hosting.
Cloudflare is the only platform on this list that lives mostly at the edge. Pages is static plus serverless functions; Workers is the serverless-at-the-edge primitive; D1 is SQLite running in every Cloudflare datacenter; R2 is S3-compatible object storage with no egress fees. On the ladder, Cloudflare sits between rung 3 and rung 4, with a different theory of the workload entirely.
Features: global edge CDN, Workers serverless at the edge (V8 isolates with sub-millisecond cold starts), Pages with native framework support, D1 (SQLite at the edge), R2 (no-egress object storage), KV, Queues, Durable Objects.
Pricing: Workers free up to 100k requests/day, then $5/mo for 10M requests. Pages free for most static use. R2 charges for storage but no egress.
Best for global static sites and apps, anything where edge latency matters, anyone running up bandwidth bills elsewhere (R2 alone often pays for the rest of the stack), workloads that fit the request-scoped Worker model.
Honest trade-offs: the Worker runtime is not Node, and not all npm packages run on it. Anything stateful or long-running pushes you back to a rung 4 platform. D1 is interesting but young; for production Postgres workloads you are still pointing at Neon, Supabase, or a hosted database elsewhere.
7. Fly.io
Best for low-latency global apps with ops capacity.
Fly sits between rungs 3 and 4. The contract is closer to "deploying VMs" than "deploying applications," but the multi-region primitive is real and few others on this list have it the same way.
Features: native multi-region deploys, edge instances, Firecracker-based microVMs, managed Postgres with regional read replicas, fly-replay header routing.
Pricing: per-VM, per-second machine billing. Legible once you understand the model, less legible if you don't. GPUs were deprecated for new accounts in 2024; if you need GPUs in 2026, look at Cloud Run, Northflank, or specialized providers.
Best for latency-sensitive services. Teams that have measured user latency and decided it matters. Anyone running an LLM endpoint, a multiplayer server, or an edge cache that needs to be in twelve places.
Honest trade-offs: reliability is the dominant 2026 critique. The October 2024 fleet-wide orchestration outage cast a long shadow, and the platform has had a steady drumbeat of incidents through 2025 and into 2026; check their public infra log before you commit. Ops surface is also higher than peers.
Compare: Railway vs Fly.
8. Northflank
Best for Kubernetes-shaped or BYOC hosting.
Northflank is rung 4 sitting on top of Kubernetes. Their bring-your-own-cloud story is strong, and they have leaned into enterprise AI and BYOC AI sandboxes as their wedge.
Features: Kubernetes-native scheduling, BYOC into AWS / GCP / Azure / Oracle / CoreWeave / bare metal / on-prem, preview environments, native managed databases, GPU support, microVM isolation, audit logging and SSO.
Pricing: per-instance with no markup on your underlying cloud cost when you BYOC. Sandbox is free with a credit card.
Best for teams who have decided Kubernetes is non-negotiable, teams running AI workloads that need GPU plus microVM isolation, or teams with a compliance reason to keep workloads in their own VPC.
Honest trade-offs: the Kubernetes mental model leaks through in a way that, for most teams, adds surface area. Their own listicle's critique of Railway leans on framing ("smaller ecosystem," "limited advanced features") that has not tracked reality for a couple of years. The fact-check is yours to do.
9. AWS Lightsail
Best for the AWS-on-easy-mode bridge.
Lightsail is AWS's answer to "what if AWS had a simpler product line." On the ladder it sits between rungs 2 and 3: simple instances with fixed monthly pricing, managed databases, load balancers, and one-click application templates. It is AWS-flavor of DigitalOcean, more or less.
Features: virtual instances with fixed pricing, managed Postgres / MySQL databases, load balancers, object storage, one-click apps (WordPress, LAMP, Node, etc.), container service.
Pricing: instances from $3.50/mo. Databases from around $15/mo. Fixed monthly bill, predictable.
Best for teams that need to be in AWS for institutional reasons but don't want to learn EC2, IAM, and VPC. Teams running a WordPress site, a small Node app, a hobbyist project where AWS lock-in is fine.
Honest trade-offs: Lightsail is good for what it is, but the moment you outgrow it, you are not migrating to App Platform-style PaaS; you are migrating to full AWS, which is a meaningfully steeper hill. Plan that exit deliberately or pick a rung 4 platform from the start.
10. Linode (Akamai Cloud Computing)
Best for the no-nonsense VPS at the bottom of the ladder.
Linode (now Akamai Cloud Computing, since the 2022 acquisition) sits at rung 1. You rent a VM, you do everything else. The reason it earns a slot on this list is that for a non-trivial set of workloads, that is the right answer: anything where the team has the ops capacity, the cost ceiling matters, and the workload is stable enough that managed-everything is overkill.
Features: virtual instances across multiple regions, managed Postgres / MySQL / Redis, Kubernetes service, object storage, NodeBalancers, GPU instances.
Pricing: VMs from around $5/mo; managed databases from $15/mo; transparent and stable.
Best for teams with a Linux engineer, predictable workloads, anything where the ops cost is cheaper than the PaaS cost. Hobbyist or self-hosted-PaaS deployments (Dokku, Coolify, Caprover).
Honest trade-offs: you operate the VM. The OS updates, the disk, the backups, and the upgrades are yours. The Akamai acquisition has expanded the network footprint but the platform layer (managed databases, Kubernetes service) is still less mature than the modern hyperscalers.
Choosing your rung
Most listicles let you pick the platform first and worry about which rung it sits at later. The honest order of operations is the other way around.
Pick rung 1 (VPS) if: you have at least one engineer who likes operating Linux, your workload is stable enough that the time savings of higher rungs don't pay for themselves, or your cost ceiling is strict enough that the PaaS premium is the wrong trade.
Pick rung 2 (managed VPS) if: you are hosting a static site or a small dynamic app where the rest of the stack is so simple that the rung 1 ops cost is the only material decision.
Pick rung 3 (containers-as-a-service) if: your team already operates the database and the queue and the rest of the integration stack somewhere else, and you need a managed container runner. Most teams that think they want this want rung 4.
Pick rung 4 (PaaS) if: you want the platform to handle the runtime, the database, the buildpack contract, and the networking. This is where most full-stack teams in 2026 should be by default; the cost premium over rung 1 is real but smaller than the engineer-hour premium of doing it yourself.
Pick rung 5 (agentic PaaS) if: you want to deploy by talking to Claude Code, Cursor, or Codex, and you want the agent to provision databases and configure secrets without you in the loop. This is where Railway has leaned the hardest in 2026.
The wrong move on all five rungs is the same: picking the rung the marketing page tells you to pick rather than the one your team's actual constraints justify.
A closing note on the vanilla cloud
The implicit alternative to every platform on this list is rolling your own on AWS, GCP, or Azure directly. That is a real choice for the teams who have the platform engineer, the compliance posture, or the workload that doesn't fit a PaaS. Most teams don't have those constraints, and the "free" path into the hyperscalers costs roughly one engineer's quarter to set up cleanly, plus an ongoing support tier most people forget to budget. Every platform on this list is, on some axis, an argument for why you should not do all of that yourself.
Pick the rung that matches the work. If your current platform doesn't, migrate before another year of compounding migration tax accrues. I see this on calls every week.
And if your current "platform" is a folder of Terraform you wrote yourself on top of EC2, the right move is to give yourself the quarter back.
Happy shipping.
Angelo
Angelo Saraceno is a Solutions Engineer at Railway. Before Railway he was at Citrix, working inside Verizon and Lockheed environments, so he has seen what "enterprise IaaS" looks like after the slides come down. He writes about infrastructure, deployment, and the gap between how cloud is sold and how it runs in practice.