compare
Piku vs Tsuru
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Piku | Tsuru |
|---|---|---|
| Language | Python | Go |
| Licence | MIT | BSD-3-Clause |
| Stars | 6.6k | 5.3k |
| Latest | v1.0.0 | v1.32.0 |
| Last push | 2026-09-04 | 2026-09-29 |
| Release cadence | too few releases | about 14 days between releases |
| Active contributors | 4 commit authors on the default branch in the last 90 days | 4 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace Heroku. Alternatives to Heroku →
PartialPikuGit push deploys with a Procfile and an ENV file on a single server, built per language without buildpacks or managed databases.
Full replacementTsuruDeploys apps from git or images onto Kubernetes, with service add-ons and teams.
Tsuru
- v1.32.02026-09-03cc66f965fd02d85ffa30b5f76517db8988411984 fix(lint): move new-from-merge-base into .golangci.yml so make lint matches CI…
- 1.31.22026-09-03bc516618c09560e06f73e7f5f4932dac62bd2b6e Fix/cluster storage breaking kubeconfig (#2911)
- 1.31.12026-08-206ddeb3c5e58a6da703230f5c917386392656e12d fix: team info should not return all app data (#2902)
- 1.31.02026-07-306a72ef9b4de3b195eba830eab348dc796e53ba76 Feature/service fine grained permissions (#2878)
- 1.30.22026-07-16789d5bf0ce7d747c1ebea84ef6d24a17ecdb9c56 Add cluster on service info endpoint
Piku
✓ signed The latest release, v1.0.0, carries a signature GitHub verified.
Loading the security report
Tsuru
✓ signed The latest release, v1.32.0, carries a signature GitHub verified.
Loading the security report