Roadmap
Where hostcd is and where it is going. Dates are directional, not commitments — this is a pre-1.0 product and priorities shift with what pilots need. See the changelog for what has actually shipped.
Now — shipped and supported
- Core reconcile loop: git-driven drift detection, preview, sync, rollback and an actor-attributed audit trail for Linux hosts, with an outbound-only pull agent (nothing listens on a managed host).
- Resource kinds: file (templated), package, service, directory, symlink, mount, sysctl, cron, user, group, apt/yum repositories, ufw rules.
- Package managers: apt / dnf / yum / zypper (Linux); choco / winget on Windows (late beta). Services via systemd and the Windows SCM.
- Supply chain: signed releases (keyless cosign),
SHA256SUMS, SBOM; a verified, pinned install path; a public, independentverify-releasecheck. - Team (licensed): approval gates, outbound notifications, audit export (SIEM).
- Enterprise (licensed): everything in Team plus SSO (SAML 2.0 / OIDC + SLO), SCIM, high availability (Postgres multi-replica), Vault Transit sealing.
- Licensing: offline token, no phone-home; Community core under BSL 1.1; graceful downgrade on lapse (approval gates stay fail-closed).
Next — in progress / near term
- External validation. A first Founding Pilot and an independent, measurable case study (drift caught, auto-repairs, rollback exercised, time saved). This is the current bottleneck — the engineering is ahead of the external proof.
- High availability → GA. Postgres-backed multi-replica HA (active-active reads, a single elected writer) is an Enterprise preview today. To remove "preview": a 24–72 h two-node soak, a real restore + standby re-join drill, and documented RTO/RPO.
- Windows → beyond late beta. Prove the mixed-version upgrade path and the Windows drift / self-heal / rollback story on a live fleet.
- Trust surface. Keep the closed-source core but widen transparency — a public roadmap (this page), security policy & threat model, changelog, and a feedback channel.
- Harden-by-default guidance. Make signed-commit verification a documented default for production; surface the
/metricstoken and hardening checklist earlier.
Later — under consideration
- HA out of preview with a documented operations runbook and failover SLOs.
- Broader OS coverage and a first-class Windows GA.
- More notification / SIEM integrations and policy controls on the approval gate.
- The BSL 1.1 core converts to Apache-2.0 on 2030-10-26 (the license change date) regardless of the above.
Not planned
- Agent-side fencing tokens (a monotonic leadership term pushed to agents). Evaluated and rejected for this architecture: agents are pull-only and every mutating request is already forwarded to the single elected leader, with the store's CAS version as the backstop — an agent-side term would be the wrong layer. See the threat model for the HA trust model.
Have a need that should be on this list? Tell us. What has shipped is in the changelog.