LabHub

Blog

DevOps PaaS Platforms 2026 — Vercel / Fly.io / Render / Railway / Coolify / Dokploy / Kamal Deep Dive

2026-05-16 · 20 min read · #paas#devops#vercel#fly-io#render#railway#cloudflare-pages#netlify#coolify#dokploy#kamal#heroku#northflank#deep-dive#english

한국어English日本語

Prologue — Heroku left, and 14 PaaS platforms grew in its place

When Heroku unveiled "git push to deploy" in 2007, it looked like magic. One line — git push heroku main — sent your Rails app to the internet, and that became the definition of PaaS.

Then in November 2022, Salesforce-owned Heroku killed the free tier. That single event shaped the 2026 PaaS landscape. The developers who had built side projects on Heroku scattered, and 14 PaaS platforms grew to fill the space.

This is the picture as of May 2026:

This piece compares all 14 in one sitting and answers — who should pick what.

1. The 2026 PaaS map — managed / open-source self-hosted / roll-your-own on a VPS

In one line, a PaaS is "you git push your code and it runs on the internet." But in 2026, that single line splits into three lanes.

1.1 Three axes

Axis 1 — Managed cloud PaaS. Vercel, Fly, Render, Railway, Cloudflare, Netlify, Heroku, Northflank, Sevalla. Enter a card and you stop worrying. Infrastructure becomes invisible. In return, monthly usage shows up on the invoice.

Axis 2 — Open-source self-hosted PaaS. Coolify, Dokploy, Caprover, Easypanel. Install on a single VPS (Hetzner, DigitalOcean, OVH, Vultr) and you get a Vercel-like experience on top of it. Infrastructure cost is just the VPS bill. Backups, monitoring, security patches are your job.

Axis 3 — Roll your own on a VPS / lightweight container orchestrator. Kamal 2. Not a PaaS but "a clean way to deploy containers to servers you chose." Built by 37signals under DHH's hand, and the default deploy tool for Rails 7.2.

1.2 Cost vs control matrix

                  CONTROL ↑
                    |
    Kamal 2 ────────|──────── Coolify / Dokploy
    (raw VPS ops)   |        (OSS self-hosted)
                    |
    ────────────────+────────────────  COST →
                    |
    Heroku / Render |        Vercel / Cloudflare
    (classic PaaS)  |        (edge / serverless)
                    |
                  CONTROL ↓

Horizontal is monthly cost, vertical is infrastructure control. Upper left is cheap but you do everything. Lower right is one card and everything runs.

After the 2022 Heroku free-tier shutdown, the center of gravity for side projects shifted to the upper left. A USD-5 Hetzner VPS with Coolify installed can run five projects at once. That is the new default in 2026.

1.3 Git-driven deploys — the standard everyone shares

There is one thing every platform on all three axes shares. Git push is deploy.

Vercel standardized this flow in 2017, and by 2026 it reached even self-hosted PaaS defaults. Coolify, Dokploy, and Caprover all support GitHub webhooks and have preview-environment features.

2. Vercel — home of Next.js, inventor of Fluid Compute

In 2026 Vercel does two things at once. It is the home of Next.js, and with Fluid Compute it redefined the serverless paradigm.

2.1 Fluid Compute — the model that ended cold starts

Announced in August 2024, Fluid Compute can be summarized as "one instance handles many concurrent requests."

The classic AWS Lambda / Vercel Functions model:

The Fluid Compute model:

It especially shines for AI/LLM backends. If you call ChatGPT/Anthropic APIs and spend 90% of your time waiting on the network, other requests can use that idle time. Vercel claims about 1/3 the cost for the same traffic, and benchmarks match.

2.2 Vercel's strengths

2.3 Vercel's weaknesses

2.4 Who should pick Vercel

Avoid if: you run 24/7 daemons, serve 5 GB ML models, or have a strict cost ceiling on a side project.

3. Fly.io — multi-region + bare-metal friendly

Fly.io's one-line summary is "your Docker image runs in 30 cities at once." What differs from Vercel and Render is Fly Machines — Firecracker microVM-based containers running close to physical servers.

