Search tldr

Disco — Self-hosted PaaS for teams outgrowing Render & Heroku

Disco provides a self-hosted, open-source Heroku alternative with git-push deployments, zero-downtime releases, and automatic SSL. It targets teams that need managed-PaaS ergonomics without vendor markup, lock-in, or surrendering data control.

Share

Disco — Self-hosted PaaS for teams outgrowing Render & Heroku

Author: Disco | Published: Unknown | Generated: 2025-10-22 | Domain: disco.cloud Tags: ‘#selfhosting’ ‘#paas’ ‘#devops’ ‘#docker’ ‘#heroku’ ‘#deployment’


TLDR

Disco is an open-source, self-hosted PaaS designed for teams moving beyond managed platforms such as Render and Heroku. It installs a Docker Swarm-based runtime with Caddy-managed SSL, GitHub-triggered deployments, blue/green releases, and rollbacks on infrastructure the customer owns. Disco claims teams spending at least $1,000 per month on managed PaaS can often reduce costs by 70–95%, while keeping application traffic and data outside Disco’s request path.

Key Takeaways

  • PaaS workflow on owned infrastructure: Disco offers git push deployments, deployment previews, logs, scaling, automatic SSL, and zero-downtime releases while running on providers including Hetzner, DigitalOcean, AWS, GCP, and bare metal.
  • Control plane is separated from application traffic: Disco states that its control plane does not sit in the production request path; application traffic and data remain on the customer’s servers.
  • Built on Docker Swarm and Caddy: A one-command installation on a fresh Ubuntu 24.04 LTS server sets up Docker Swarm, Caddy SSL, and the Disco daemon.
  • Cost-reduction positioning: The site estimates that organizations already spending $1,000+/month on managed PaaS may cut costs by 70–95%, subject to workload, region, and redundancy requirements.
  • Reported migration result: Idealist.org reportedly replaced a $3,000/month Heroku bill with a $55/month server using Disco.

Images & Media

Keep reading