Where ComposeGuard stands
ComposeGuard 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.
Built and in test
Fleet inventory and drift Built
Hosts, stacks and containers in one view, with drift against the declared state.
Scanning and ranking Built
Vulnerability scans with SBOM, ranked by known exploitation and exploit probability.
Safe rollout Built
Review, health-gated apply and automatic rollback.
Security foundation Built
Production profile, encrypted state, tamper-evident audit log, signature verification.
Being built now
Every version scanned In progress
All available versions of each image scanned and compared, with a recommendation across all of them.
Version policies per container In progress
From pinned to most secure, recommend-only by default.
Strict production defaults In progress
Unsafe or unsigned images held by default, with a logged, per-image risk acceptance.
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.
Next
Operator single sign-on Planned
Login through your identity provider.
Evidence export Planned
Signed reports for audits.
Runs on FleetGrid Planned
ComposeGuard moves onto the FleetGrid substrate with an encrypted overlay network between hosts.
There is no release date yet. The first release follows the end-to-end proof, not a calendar.