RedFlag is a machine knowledge and operations system with a self-hosted fleet surface. The Endpoint observes a host; the native Desktop presents that machine; the web dashboard brings a fleet into view. The privileged Helper verifies and executes bounded operations.
One machine is enough
A standalone machine is a legitimate deployment. The system keeps process, connection, package, service, container and update evidence attached to the machine that reported it. Joining a fleet transfers approval authority to Server; Desktop remains the local console. Installing Server is a separate operation and does not enroll the local Endpoint.
Observe, authorize, remember
Updates pass through human approval and recorded policy. On APT and DNF, signed capabilities bind an operation to a host and the artifact hashes that resolved. Standalone pacman uses an envelope over exact archives and detached signatures. The Helper checks authorization before acting through fixed arguments. Coverage differs by package manager.
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
Linux Desktop has been exercised on development machines. Windows installation testing is in progress. Available public downloads are listed below.
Linux uses native packages: Debian/Ubuntu .deb and Arch/SouveraineOS pacman packages. Arch packaging exists, but the current public release does not yet include an Arch download.
Update support varies by package manager. Full dependency hashing and Helper network isolation remain in development; Windows Fleet Join is not yet available.