3.1 Multi-region model

When you deploy an app on Fly, you list regions in fly.toml.

app = "my-app"
primary_region = "nrt"

[build]
  image = "ghcr.io/me/app:latest"

[[regions]]
  code = "nrt"
[[regions]]
  code = "iad"
[[regions]]
  code = "fra"

This single setting starts instances in Tokyo, Virginia, and Frankfurt at once. Traffic routes to the nearest region. If you need Postgres, fly pg create spins up multi-region Postgres with WAL replication.

3.2 Fly's strengths

3.3 Fly's weaknesses

3.4 Who should pick Fly

4. Render — the right answer for Heroku replacement

In 2026 Render is the "most Heroku-like new PaaS." Founded 2019, Series B 50M USD in 2022, Series C in 2025 with serious enterprise moves.

4.1 Render's model

A single render.yaml (Render Blueprint) declares the whole infrastructure as code. It looks like an evolution of Heroku's app.json.

services:
  - type: web
    name: api
    runtime: docker
    dockerfilePath: ./Dockerfile
    envVars:
      - key: DATABASE_URL
        fromDatabase:
          name: api-db
          property: connectionString

databases:
  - name: api-db
    databaseName: api
    plan: standard

4.2 Render's strengths

4.3 Render's weaknesses

4.4 Who should pick Render

5. Railway — usability champion, Series B re-raised in 2024

Railway is loved for usability alone. They raised a Series B of 20M USD in May 2024 — proof that "PaaS is not dead."

5.1 Railway's model

5.2 Railway's strengths

5.3 Railway's weaknesses

5.4 Who should pick Railway

6. Cloudflare Pages + Workers + R2 — full-stack edge complete

Cloudflare entered the PaaS market last and with the most different model. The 2026 Cloudflare stack deserves the name full-stack edge.

6.1 Cloudflare stack composition

6.2 Cloudflare's strengths

6.3 Cloudflare's weaknesses

6.4 Who should pick Cloudflare

7. Netlify — JAMstack pioneer, transformed into composable full-stack

Netlify is the company that coined JAMstack in 2014. The 2026 Netlify adds full-stack capabilities to that identity.

7.1 Netlify today

7.2 Netlify's strengths

7.3 Netlify's weaknesses

7.4 Who should pick Netlify

8. Coolify (open source) — self-hosted Vercel

Coolify became the de facto standard for open-source self-hosted PaaS in 2026. A 2024 seed round kicked off full-time development, and GitHub stars passed 40k.

8.1 Coolify's model

8.2 Coolify's strengths

8.3 Coolify's weaknesses

8.4 Who should pick Coolify

9. Dokploy (open source) — Coolify alternative

Dokploy appeared in 2024 as an alternative to Coolify. As of May 2026, GitHub stars passed 20k, and it attracts "people who thought Coolify felt heavy."

9.1 Dokploy vs Coolify

ItemCoolifyDokploy
First appeared20202024
GitHub stars (May 2026)40k+20k+
Core languagePHP (Laravel)TypeScript (Next.js)
DatabasePostgresPostgres
Reverse proxyTraefikTraefik
Multi-serverBetaStable
PricingFree / CloudFree / Cloud

Dokploy's differentiator is that multi-server support shipped as a stable feature. Coolify still has multi-node in beta.

9.2 Who should pick Dokploy

10. Kamal 2 (37signals) — deploy to your own servers

Kamal is not a PaaS. It is a container deploy tool. 37signals (Basecamp, Hey) built it as part of leaving AWS, and Kamal 2 shipped in 2024.

10.1 Kamal's philosophy

10.2 Example deploy.yml

service: hey
image: 37signals/hey

servers:
  web:
    - 192.168.0.1
    - 192.168.0.2
  job:
    hosts:
      - 192.168.0.3
    cmd: bin/jobs

registry:
  server: ghcr.io
  username: my-org
  password:
    - KAMAL_REGISTRY_PASSWORD

env:
  secret:
    - RAILS_MASTER_KEY
    - DATABASE_URL

