Fleet overview
Review tenant health, access state, usage, managed-secret status, and recent activity from one operational overview.
Hermes Hub
Host and govern A2A-ready AI agent runtimes
Hermes Hub is Bewize's shipped AI agent control plane for hosted Hermes Agent runtimes. It manages tenant lifecycle, A2A edge access, releases, policies, secrets, storage, schedules, internal flavors, and runtime operations so companies can run agents through infrastructure they control.
See the operator console
Hermes Hub is API-first infrastructure with a focused console for day-to-day operations. These current product captures use safe illustrative tenants and mock operational data.
Skills and flavors
Inspect first-party agent specializations, installed versions, adoption, and upgrade state.
Hub configuration
Manage Hub-owned defaults and understand which configuration changes affect tenant runtimes.
Shared storage governance
Control share groups and make access relationships explicit across managed tenants.
Tenant files
Browse tenant-scoped files and operational artifacts without collapsing tenant boundaries.
Run evidence
Filter run history, inspect outcomes, and connect token usage to the operational record.
A focused console for day-to-day operations
Hermes Hub remains API-first infrastructure, with an operator console for inspecting fleet state, run history, usage, schedules, configuration, files, skills, and first-party flavors. The screenshot uses illustrative mock tenants and operational data.
Searchable run history
Filter operational history by time, tenant, and status, then inspect the selected run.
Usage evidence
Review token events and aggregate usage alongside run outcomes.
Fleet context
Move from dashboard health into the operational record that explains agent activity.
Safe demonstration data
Visible tenant names, counts, schedules, and verdicts are illustrative rather than customer deployment data.
What does Hermes Hub do?
Hermes Hub turns hosted Hermes Agent runtimes into managed tenants: each tenant has runtime identity, lifecycle state, policy, secrets, storage, schedules, and usage evidence. For A2A, the Hub provides controlled edge support with agent cards, credentials, peers, and routed messages rather than exposing private runtime APIs directly.
AI agent orchestration
Lifecycle operations, release pinning, scheduler wakeups, run lifecycle, and policy APIs are source-backed.
AI agent management
Tenants expose identity, host, Linux user, home paths, runtime state, storage links, and environment artifacts.
Internal flavors and templates
Use precise wording: internal flavors and static templates are supported; do not imply open third-party publishing.
A2A interoperability
Source-backed scope is A2A edge support with agent cards, credentials, peers, and message routing.
Operational outcome
Platform teams can run AI agents as governed infrastructure instead of unmanaged personal tools.
How A2A fits into Hermes Hub
A2A belongs at the boundary. Hermes Hub lets compatible outside agents meet a tenant through controlled edge access while policies, credentials, files, schedules, and run evidence stay inside company-owned runtime operations.
Hermes Hub control plane
A2A cardsCredentialsPeer routingPolicyRun evidence
Edge access, not engine-room access
Compatible A2A agents connect through controlled cards, credentials, peer records, and routed messages instead of direct access to tenant runtime internals.
Tenant-owned runtime controls
Lifecycle state, release pinning, secrets, storage, scheduler wakeups, policy APIs, and run history remain part of the tenant operational record.
Room-visible collaboration
WorkCord can make agent participation visible to teams in shared rooms; use it when collaboration context matters, not as a replacement for Hub runtime control.
Clear shipped-versus-roadmap boundary
A2A edge support is shipped. A2UI, an open third-party marketplace, broad chat adapters, and public browser assistance remain roadmap or directional unless separately documented.
Evaluation path
Start with the A2A boundary, then review agent orchestration, security governance, observability, and WorkCord collaboration before planning a private deployment.
Discuss Hermes Hub
Plan hosted Hermes Agent runtime, tenant lifecycle, A2A edge access, policies, secrets, storage, release operations, and the evidence needed for a governed rollout.
Architecture conversation
Tell us what your team needs to control
Share your deployment boundary, number of agents, work surfaces, and governance requirements. We will reply by email to arrange a focused technical discussion.
Email the Bewize teamThis opens your email application. Read our Privacy Policy.