// the find
dyrector-io/dyrectorio
dyrector.io is a self-hosted continuous delivery & deployment platform with version management.
dyrector.io is a self-hosted CD platform that manages container deployments across Docker, Kubernetes, and Podman through persistent agents that communicate with a central platform over gRPC. The target audience is small-to-medium teams who want version-tracked deployments without stitching together ArgoCD, Portainer, and a release tracker separately. It runs on Go agents talking to a NestJS backend with a Next.js frontend.
The agent architecture is the right call: two separate Go binaries (dagent for Docker, crane for K8s) connect to the platform over TLS gRPC rather than polling REST, which means agents behind NAT work fine and the protocol is typed end-to-end. The Playwright E2E test suite is more honest than most projects this size — it covers deployment state transitions (mutability, copyability, protection) rather than just happy paths. The fuzz tests on Docker version checking in golang/internal/runtime/container show someone actually thought about malformed input. Version management as a first-class concept is genuinely useful — knowing which version of which container is running where, with changelogs, fills a real gap.
The polyglot stack is a real cost: Go agents, NestJS backend, Next.js frontend, and Prisma migrations are four separate dependency trees you need to understand to debug a production issue at 2am. By their own README admission the platform is still alpha and the SaaS instance may reset its database — that's not a product you hand to a team that needs reliability. The 131 forks against 1841 stars suggests most interest is passive; the contributor base looks thin relative to the surface area. It competes directly with ArgoCD (for K8s) and Portainer (for Docker) without a clearly winning argument over either — 'version management' is a feature those tools are adding, not a sustainable moat.