Where FleetMagistrate stands.
FleetMagistrate is in active development and has not been released. The core runs today in a test lab. It will be published once end-to-end tests against real hosts prove every user flow. This is a direction, not a list of dates.
The core loop works end to end.
✍ Signed command channel Built
Signed, replay-protected commands and signed results over mutual TLS.
◎ Desired state and templates Built
Resource kinds, whole-host plans and templates for host groups.
↩ Safe apply Built
Dry run, approval for risky changes, automatic rollback.
🐧 Debian, RHEL, SUSE Built
Three provider families behind one interface.
On the way to the first release.
🌿 Desired state from signed Git In progress
Template revisions from a Git repository, signed by pinned signers.
📊 Reports, export and event hooks In progress
Evidence for audits and integration with other tools.
🐳 Deploys ComposeGuard In progress
ComposeGuard installed and kept current as a FleetMagistrate template.
🧪 End-to-end test suite In progress
Every user flow proven against real binaries on real hosts. This is the gate for the first release.
📦 Signed, reproducible release In progress
Release binaries anyone can verify.
Decided, not started.
👥 Four-eyes for production Planned
A second operator's signature for production changes.
🔑 Operator single sign-on Planned
Login through your identity provider.
🎯 Staged rollouts Planned
Roll changes out ring by ring and stop on the first failure.
📜 Run existing scripts Planned
Run your existing shell, Python or Perl automation over the same signed channel, and migrate it later.