Cutting PaperClip stack costs with a home-first setup
AzureAgentForge is an open-source that uses PaperClip for and the , Hermes for running agents, and Honcho for memory. It also includes a custom memory governor and a budget-aware , mainly using Azure AI Foundry. The setup first ran mostly in Azure because that was useful for learning, testing, and building a real deployment path.
For a , the always-on cloud cost became too high and would not go much below about $140 per month without removing parts of the design. Version 1.4 changes the setup so an always-on home PC or Mac Mini runs the full stack as the main site. Azure stays ready as a warm standby and failover site.
One managed Azure Postgres instance is shared, so switching during a problem is mostly a matter of moving compute work. Azure compute stays dormant until it is needed, and helper scripts handle failover and failback between the local machine and Azure.
Key points
- The Azure-first setup cost about $140 per month and was hard to reduce further.
- The newer setup runs the full stack on an always-on home PC or Mac Mini.
- Azure is kept as a warm standby and failover site instead of the main always-on site.
- A shared managed Azure Postgres instance makes the switch mostly about moving compute work.
- Helper scripts handle failover and failback between the local machine and Azure.