basecamp/kamal

Deploy web apps anywhere.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 17 minutes ago
Added to GitGenius on September 4th, 2026
Created on January 7th, 2023
Open Issues & Pull Requests: 149 (+0)
GitHub issues: Enabled
Number of forks: 750
Total Stargazers: 14,564 (+0)
Total Subscribers: 101 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 62
New in 7 days: 0
Closed in 7 days: 11
Avg open age: 386 days
Stale 30+ days: 55
Stale 90+ days: 44

Recent activity

Opened in 7 days: 0
Closed in 7 days: 11
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Builder (4)
  • Accessories (3)
  • Dockerized (3)
  • Kamal v1 (1)

Detailed Description

Kamal is a deployment tool that enables zero-downtime deployments of containerized web applications to any infrastructure, from bare metal servers to cloud virtual machines.

Kamal solves the problem of deploying applications across heterogeneous infrastructure without service interruption. It uses kamal-proxy to seamlessly redirect traffic between containers during deployments, allowing requests to switch targets without downtime. The tool orchestrates deployments across multiple servers using SSHKit to execute commands remotely, and requires only Docker and SSH access to target machines, making it agnostic to the underlying infrastructure provider.

Kamal suits teams deploying containerized applications who want to avoid vendor lock-in and maintain control over their infrastructure. While originally built for Rails applications, it works with any web app that can be containerized with Docker. The tool is particularly valuable for organizations running on bare metal or using multiple cloud providers, as it treats all deployment targets uniformly through SSH rather than requiring Kubernetes or cloud-specific APIs.

The project maintains active engagement with its documentation, directing contributors to a separate repository dedicated to improving guides and references. Development activity shows consistent attention to the core deployment workflow and infrastructure compatibility.