This single file enables kamal setup → kamal deploy.

10.3 Kamal's strengths

10.4 Kamal's weaknesses

10.5 Who should pick Kamal

11. Northflank / Sevalla / Caprover / Easypanel — other PaaS

11.1 Northflank — peak of Kubernetes PaaS

Northflank is the best at "wrapping Kubernetes in a PaaS UX." In 2026 it is one of the managed PaaS that takes the heaviest workloads.

Target: teams with 30+ containers, complex microservices, and enterprise compliance needs.

11.2 Sevalla — Kinsta's new PaaS

Sevalla is the new PaaS Kinsta — famous for managed WordPress hosting — launched in 2024. Built on Google Cloud, aimed at "the gaps in Vercel and Render."

Target: agencies running PHP and Node broadly — WordPress, Laravel, and friends.

11.3 Caprover — the oldest self-hosted PaaS

Caprover appeared in 2017. Docker Swarm-based. Before Coolify, it was the standard for self-hosted PaaS. Still 13k+ GitHub stars and stable.

Target: long-time users and teams that deliberately use Docker Swarm.

11.4 Easypanel — lightweight self-hosting

Easypanel appeared in 2022. Docker Compose-based. Lighter than Coolify with a clean UI.

Target: solo developers running 3–5 apps cleanly on a single VPS.

12. Heroku — a giant past its era

Heroku is still alive in 2026. It lost users after the 2022 free-tier shutdown but runs on the enterprise Salesforce customer base. In 2025 reports surfaced that IBM was considering acquiring Heroku, but as of May 2026 nothing is confirmed.

12.1 Heroku today

12.2 What Heroku still offers

12.3 Starting fresh?

Putting a new side project on Heroku is nostalgia. Render, Railway, and Coolify do the same thing cheaper and better. But if work already uses Heroku, the previous decision is not necessarily wrong.

13. Korea & Japan — Kakao i Cloud, Naver NCP, Sakura, KAGOYA, Conoha

Global PaaS isn't the whole story. Korea and Japan have their own PaaS and VPS ecosystems.

13.1 Korea — Kakao i Cloud / Naver NCP

If a Korean startup uses managed PaaS, Vercel, Render, or Fly come first when the user base is global. Naver NCP and Kakao i Cloud are more efficient when users are inside Korea.

13.2 Japan — Sakura, KAGOYA, Conoha, Heroku Japan

The 2026 standard for Japanese developer side projects has become "KAGOYA or Conoha VPS + Coolify or Dokploy."

14. Who should pick what — side project / startup / global / cost-sensitive

14.1 Side projects

14.2 Early-stage startup (seed)

14.3 Series A–B startup

14.4 Global users / edge

14.5 Cost-sensitive (solo / bootstrap)

This combo runs 5–20 projects in under USD 10/mo. The 2026 bootstrapper standard.

14.6 Korea / Japan local users

15. Decision tree — pick in 30 seconds

Side project? USD 0–5/mo?
├── Only Next.js → Vercel Hobby
├── Full stack + DB → Railway (usage-based)
├── 5+ projects → Hetzner + Coolify
└── Static + edge → Cloudflare Pages

Startup MVP? USD 20–100/mo?
├── Next.js → Vercel Pro + Neon
├── Rails/Django → Render
├── Multi-region → Fly.io
└── Cost-first → Coolify on Hetzner + Cloudflare

Growth stage? USD 500+/mo?
├── Keep going, start splitting
├── DB to managed external (Neon / Supabase / PlanetScale)
├── Observability to Datadog / Grafana / Axiom
└── CDN/WAF to Cloudflare

Enterprise?
├── BYOC → Northflank
├── Own datacenter → Kamal 2 + own K8s
└── Compliance → AWS/Azure/GCP direct

References

Read the original: https://www.youngju.dev/blog/culture/2026-05-16-devops-platforms-paas-2026-vercel-fly-render-railway-coolify-dokploy-kamal-deep-dive.en

Comments

No comments yet.

Sign in to leave a comment