Hermes Multi-Tenant Isolation Architecture
Shared host, per-client profiles and tool boundaries: how external clients reach their own Hermes workspaces without seeing another tenant's tools or data.
Hermes Single Client, Single Department Architecture
Option 1 of the Hermes multi-tenant setup: one external actor, one gateway, one isolated workspace inside an execution sandbox, and a single client profile.
Full FlowZap Code
Copy and paste the following FlowZap code into a project in your FlowZap account to see this template diagram.
external_actor { # External Actor
n1: circle label:"Client User"
hermes_runtime.n4.handle(right) -> execution_sandbox.n5.handle(left) [label="executes code"]
hermes_runtime.n3.handle(right) -> hermes_runtime.n4.handle(left) [label="routes"]
hermes_runtime.n2.handle(right) -> hermes_runtime.n3.handle(left)
external_actor.n1.handle(right) -> hermes_runtime.n2.handle(left) [label="message"]
}
hermes_runtime { # Hermes Runtime
n2: rectangle label:"Telegram Bot"
n3: rectangle label:"Gateway"
n4: rectangle label:"Profile: client-x"
}
execution_sandbox { # Execution Boundary
n5: rectangle label:"Isolated Workspace"
}
Install the MCP packagenpm install -g flowzap-mcpMCP documentation
Related templates
Hermes Single Client, Multi-Department Routing Architecture
Option 2: one client with several entry points, a prefix router that maps /eng or /support to a mode, and a single unified Hermes profile behind the gateway.
Hermes Full Multi-Tenant with Department Routing
Option 4: external participants, per-client gateways and routers, department prefixes inside each tenant, and a sandbox per client.
Hermes Multi-Client Isolated Profiles Architecture
Option 3, the core multi-tenant setup: per-token entry points, one gateway per client, and isolated Hermes profiles running in separate containers.
Hermes Kanban Agent Coordination Workflow
A planner decomposes the request on a shared board, specialized workers claim tasks, and the orchestrator delivers once every card is closed.
Agentic Taste Evaluation Loop
Legacy executor, LLM-as-judge evaluator and next-gen consumer: an evaluator scores the full trajectory, rejects structural sloppiness and forwards only validated payloads.