I kept running into the same problem. CI tools are great at building code, but not at releasing it. Approvals feel bolted on, rollback is improvised, and when something breaks, nobody can answer who deployed what or when.
So I built Orbnetes — a self-hosted release orchestration layer that sits on top of your existing CI and handles everything after the build finishes.
How it works
You connect it to GitHub, GitLab, or your own storage. It picks up the artifact, validates it, and manages the release from there — approvals, environment promotion, rollback, full audit record.
Deployments run through lightweight cross-platform agents (~2MB) inside your own infrastructure. Deployment logic lives in YAML blueprints with a syntax close to GitHub Actions — familiar but scoped purely to release control.
Every release gets a structured record. If something fails, rollback executes against the already-validated artifact not a pipeline re-run.
Key features
- Cross-platform agents for Linux, macOS, Windows
- YAML blueprints with approval gates and rollback policies
- Full audit trail independent of your CI platform
- Self-hosted, free, no Kubernetes required
Orbnetes is free to try. Would love to hear your feedback!