A self-hosted, Docker-powered mini-Heroku that deploys and manages web apps on your own server from a git push.
- Stars
- 1,391
- Forks
- 75
- Open issues
- 17
- Last commit
- 4 days ago
What is it?
ZaneOps is a self-hosted platform for deploying static sites, web apps, databases, background workers and other services on your own server. It is aimed at developers who want a Heroku, Railway or Render style workflow without handing their infrastructure to a hosted provider. The README gives examples such as Supabase, WordPress and Ghost as things you can run on it.
The platform uses Docker Swarm for scheduling and scaling containers, and Caddy as the reverse proxy that routes HTTP traffic. Installation is a single shell script that sets up the stack on a server.
The web interface includes a dashboard, project detail pages, HTTP request logs and runtime logs for each service.
Key features
- 01Deploys static sites, web apps, databases, services and workers on your own server.
- 02Uses Docker Swarm to run and scale containers.
- 03Uses Caddy as the reverse proxy for HTTP routing.
- 04Provides HTTP request logs and runtime logs per service.
- 05Installs with a single shell command.
Use cases
- Hosting your own web apps and APIs as an alternative to Heroku or Render.
- Running self-hosted services such as WordPress or Ghost on a private server.
- Deploying a small team's apps without paying for a managed PaaS.
Quick start
- 1
Run the official install script from the README (it pipes a remote script into bash, so review it first)
Things to know
- The license is not clearly identified in the project metadata, so check the repository's license terms before use.
- It is self-hosted and built on Docker Swarm and Caddy, so you need to run and maintain your own server infrastructure.
In collections
Topics
FAQ
- What is zane-ops?
- A self-hosted PaaS for deploying web apps, databases, static sites and services, built on Docker Swarm and Caddy. ZaneOps is a self-hosted platform for deploying static sites, web apps, databases, background workers and other services on your own server. It is aimed at developers who want a Heroku, Railway or Render style workflow without handing their infrastructure to a hosted provider. The README gives examples such as Supabase, WordPress and Ghost as things you can run on it.
- Is zane-ops free to use? What license does it have?
- zane-ops is open source under the Other license. Check the license terms before using it in commercial products.
- Is zane-ops still maintained?
- Actively maintained. The last commit to zane-ops was on Nov 3, 2026.
- What can I use zane-ops for?
- Hosting your own web apps and APIs as an alternative to Heroku or Render. Running self-hosted services such as WordPress or Ghost on a private server. Deploying a small team's apps without paying for a managed PaaS.
- How do I install zane-ops?
- Run the official install script from the README (it pipes a remote script into bash, so review it first)
- Where can I get zane-ops?
- The source code and installation instructions are on GitHub: https://github.com/zane-ops/zane-ops
Summary generated by AI from the project's README. GitHub stats refresh daily.
Related projects
Self-hostable platform to deploy apps, databases and one-click services to your own servers over SSH, an alternative to Heroku, Netlify and Vercel.
A tiny self-hosted PaaS that deploys apps to your own servers with git push, using nginx and uWSGI.
A self-hosted, Heroku-style PaaS that deploys git-pushed apps to your own Kubernetes cluster through a web UI.
Self-hosted PaaS that deploys apps and databases on your own server using Docker, Nginx and Let's Encrypt, with a web GUI and CLI.
Self-hostable PaaS for deploying apps and databases on your own VPS, as an alternative to Vercel, Netlify and Heroku.