← All projects
Architecture study · 2026
hermes-infrastructure
How I organise an agent system on a single server — and what I refuse to give it.
The problem
A multi-agent system routed through a third-party API sends all of its context to that third party. For personal data this is not an implementation detail: it is an architecture decision, and it is taken before the first line of code.
What I built
A full architecture study: model routing by task and data sensitivity, a multi-profile orchestrator with specialised workers, self-hosted services (local inference, automation, secrets vault) and a backup strategy. The public version is stripped of any real infrastructure data.
Technical points
- Clean separation between orchestrator and workers: a simple task does not wake five agents.
- Routing arbitrates between cost, latency and confidentiality — not quality alone.
- Every publication goes through systematic sanitisation: no hostname, port or secret.