AzureAgentForge

What AzureAgentForge does

AzureAgentForge does not invent a new orchestration engine, agent runtime or memory store. It integrates PaperClip for orchestration, task management and the operator UI, Hermes for agent execution, and Honcho for private, self-hosted memory. Terraform deploys the Azure side, including Container Apps compute, networking, secrets in Key Vault, PostgreSQL with pgvector and centralized logging.

Model traffic goes through a Foundry-first, OpenAI-compatible router with budgets, fallbacks and cost attribution, and human approval gates cover destructive or high-risk actions. The stack can run on your own computer, in your Azure subscription, or both. The README reports about 83 dollars a month in measured infrastructure spend for its cost-optimized Azure profile, and about 35 to 45 dollars a month in cloud spend for a self-hosted-primary topology with an Azure warm standby, both excluding LLM token charges and described as estimates rather than guaranteed bills.

Key features

• PaperClip, Hermes and Honcho integrated into one deployable stack
• Terraform deployment to Azure Container Apps with Key Vault and PostgreSQL
• Foundry-first model router with budgets, fallbacks and cost attribution
• Human approval and blast-radius controls for risky actions
• Self-hosted-primary and full-Azure topologies

When to use it

• Run a team of Hermes-based agents with private memory in your own Azure subscription
• Cap model spend per agent with enforced budgets
• Tear down and rebuild an agent platform consistently with Terraform

Who it is for: Teams that want to operate Hermes agents on Azure with memory, cost controls and approval gates.

How it fits with Hermes Agent

Hermes Agent is the agent execution runtime inside a larger stack with PaperClip orchestration and Honcho memory.

Note: The README has a section on what is not finished yet, and Azure and model provider charges apply.

FAQ