Vercel vs Kamal for Solo Developers

Quick Comparison

Vercel Overview

Vercel handles frontend deployment so well that it barely feels like deployment. Connect a repository, push code, and your application appears on the internet with SSL, CDN caching, preview URLs, and edge functions. No server configuration, no Docker files, no SSH keys.

The platform is purpose-built for modern frontend frameworks. Next.js gets the deepest integration (Vercel maintains it), but Astro, Remix, SvelteKit, and static sites all deploy seamlessly. The developer experience, from preview deployments on pull requests to instant rollbacks, is the industry benchmark.

For solo developers, Vercel eliminates an entire category of work. You focus on code. Vercel focuses on getting that code to users worldwide.

Kamal Overview

Kamal (formerly MRSK) is a deployment tool created by the team at 37signals (Basecamp, HEY). It deploys Docker containers to any server via SSH. No Kubernetes. No managed platform. Just Docker containers on Linux servers, orchestrated by a single configuration file.

You define your application in config/deploy.yml, specifying the Docker image, the servers to deploy to, environment variables, and optional accessories like databases and Redis. Run kamal deploy from your laptop, and Kamal builds your Docker image, pushes it to a registry, SSHs into your servers, and rolls out the new version with zero-downtime using Traefik as a reverse proxy.

Kamal's philosophy is that deployment doesn't need to be complicated. You don't need Kubernetes, you don't need a PaaS, and you don't need vendor lock-in. A Linux server, Docker, and SSH are enough. 37signals runs HEY (their email service with millions of users) using Kamal, which validates the approach for production workloads.

I appreciate Kamal's directness. The deploy.yml is readable. The commands are straightforward: kamal deploy, kamal rollback, kamal app logs. There's no abstraction hiding what's happening. Docker containers go on servers via SSH. That's it.

Key Differences

Deployment model. Vercel is a managed platform that handles everything. Kamal is a CLI tool that automates Docker deployment to servers you provide. Vercel owns the infrastructure. Kamal orchestrates your infrastructure. The responsibility shifts from the platform to you.

Infrastructure ownership. With Vercel, you don't own servers. With Kamal, you rent or own the servers and Kamal deploys to them. This means Kamal works with any provider: Hetzner, DigitalOcean, OVH, bare metal, or even a Raspberry Pi. You're never locked into a single hosting provider.

Scope. Vercel deploys frontends and serverless functions. Kamal deploys anything that fits in a Docker container. Rails apps, Django APIs, Go services, background workers, and their databases. If your project has a backend, Kamal can deploy all of it.

Cost structure. Vercel's pricing is platform-based: free tier or $20/month. Kamal is free software. You pay only for your servers. A $4/month Hetzner VPS running Kamal can host your full application. At scale, Kamal's approach is significantly cheaper because you're paying for compute, not a platform fee.

Complexity trade-off. Vercel requires zero infrastructure knowledge. Kamal requires understanding Docker, SSH, basic Linux, and DNS configuration. The initial setup is more involved, but Kamal's design keeps ongoing complexity low. Once configured, kamal deploy is a one-command deployment.

Zero-downtime deploys. Both handle zero-downtime deployments. Vercel uses its platform's deployment infrastructure. Kamal uses Traefik to health-check the new container before switching traffic. Kamal's approach is transparent and configurable. Vercel's is invisible and automatic.

Accessories and databases. Kamal can deploy "accessories" alongside your app: PostgreSQL, Redis, Elasticsearch, and other services. They run as Docker containers on your servers. Vercel doesn't handle databases or persistent services natively.

When to Choose Vercel

• You're deploying frontend applications and want zero ops work
• Preview deployments and Git-based workflows are essential
• You don't want to manage any servers or Docker containers
• Global CDN and edge functions are important for your use case
• The managed experience is worth more to you than infrastructure savings

When to Choose Kamal

• You want to deploy Docker applications to your own servers
• Infrastructure independence and avoiding vendor lock-in matter
• You're comfortable with Docker, SSH, and basic Linux administration
• Cost efficiency at scale is a priority
• Your application needs a backend, database, and other services alongside it

The Verdict

Vercel and Kamal represent opposite philosophies. Vercel says: don't think about infrastructure, we'll handle it. Kamal says: infrastructure isn't that hard, here's a simple tool to manage it yourself.

Vercel's 9/10 reflects that for frontend deployment, the managed experience is worth every penny. Kamal's 7/10 reflects that it's an excellent tool for developers who want deployment control, but the server management overhead is real for solo developers.

If you're deploying a frontend application, use Vercel. If you're deploying a full-stack application and you're comfortable with Docker and SSH, Kamal gives you a clean, simple deployment workflow on any server you choose. The cost savings compared to managed platforms add up quickly, especially on affordable providers like Hetzner or OVH.

For many solo developers, the best approach is Vercel for the frontend (free tier) and Kamal for the backend on a cheap VPS. You get the best of both worlds: managed frontend hosting and infrastructure-independent backend deployment.