Explore Roomcord

Bewize Hub release notes

The control plane is turning agents into operated infrastructure

A chronological view of Bewize Hub progress: tenant-scoped runtimes, A2A edge access, redacted observability, policy, release management, secrets, storage, schedules, flavors, and production operator surfaces.

Updated September 15, 2026

Explore Bewize HubRoomcord releases
Tenantsisolated runtime boundary
A2Acontrolled agent edge
Cronscheduled agent work
Metricsredacted usage visibility

Chronological changelog

What changed, latest first

These notes focus on source-backed product capabilities and avoid overstating roadmap items as shipped.

Hermes Hub release

Latest

Hermes Hub improved stale-run cleanup and warm-runtime capacity.

The September 15 release added indexed stale-run cleanup and increased default warm-runtime capacity while preserving explicit host settings. These are Hermes Hub runtime updates, not releases of Autoworker Hub.

Source: FullDive public release notes, Hermes Hub, 2026-09-15.

Autoworker Hub release

Autoworker Hub advanced runtime resilience and release verification.

The separate Autoworker Hub release notes report dynamic runtime-port leasing, external memory connectivity and migration support, stronger recovery, and verified packages for two processor architectures.

Source: FullDive public release notes, Autoworker Hub, 2026-09-14.

Current platform inventory

Bewize Hub product truth was consolidated into an operator-ready control-plane story.

The current Bewize Hub inventory frames the product as the operational control plane behind hosted agents: isolated by tenant, governed by policy, observable without leaking prompts, connected to chat and A2A, upgraded through releases, packaged through flavors, and kept cost-efficient through cold-idle hosting.
Isolation Tenant boundaries are concrete infrastructure

Each tenant has isolated memory, secrets, sessions, cron, files, browser profile, SSH identity, logs, and runtime state. The separation is done in infrastructure, not by a prompt promise.

Operations Runs, releases, and schedules are managed surfaces

The Hub exposes tenant lifecycle, run status/events, stop controls, cron, release activation, pinned releases, reconcile flows, and timeline markers so agent work can be operated like a product.

Governance Capabilities are granted, not assumed

Hub-wide and per-tenant policy controls search, files, browser, terminal, cron, delegation, and similar features; approval gates exist for sensitive actions.

  • Boundary: current shipped runtime scope is managed AI worker tenants. Arbitrary agent-framework hosting and a public third-party flavor marketplace are not shipped.

Source: Bewize Hub maintained feature inventory and article research brief refreshed 2026-07-09.

Admin proof

Bewize Hub admin UI gained screenshot-backed tenant operations proof.

The Bewize Hub Playwright output demonstrated dashboard health, tenant lifecycle controls, tenant-scoped timeline observability, policy and skills management, secrets/env redaction, system operations, browser isolation, and hub config defaults with tenant runtime impact.
Console Operators can work without SSH as the default interface

Tenant directory/detail, lifecycle controls, policy and skills views, file browsing, schedule markers, env metadata, releases, specialization, reconcile output, and browser-isolation proof became screenshot-ready surfaces.

Trust Secrets and metrics stay product-safe

Secret metadata and usage surfaces are designed to support operations without rendering raw secret values or turning analytics into a prompt leak.

Source: 2026-06-14 product-update feed.

Website architecture

Bewize public website started presenting the A2A ecosystem product architecture.

The website began leading with the Bewize A2A ecosystem: Roomcord for shared rooms, Bewize Hub for hosted agent runtime and orchestration, AgentsEval for captured-run evaluation, and Browser Sidecar for tenant browser isolation. The copy separated implemented proof from directional Chrome-extension and process-mining claims.
Ecosystem Bewize Hub became the platform layer in the public story

The website connects Roomcord, Bewize Hub, AgentsEval, and Browser Sidecar as one managed A2A agent ecosystem rather than isolated product pages.

Positioning Private and governed deployment became the center

The story moved toward self-hosted, isolated, observable agent infrastructure for companies that need control over data, tools, runtime policy, and adoption.

Source: 2026-06-14 product-update feed.