Instance setup
A dedicated workspace provisioned for your account.
Public workbench preview
Preview the Cloud workbench before you launch it.
The public page now shows the real workspace shape: employees, inbox, routines, memory, channels, approvals, and runtime health. Hermes and OpenClaw remain runtime choices; you see one Cloud workbench.
Preview mode
Visible before sign-inPrivate data stays behind the workspace gateLaunch, connect, and manage require sign-in
Team Inbox
Morning brief is ready
Needs review · 2 sources
Customer reply draft
Human approval required
Source connection pending
Private action
Routines
08:30Daily brief
14:00Inbox sweep
FriWeekly handoff
Instance Knowledge
Product facts
Customer tone
Decision log
Cloud workbench
What you can understand before logging in
The public page now shows the real Cloud shape: employees, inbox, routines, memory, channels, approvals, and runtime health. Sign-in starts only when you launch or manage private state.
Controls
Runtime and control stay visible
Cloud handles the wiring. You handle the decisions.
Runtime boot
Starts Hermes / OpenClaw and handles upgrades and health checks.
Instance Knowledge
Cloud-level memory for durable team facts and decisions.
Team Inbox / Work State
Approvals, in-progress work, and blockers in one panel.
Routine scheduling
Scheduled, event-based, or message-triggered runs.
Model access
Voxyz Access wired by default; BYOK toggle for heavier or controlled usage.
Runtime
Hermes + OpenClaw in one Cloud workspace
To the buyer, this is one Cloud Office, not two products. Hermes and OpenClaw can both carry employee entries, tasks, memory, tools, and reviewable state; Cloud turns the runtime choice into a clear product experience.
Hermes
Hermes
An optional agent runtime for employee entries, task scheduling, memory, skills, Dashboard, and API capabilities.
- Employee entries
- Tasks and scheduled runs
- Memory / skills / API
OpenClaw
OpenClaw
An optional agent runtime for employee entries, sessions, workspace state, task scheduling, WebChat, and multi-entry routing.
- Employee entries
- Sessions and multi-entry work
- WebChat / workspace / routines
The same Cloud instance can use Hermes or OpenClaw by configuration. The first employee bootstraps the default Hermes Profile; Instance Knowledge belongs to the Cloud layer, and the runtime executes the work.
Common questions
Is Cloud priced per AI employee?
No. Cloud is priced per workspace. One subscription can run multiple AI employees and includes the Hermes + OpenClaw path without per-runtime pricing.
How does Cloud relate to Playbook?
Cloud is the hosted workspace you can boot from a fresh account. Playbook is the build-it-yourself field guide. You can buy either or both.
Does the first AI employee create a new Hermes Profile?
No. The first employee bootstraps the default Hermes Profile with First Contact, Job, Routine, and channel intent. A dedicated Profile is only created later when you explicitly want isolated memory, channels, or responsibility.
I already own Pro. Anything to do?
Nothing changes. When you activate Cloud, the existing Cloud starter months still apply.
Next step
Let Cloud carry the wiring. You carry the decisions.
One Cloud workbench runs your first AI employee. Over time, the same workspace can become the start of an AI-native team.