Netlify vs Kamal for Solo Developers

Quick Comparison

Netlify Overview

Netlify is the standard for deploying static sites and JAMstack applications. Push code to Git, Netlify builds it, puts it on a CDN, and gives you a URL. Preview deploys for branches, form handling, serverless functions, and free SSL. It's a complete frontend hosting solution with almost no configuration required.

I reach for Netlify whenever I need to deploy something static. The workflow is fast, the free tier covers most solo projects, and I don't have to think about infrastructure. That last part is the key. Netlify handles CDN routing, SSL certificates, build caching, and edge delivery without me touching anything.

The scope is narrow by design. Netlify hosts static content and runs short-lived serverless functions. It's not trying to be a full application platform, and that's fine for the projects it targets.

Kamal Overview

Kamal is a deployment tool built by the Basecamp team (the Rails folks). It deploys Docker containers to any server you own using SSH. No Kubernetes, no managed platform, no vendor lock-in. You define your services in a YAML config, run kamal deploy, and your Docker images are pulled and started on your VPS with zero-downtime rolling deploys.

Kamal 2 made things significantly simpler than the original version. It uses kamal-proxy (a lightweight reverse proxy) instead of Traefik, handles SSL automatically via Let's Encrypt, and supports deploying multiple services and accessories like databases and Redis alongside your main app.

I tried Kamal for a Rails project on a Hetzner VPS and the experience was clean. The deploy config is a single YAML file. Running kamal setup provisions everything. Running kamal deploy builds your Docker image, pushes it to a registry, pulls it on the server, and swaps traffic with zero downtime. It's what Capistrano was for the Docker era.

Key Differences

Platform vs tool. Netlify is a hosted platform. You deploy to their infrastructure. Kamal is a deployment tool. You use it to deploy to your own server. Netlify manages everything. Kamal automates deployment but you still own and manage the server.

What they deploy. Netlify deploys static files and serverless functions. Kamal deploys Docker containers. Any application that runs in Docker can be deployed with Kamal. Rails, Django, Node, Go, anything. The scope of what Kamal can handle is much broader.

Infrastructure ownership. With Netlify, your code runs on Netlify's infrastructure. With Kamal, your code runs on servers you control. This means Kamal gives you more control and better economics at scale, but also more responsibility.

Developer experience. Netlify's experience is push-and-forget. Kamal's experience is more hands-on. You write a deploy config, run CLI commands, and manage your server. Kamal simplifies deployment significantly compared to raw Docker Compose or Kubernetes, but it's still more involved than Netlify's fully managed approach.

Cost comparison. Netlify's free plan costs nothing within its 300 monthly credits. Kamal is free but requires a VPS, and a Hetzner CX22 lists at EUR 3.79/month. For a single low-traffic static site, Netlify's free credits are clearly cheaper. For a full application stack, Kamal on a cheap VPS beats the monthly cost of managed platforms like Railway or Render. See the worked math below.

Zero-downtime deploys. Netlify handles this with atomic deploys for static content. Kamal handles this with rolling container deploys and health checks. Both achieve zero-downtime, but through different mechanisms.

Accessories and services. Kamal can deploy "accessories" like Postgres, Redis, and background workers alongside your main app, all from the same config file. Netlify has no concept of running additional services.

By the Numbers (2026)

Here is what each tool actually looks like in figures I pulled this week, not from memory.

Netlify (credit-based plans). Netlify moved every account onto a shared credit model. You no longer get separate bandwidth and build-minute buckets. Everything draws from one monthly credit pool.

• Free plan: $0/month, 300 credits/month as a hard limit.
• Personal plan: $9/month, 1,000 credits/month.
• Pro plan: $20/month, 3,000 credits/month, with unlimited team member seats, 3 or more concurrent builds, and 30-day analytics.
• Credit rates as of the April 14, 2026 update: each production deployment costs 15 credits, web bandwidth costs 20 credits per GB, compute and functions cost 10 credits per GB-hour, and web requests cost 2 credits per 10,000 requests.
• Deploy previews, branch deploys, failed deploys, and form submissions are not metered. Form submissions became free across all credit plans on April 14, 2026.

Kamal. Kamal is the open-source side of the comparison, so the numbers are about the project rather than a bill.

• Latest version: v2.11.0, released March 18, 2026.
• License: MIT, with 14,249 stars and 715 forks on GitHub.
• Total RubyGems downloads: 18.9 million across all versions.
• The bundled router, kamal-proxy, is its own MIT project with 1,073 stars and replaces the Traefik dependency that Kamal 1 used.
• Production proof: Kamal deploys HEY.com and Basecamp, which is the strongest "this is not a toy" signal a deployment tool can carry.

