# Alternatives to Tsuru

Tsuru is an open-source, extensible PaaS originally built and open-sourced by Globo.com, offering CLI source-code deploys, buildpack-based builds, and a pluggable router/backend architecture on top of Docker and Kubernetes. It is used in production by companies like Globo, Jumia, and Stone for internal developer platforms.

Tsuru ranks #9 of 11 in Self-hosted PaaS, with an Alt Score of 46. It is licensed under BSD-3-Clause, free from Free and available on Linux, macOS and Windows. 8 of 10 checklist rows are verified against a public source.

Source: https://altcatalog.com/alternatives/tsuru/
Category: Self-hosted PaaS

## Overview

- **Who it's for**: Platform/infrastructure teams who want to run their own self-hosted, Heroku-like PaaS on top of Kubernetes, and the application developers inside those organizations who just want to push code and get a running app without managing servers or writing Kubernetes manifests themselves.
- **What you get**: A CLI-driven PaaS that deploys apps onto one or more Kubernetes clusters using a curated set of language platforms (Go, Python, Java, Node.js, PHP, Ruby, or a static/Dockerfile build), plus app quotas, automated SSL/TLS certificate issuance, multi-cluster/multi-cloud placement via pools, and provisioned add-on services (databases, caches, proxies) that bind directly to an app's environment variables.
- **How it works**: A central Tsuru API server (backed by MongoDB) receives commands from the tsuru CLI (or Terraform), builds container images via BuildKit and a Deploy Agent, pushes them to a container registry, and schedules the resulting app units onto a target Kubernetes cluster; a separate Router API component wires up networking/routing for each app once its units pass health checks.

## Profile

- **License**: BSD-3-Clause (verified 2026-07-30)
- **Pricing model**: Free (verified 2026-07-30)
- **Starts at**: Free (verified 2026-07-30)
- **Platforms**: Linux, macOS, Windows
- **Status**: active (verified 2026-07-30)

## Ranked alternatives

