RedFlag is a self-hosted machine and update-management system. The Agent observes a host; the native Desktop presents that machine; the web dashboard brings a fleet into view. The privileged Helper executes the narrow operations its signed authority permits.
One machine is enough
A standalone machine is a legitimate deployment. Joining a fleet changes where authority is placed, rather than unlocking a paid edition. The system keeps process, connection, package, service, container and update evidence attached to the machine that reported it.
Observe, authorize, remember
Updates pass through human approval and recorded policy. On APT and DNF, dependency resolution precedes the mutation path. Signed capabilities bind an operation to a host and the artifact hashes that resolved. The Helper checks the envelope before acting through fixed arguments.
Failures and overrides belong in the history. An operator should be able to examine why an update stopped, what was overridden and what the machine actually reported.
Availability and maturity
Public release availability is collected from the Forge and its manifest. A published prerelease does not make the system production-proven. The project's adoption and exercised paths remain modest, and its named security gaps remain part of the documentation.
What remains open
- Complete transitive dependency hashing and helper network isolation remain unfinished.
- Capability-helper coverage differs from the signed-command paths used by other package managers.
- The system does not protect a host from its own administrator.
- Public binaries are prerelease software; broad production acceptance is not established.