Stars
Forks
Watchers
Developer links
ZaneOps
Shipping a Git repository to a live HTTPS URL takes one dashboard and one server with ZaneOps, an open-source alternative to Heroku, Railway, and Render. Linked GitHub or GitLab repositories build with a Dockerfile, Nixpacks, Railpack, or a static directory builder. Deploys start by hand, on git push, or from a CI webhook. Blue/green releases keep the previous version serving traffic while the new one starts. Each pull request or merge request can open its own preview environment, and the API can create one on demand. Configuration edits queue up as changes that you review before a new version deploys. A pasted docker-compose.yml or a ready-made template (Postgres, Redis, WordPress) deploys a whole stack with blue/green rollouts. Every domain gets a free SSL certificate that renews itself. Wildcard hosts, permanent or temporary redirects, and several services under one domain all work. Runtime logs, request logs, metrics, and health checks gather in the dashboard. Services get CPU and memory limits and volumes, and environment variables import or export as .env files. Viewer, Member, Admin, and Owner roles decide who can see and change what; the free tier allows one workspace and three users. A web terminal opens a shell inside any running deployment, and a second one reaches the server itself over SSH. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.
Benefits
- Heroku-Style Deploys on Your Server
- Connect GitHub or GitLab, choose a repository, and ZaneOps builds and deploys it from a Dockerfile, Nixpacks, Railpack, or static directory, with no code changes or extra CLI tools required.
- Ship Updates Without Downtime
- Blue/green deployments keep the previous version serving traffic while the new one starts, and pull request previews let teammates test a branch in an isolated environment before merging.
- See Inside Every Running Service
- Persistent runtime logs, an HTTP request log, per-service metrics, and health checks gather in one dashboard, and a terminal opens a shell inside any running deployment for debugging.
- Review Changes Before They Deploy
- A Git-like configuration system lets you review and validate every change before deploying a new version, so mistakes are caught before they reach production.
Features
- Docker Swarm Orchestration
- Each service and app maps one-to-one to a Docker Swarm service, which is what lets ZaneOps run rolling blue/green deployments.
- Caddy Proxy and HTTPS
- Caddy is the single entrypoint for all HTTP traffic, providing automatic HTTPS, reverse proxying, wildcard and path-based routing, redirects, and the request data behind the HTTP logs page.
- Dockerfile, Nixpacks, Railpack Builders
- Build from a Dockerfile, Nixpacks, Railpack, or a static directory, or pull a prebuilt image from a Docker registry, with GitHub and GitLab apps connecting your repositories.
- Compose Stacks and Templates
- Deploy multi-container apps from docker-compose.yml as Swarm stacks with blue/green rollouts, using curated templates such as Postgres, Redis, and WordPress or experimental Dokploy template import.
- Fluentd and Loki Logging
- Fluentd collects service logs, Grafana Loki stores and indexes them for search, and per-service metrics and health checks show resource use for every deployment.
- OpenAPI and Webhooks
- A documented OpenAPI REST API with API tokens lets scripts and CI pipelines create preview environments, while deployment webhooks trigger releases from any CI/CD workflow.