| # | App | Alt Score | Licence | Platforms |
|---|-----|-----------|---------|-----------|
| 1 | [SwiftWave](https://altcatalog.com/alternatives/swiftwave.md) | 91 | Apache-2.0 | Linux, Web |
| 2 | [CapRover](https://altcatalog.com/alternatives/caprover.md) | 86 | Apache-2.0 | Web |
| 3 | [Coolify](https://altcatalog.com/alternatives/coolify.md) | 86 | Apache-2.0 | Web |
| 4 | [Dokploy](https://altcatalog.com/alternatives/dokploy.md) | 86 | Apache-2.0 | Web |
| 5 | [Easypanel](https://altcatalog.com/alternatives/easypanel.md) | 86 | Proprietary | Linux |
| 6 | [Kubero](https://altcatalog.com/alternatives/kubero.md) | 73 | GPL-3.0 | Windows, macOS, Linux, Web |
| 7 | [Cloud Foundry](https://altcatalog.com/alternatives/cloud-foundry.md) | 60 | Apache-2.0 | Windows, macOS, Linux |
| 8 | [Dokku](https://altcatalog.com/alternatives/dokku.md) | 46 | MIT | Linux |
| 9 | [Kamal](https://altcatalog.com/alternatives/kamal.md) | 42 | MIT | Linux |
| 10 | [Piku](https://altcatalog.com/alternatives/piku.md) | 32 | MIT | Linux |

Alt Score = Verified coverage (90%) + Visibility (10%). See https://altcatalog.com/how-alt-score-works/

## Feature comparison

Legend: Yes / No / Partial / ? (not verified).

| Self-hosted PaaS checklist | Tsuru | SwiftWave | CapRover | Coolify | Dokploy | Easypanel |
|---|---|---|---|---|---|---|
| Pricing model | Free | Free | Free | OSS + paid hosting | OSS + paid hosting | Freemium |
| Starts at | Free | Free | Free | Free | $4.50/mo | $10.9/mo |
| License | BSD-3-Clause | Apache-2.0 | Apache-2.0 | Apache-2.0 | Apache-2.0 | Proprietary |
| Platforms | Linux, macOS, Windows | Linux, Web | Web | Web | Web | Linux |
| One-click app catalog | No | Yes | Yes | Yes | ? | Yes |
| Git push deploys | No | Yes | Yes | Yes | Yes | Yes |
| Docker Compose support | No | Partial | Partial | Yes | Yes | Yes |
| Automatic SSL | Yes | Yes | Yes | Yes | Partial | Yes |
| Backups built in | ? | Yes | Partial | Yes | Yes | Yes |
| Multi-server support | Yes | Yes | Yes | Yes | Yes | Partial |
| Web UI quality | No | Yes | Yes | Yes | Yes | Yes |
| Resource usage | Yes | Yes | Yes | Partial | Yes | Yes |
| Database provisioning | Yes | Yes | Yes | Yes | Yes | Yes |
| Zero-downtime deploys | ? | Partial | Partial | ? | Yes | ? |

## Sources

Sources for Tsuru. Each alternative is sourced on its own page.

- **License**: BSD-3-Clause — <https://raw.githubusercontent.com/tsuru/tsuru/main/LICENSE> (verified 2026-07-30)
  - Note: GitHub's license detector also classifies this as 'BSD 3-Clause New or Revised License'; docs.tsuru.io/getting_started/overview/ separately states the project is released under the '3rd-Clause BSD lic
  - Quote: “Copyright (c) 2015, tsuru authors. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:”
- **Pricing model**: Free — <https://docs.tsuru.io/getting_started/overview/> (verified 2026-07-30)
  - Note: Self-hosted OSS PaaS software with no hosted/commercial tier. tsuru.io's own sitemap.xml lists only the homepage and /media/ — no pricing page exists.
  - Quote: “Tsuru projects are open-source software released under the 3rd-Clause BSD license. Furthermore, all external components/dependencies also are maintained by the open-source community (each one released”
- **Starts at**: Free — <https://docs.tsuru.io/getting_started/overview/> (verified 2026-07-30)
  - Note: No paid tier found; you self-host it on your own infrastructure/Kubernetes cluster at no license cost.
  - Quote: “Tsuru projects are open-source software released under the 3rd-Clause BSD license.”
- **Platforms**: Linux, macOS, Windows — <https://docs.tsuru.io/user_guides/install_client/> (verified 2026-07-30)
  - Note: Refers to the tsuru CLI client's supported OSes (also distributed via Docker container image). The Tsuru server/API itself is deployed as containers on a Kubernetes cluster, not installed on end-user
  - Quote: “Pre-built binaries. Linux ... MacOS ... Windows. If you are using Windows Subsystem for Linux (WSL), you can install Tsuru by following the same steps as would for Linux. However, if you are not using”
- **Status**: active — <https://github.com/tsuru/tsuru/commits/main.atom> (verified 2026-07-30)
  - Note: LOUD FLAG FOR REVIEWER: despite tsuru's Globo.com origins and long history, the core tsuru/tsuru repo is NOT dormant — most recent commit to main landed 2026-07-29 (one day before this research), and
  - Quote: “Recent Commits to tsuru:main ... Feature/service fine grained permissions (#2878) ... <updated>2026-07-29T13:57:36Z</updated>”
- **One-click app catalog**: No — <https://docs.tsuru.io/admin_guides/managing_platforms/> (verified 2026-07-30)
  - Note: Tsuru's catalog (Go, Python, Java, NodeJS, PHP, Ruby, Static) is a set of language/framework runtimes you deploy your own code onto, not a one-click catalog of pre-built applications (e.g. WordPress,
  - Quote: “A platform is a well defined pack with installed dependencies for a language or framework that a group of applications will need.”
- **Git push deploys**: No — <https://docs.tsuru.io/tsuru_client/tsuru_app_deploy/> (verified 2026-07-30)
  - Note: Current documented deploy methods are CLI file upload (tsuru app deploy), container image, or Dockerfile build — no git-remote-push deploy mechanism appears anywhere in current docs, FAQ, or the app-d
  - Quote: “Deploy the source code and/or configurations to the application on Tsuru. ... To deploy using app's platform build process (just sending source code and/or configurations): Uploading all files within ”
- **Docker Compose support**: No — <https://docs.tsuru.io/contributing/docker-compose/> (verified 2026-07-30)
  - Note: The only official docker-compose usage documented is for standing up a local dev environment to build/test Tsuru itself (contributing guide) — it is not a way to deploy end-user apps. App deploys only
  - Quote: “Running development environment with Docker Compose. This guide will provide step-by-step instructions on how to set up and run a minimal Tsuru environment for building and testing Tsuru on your local”
- **Automatic SSL**: Yes — <https://docs.tsuru.io/tsuru_client/tsuru_certificate_issuer/> (verified 2026-07-30)
  - Quote: “Issuer is used to automate the issuance of SSL/TLS certificates.”
- **Multi-server support**: Yes — <https://docs.tsuru.io/getting_started/overview/> (verified 2026-07-30)
  - Note: Corroborated by the admin guide: 'Cluster is used by provisioner to deploy applications in a specific kubernetes installation' — Tsuru manages apps across multiple clusters/nodes (https://docs.tsuru.i
  - Quote: “Multi-cloud support. Tsuru supports compatibility with multiple cloud providers, providing developers the freedom to choose their preferred infrastructure. Seamlessly deploy applications across differ”
- **Web UI quality**: No — <https://github.com/tsuru/tsuru-dashboard> (verified 2026-07-30)
  - Note: Tsuru's official web dashboard (tsuru-dashboard) and its companion tsuru-autoscale-dashboard are both archived/unmaintained on GitHub. Tsuru today is CLI/API-first with no actively maintained web UI —
  - Quote: “This repository was archived by the owner on Sep 12, 2024. It is now read-only.”
- **Resource usage**: Yes — <https://docs.tsuru.io/tsuru_client/tsuru_app_quota/> (verified 2026-07-30)
  - Quote: “tsuru app quota view - Displays the current usage and limit of the given app.”
- **Database provisioning**: Yes — <https://docs.tsuru.io/tsuru_client/tsuru_service_instance/> (verified 2026-07-30)
  - Note: Corroborated by the main repo README: 'Back apps with add-on resources such as SQL and NoSQL databases, including memcached, Redis, and many others' (https://raw.githubusercontent.com/tsuru/tsuru/main
  - Quote: “Manage provisioned resources (like a database or proxy) that can be linked to an application.”

---
Ranked by verified data, never by who paid. https://altcatalog.com/trust/