Real Cost at Solo-Dev Scale

The two tools bill in completely different ways, so a fair comparison needs a fixed workload. Assume a realistic small full-stack app for one developer: roughly 30 production deploys a month, about 50 GB of bandwidth served, and a small backend that stays warm.

On Netlify (credit-based math). Using the April 2026 rates, 30 deploys cost 30 times 15, which is 450 credits. 50 GB of bandwidth costs 50 times 20, which is 1,000 credits. That alone is 1,450 credits before any compute, which already blows past the Free plan's 300-credit hard cap and past the Personal plan's 1,000 credits. You would land on the Pro plan at $20/month for 3,000 credits, with compute and web requests eating into the remaining headroom. If your bandwidth or deploy count grows, you either buy more credits or watch the pool drain faster. For a genuinely tiny static site that deploys a few times a month and serves a few GB, the Free 300 credits can still be enough, so the honest answer is "free until it isn't, then $20."

On Kamal (server math). Kamal itself is free, so the bill is whatever VPS you point it at. A Hetzner CX22 (2 vCPU, 4 GB RAM, 40 GB disk, 20 TB included traffic) lists at EUR 3.79/month on Hetzner's cost-optimized page, with the April 2026 price adjustment in effect (check current pricing for your exact region and currency). That single box hosts the app, a Postgres accessory, and a Redis accessory from one config file, and its 20 TB of included traffic dwarfs the 50 GB in this workload. So the same full-stack app runs for under five dollars a month, with deploy count and bandwidth being effectively free until you outgrow the hardware.

The takeaway is not "Kamal is cheaper." It is that the two pricing models bend in opposite directions. Netlify's cost rises with usage, which is fine when usage is near zero and painful when it is not. Kamal's cost is a flat server fee plus the time you spend owning that server.

When to Choose Netlify

• Your project is a static site, blog, or client-side application
• You want zero infrastructure to manage
• Fast, free deploys with preview URLs matter to you
• You don't want to own or maintain a server
• Simplicity and speed of deployment are your top priorities

When to Choose Kamal

• You're deploying a full-stack application with a backend
• You want Docker-based zero-downtime deploys to your own VPS
• You prefer owning your infrastructure over renting platform time
• You need to deploy databases and background workers alongside your app
• You're already comfortable with Docker and want a clean deployment workflow

The Verdict

Netlify and Kamal solve completely different problems. Netlify is a hosting platform for static content. Kamal is a deployment tool for Docker applications on your own servers. Comparing them directly is like comparing a CDN with a deployment script.

If you're deploying a frontend or static site, use Netlify. Don't set up a VPS and configure Kamal to serve HTML files. That's unnecessary work for a solved problem.

If you're deploying a backend application and want the simplicity of a managed platform without the managed platform price, Kamal is worth learning. It turns a roughly four-dollar-a-month Hetzner CX22 into a production deployment target with zero-downtime deploys, SSL, and multi-service support. The initial setup takes more time than clicking "Deploy" on Railway, but the ongoing cost savings and infrastructure control are significant.

For many solo developers, the practical setup is Netlify for the frontend and Kamal for deploying the backend to a VPS. Simple frontend hosting paired with affordable, controlled backend deployment.

Sources

• Netlify Pricing and Plans (checked 2026-05-29): Free $0/300 credits, Personal $9/1,000 credits, Pro $20/3,000 credits with unlimited seats and 3+ concurrent builds.
• Netlify Docs: Credit-based pricing plans (checked 2026-05-29): production deploy 15 credits, web bandwidth 20 credits/GB, compute 10 credits/GB-hour, web requests 2 credits/10,000, deploy previews and failed deploys not metered.
• Netlify Changelog: Pricing updates April 2026 (checked 2026-05-29): April 14, 2026 rate changes and free form submissions across credit plans.
• Kamal GitHub repository (checked 2026-05-29 via api.github.com): 14,249 stars, 715 forks, MIT license.
• Kamal v2.11.0 release (checked 2026-05-29 via api.github.com): latest release, published March 18, 2026.
• Kamal on RubyGems (checked 2026-05-29 via rubygems.org API): version 2.11.0, 18.9M total downloads.
• kamal-proxy GitHub repository (checked 2026-05-29 via api.github.com): 1,073 stars, the bundled router that replaced Traefik.
• Kamal documentation (checked 2026-05-29): deploys HEY.com and Basecamp, automatic HTTPS via Let's Encrypt, accessory services.
• Hetzner Cloud cost-optimized plans (checked 2026-05-29): CX22 with 2 vCPU, 4 GB RAM, 40 GB disk, 20 TB traffic at EUR 3.79/month, April 2026 price adjustment in effect.