dyrector.io is an open-source, self-hosted continuous delivery platform that ships versioned container releases to Docker hosts and Kubernetes clusters from one dashboard. Teams compose container images into tracked versions and roll each version out per node with configurable strategies, preview, audit logs, and rollback. It serves platform and DevOps teams that want release discipline without surrendering infrastructure control.[1][2][3]
Quick verdict
Platform teams shipping versioned container releases across Docker and Kubernetes benefit most from dyrector.io. Its versioned rollouts with per-node strategies, audit logs, and API automation give release discipline to self-hosted estates. Teams needing managed operations, SSO, or a production SaaS should look elsewhere until the alpha and enterprise story mature. If you can operate Docker Compose infrastructure, self-host dyrector.io free; otherwise shortlist a managed delivery platform.[1][2][3]
Key features
Versioned container releases Teams build projects from container images and compose changes into versions with release notes and changelogs, so every rollout carries a reviewable record of what changed.[1][2]
Configurable rollout strategies Each version rolls out per node with rolling, consistent, upgrading, redeploy, or restart strategies, and operators can preview changes before deploying.[1]
Docker and Kubernetes targets Lightweight agents run on the targets: dagent on Docker hosts and crane on Kubernetes clusters, letting one platform serve both estates.[1][2]
Node lifecycle management Nodes join with generated install scripts and stay manageable from the dashboard with disable, reassign, redeploy, restart, and delete operations.[1]
Teams, roles, and audit logs Team management with scoped roles plus audit logs gives multi-team setups access control and a traceable deployment history.[1]
REST API with scoped tokens A REST API with scoped tokens automates teams, projects, versions, deployments, and notifications for pipeline-driven workflows.[1]
Broad registry and runtime support Private and public registries are supported, including GitHub, Docker Hub, Google, and GitLab sources, with Podman support for teams outside the Docker runtime.[1][2]
Delivery control dashboard A web dashboard centralizes builds, versions, deployments, and node monitoring with inbox notifications, replacing scattered manual release steps.[1][2]
Who will love it
Platform teams standardizing releases Teams running versioned releases across mixed Docker and Kubernetes estates gain the most, because versions, strategies, and audit trails directly serve that standardization need.[1][2]
Budget-conscious self-hosters Organizations able to operate Docker Compose infrastructure get a full delivery platform free and unlimited, which suits tight budgets with ops capacity.[1][2]
Automation-driven delivery teams Teams that drive releases from CI pipelines benefit from the REST API and scoped tokens, which fit scripted version and deployment workflows.[1]
Who should avoid it
Docker-first platform installation The platform itself installs via Docker Compose, and Kubernetes support for hosting it is still in progress, so Kubernetes-only shops face an extra runtime to adopt.[1]
No documented SSO or enterprise tier The docs confirm Ory Kratos authentication but no SSO offering and no enterprise support tier, so regulated or large organizations should verify these points before committing.[1]
Hosted SaaS still in alpha The hosted option is an alpha with published usage limits and support through community Discord, so production use today favors self-hosting.[1][2]
Deployment and compatibility
Self-hosting requirements Self-management needs Docker or Podman with Compose; installation follows generated scripts and stays free and unlimited.[1][2]
Workload target compatibility Workload nodes run Docker with dagent or Kubernetes with crane, covering the two dominant container runtimes from one control plane.[1][2]
SaaS alpha terms The alpha SaaS bills per developer and per deployment with trial, node, deployment, and storage caps; teams exceeding those caps should self-host or wait for paid plans.[1]
Questions worth asking
What is the best dyrector.io alternative for non-technical users?
Is dyrector.io really no-code?
How much does dyrector.io cost per month?
Self-hosting dyrector.io is free and unlimited. The hosted SaaS alpha charges USD 20 per developer per month plus USD 2 per deployment per month, with detailed caps published in the pricing table. Pricing was checked in October 2026 and the SaaS remains in alpha.[1]
Sources and editorial review
Source research. Reviewed on October 9, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- dyrector.io homepage
official · Observed October 9, 2026
Official homepage: positioning, target users, feature overview, self-hosted and SaaS editions.
- dyrector.io documentation
official · Observed October 9, 2026
Official documentation: strategies, agents, nodes, teams, audit, API, registries, self-management.
- dyrector.io pricing
official · Observed October 9, 2026
Official pricing: SaaS alpha rates, usage caps, self-hosted free terms, support channel.
- dyrector-io/dyrectorio on GitHub
official · Observed October 9, 2026
Official repository: open-source identity, agent architecture, dashboard, community activity.
- dyrector.io use cases
official · Observed October 9, 2026
Official use cases: migration, multi-environment releases, restricted networks, multi-cloud.
Compared with these products
No explicit proprietary baseline is recorded.