What it is: A lightweight layer that sits on top of your CI. You connect it to your existing CI, it picks up the artifact after the build finishes and handles everything after that — approvals, environment promotion, rollback, audit record. Built in Go, self-hosted, free.
Why: CI and CD have different functions and should be treated accordingly. CI validates code but it's not built for releasing it. The key idea behind Orbnetes is simple: to separate building from releasing. Most services like GitHub, GitLab, or Jenkins don’t really provide a complete approval, release, and rollback process. What I’m working on takes a different approach. It uses lightweight, cross-platform agents and is focused purely on release control.
Link: https://orbnetes.cloud
Orbnetes is free, give it a try and let me know what you think!
Yaroslav Snisar
Building and launching IT projects from zero. Creator of Orbnetes
Shared more about it here: techface.hashnode.dev/ci-vs-cd-how-to-build-a-res…