---
title: About DeployHermes
description: "How DeployHermes operates managed Hermes bot workspaces for teams that need durable AI-agent work."
canonical: "https://deploy-hermes.com/about"
last-updated: "2026-08-24"
---

# About DeployHermes

> How DeployHermes operates managed Hermes bot workspaces for teams that need durable AI-agent work.

Canonical: https://deploy-hermes.com/about
Updated: 2026-08-24

DeployHermes is a managed operating environment for persistent Hermes bots. It is built for teams that need an AI agent to keep working across missions, tools, and human decisions without turning a personal chat session into production infrastructure.

## What we provide

A DeployHermes workspace gives each customer an isolated runtime for a named agent squad. People assign missions, connect approved providers and tools, review decision tickets when judgement is needed, and inspect receipts for completed work. The platform is designed around a clear operating record instead of a black-box automation promise.

Hermes Agent is the runtime and control plane; it is not an AI model provider. Customers connect supported provider credentials and retain control over the model account that performs inference. DeployHermes supplies the managed environment where those agents run, remember context, and report their work back to the workspace.

## How agents are governed

DeployHermes treats agent actions as work that should be visible and attributable. Workspace membership controls who can read, decide, write, configure a squad, or manage credentials. API keys inherit a live workspace identity and can be restricted to the capabilities needed by the calling agent, so reducing a person's access or revoking a key takes effect without waiting for a separate synchronization job.

The product is a fit when a team wants persistent, supervised agent work with a durable mission board and audit trail. It is not a substitute for human approval on legal, financial, security, or other high-stakes decisions. Teams should start with bounded jobs, inspect the resulting receipts, and expand an agent's tools only after its behavior is understood.

## Contact and evaluation

You can start from the sign-in flow to evaluate the current self-service product, create a workspace API key, and connect a supported MCP client. The public documentation explains the supported setup paths, privacy posture, and troubleshooting steps without requiring a sales conversation. For support, security questions, or a deployment discussion, contact hello@deploy-hermes.com.

---

- [Full documentation index](/llms.txt)
- [Complete site text](/llms-full.txt)
- [Developer portal](/developers)
- [OpenAPI contract](/openapi.json)
- [MCP server card](/.well-known/mcp.json)