
From Per-Agent Services to One Manager
I built the first version of our agent hosting: one service per partner agent, each with its own process and proxy config. It worked, but at 25 agents every release meant touching 25 services. I redesigned it into one manager per environment that provisions agents from the admin UI and routes requests to them over Unix sockets, so releases, backups and multi-server rollouts became predictable.
- Replaced repetitive manual deployment steps with a consistent, operator-friendly workflow.
- Made backups and multi-server rollout simpler and less error-prone through standardized service layout.

