Home compute, Azure state: a practical multi-agent stack built around shared Postgres

MRobinsonTX · reddit · 2026-07-24

The author describes a cheap multi-agent setup where state lives in Azure and compute runs at home. The core of the system is a managed PostgreSQL Flexible Server plus Key Vault in Azure, while the orchestrator, agent runtime, memory service, and model router run on a local Mac mini / small PC.

Why this design works

Tradeoffs

A key lesson: agent identity matters

Once multiple agents share one memory store, ambiguity appears fast: the planner, researcher, and other agents can bleed into each other’s context. The author now gives each agent a canonical identity, rewrites aliases on write, and emits events when an unknown peer shows up instead of silently sharding memory.

Cost control

The overall message is pragmatic: Azure is the always-on spine, home hardware is the cheap muscle, and the biggest wins came from identity design and model-tier budgeting, not infrastructure polish.

Original post →

More from coding & agent

coding & agent channel →