
Tenant lifecycle
Create, start, stop, restart, block, disable, inspect runtime metadata, and track tenant identities.
Hermes Hub
Hermes Hub is the AI agent platform layer in the Bewize ecosystem. It manages tenant lifecycle, A2A edge access, releases, policies, secrets, storage, schedules, flavors, and a static agent-template market.

These screenshots are copied from Hermes Hub Playwright proof output and show implemented operating surfaces.

Create, start, stop, restart, block, disable, inspect runtime metadata, and track tenant identities.

Inspect global policy, tenant overrides, installed skills, and effective policy payloads.

Manage tenant secret metadata and environment keys without rendering raw secret values in the proofed admin surface.

Observe tenant-scoped schedules, run markers, and timeline details.

Hub config explains whether changes require hub restart, tenant reconcile, or tenant agent restart.

Tenant browser sidecar state and browser artifacts are represented inside tenant runtime metadata.
Hermes Hub carries the strongest existing platform proof: tenant lifecycle, A2A edge support, releases, policies, secrets, storage, flavors, schedules, and agent-template market direction.
The hub turns agents into managed tenants.
Lifecycle operations, release pinning, scheduler wakeups, run lifecycle, and policy APIs are source-backed.
Tenants expose identity, host, Linux user, home paths, runtime state, storage links, and environment artifacts.
Use precise wording: static agent templates and flavors are the supported market direction; do not imply open third-party publishing.
Source-backed scope is A2A edge support with agent cards, credentials, peers, and message routing.
Teams can host managed agents with visible ownership, policy, release, runtime, and A2A routing boundaries.
Plan hosted agent runtime, tenant lifecycle, A2A edge access, policies, secrets, storage, and release operations.
+1 332 2081410
[email protected]