Nexus is the platform · Argus keeps watch
Argus is an assistant built to hold context — what a system is doing, why it was built that way, and what changed before it broke. Nexus is the self-hosted platform underneath it: services, networks, containers, and hardware sharing the same wire.
Argus is specified as three faculties, each buildable and judgeable on its own. They are not separate products — none of them is worth much without the other two.
The thing that runs. Linux hosts and composed containers, a single reverse proxy holding TLS and the front door, PostgreSQL for persistence, an MQTT broker carrying device traffic, and functional modules written against those services rather than around them.
The layer a person talks to. It reads platform state rather than changing it, keeps decisions as durable records, and drafts new ones while the reasoning is still in the room — always as proposals, never as silent assertions.
Argus sits outside the platform boundary on purpose. If the assistant is absent, Nexus still runs.
The artefact Argus is built to retain — so here are real ones.
Device state and commands move over a broker rather than over HTTP request/response between the platform and each device.
One ingress point holds TLS, security headers, and the authentication boundary. Services publish no host ports.
Records are first-class platform data rather than files in a repository, because the assistant that reads and drafts them needs somewhere to look.
Everything here is a system I actually operate, described at the level it actually exists. Where something is designed but not built, it says so.
How this site is built