Back to Operating Guides
Cloud Setup6 min readUpdated May 13, 2026

Cloud Quickstart

Cloud is the hosted path: one account, one instance, OpenClaw and Hermes on the same machine, and a shared memory layer inside the runtime. Use this quickstart when you want to know what happens after you click trial.

New Cloud users who want a short, task-based path before they open setup, billing, WebChat, Dashboard, or Telegram connection settings.

Summary

Start here when you want the actual Cloud setup path: payment gate, sign-in, OpenClaw WebChat, Hermes Dashboard, Voxyz Access, BYOK API keys, Telegram, and the first workspace check.

01

Start from the Cloud trial and sign in once

The clean path is:

  1. open Pricing
  2. choose Cloud
  3. start the trial or checkout
  4. sign in or create the Voxyz account
  5. return to Cloud setup

Cloud setup is tied to the account because billing, saved agents, instance state, Studio, Marketplace, and support all share the same workspace identity. If you are already signed in, the setup page should skip the public sign-in page and continue to the Cloud flow.

02

OpenClaw and Hermes can live on the same instance

The default Cloud machine is one VPS-style instance. OpenClaw and Hermes are separate agent surfaces inside that instance, not two separate customer machines.

  • OpenClaw WebChat is the coordinator and everyday agent room.
  • Hermes Dashboard is the protected profile, provider, and operations surface.
  • Instance Knowledge is the shared memory / library layer both sides can read and write through the configured tools.

That means adding Hermes should attach it to the same running instance when the user already has OpenClaw live. The UI should not make the user wonder whether a second host was created.

03

Use Voxyz Access first, bring your own API key when needed

Most users should start with Voxyz Access. It gives the runtime a working model path without asking the user to paste an embedding key, OpenAI key, or gateway key on day one.

Advanced users can still bring their own keys later. The important product rule is simple: first launch should work with safe defaults; deeper provider control belongs in Cloud / Hermes settings where it can be saved back to the control plane and survive restarts.

04

Telegram is a connection setting, not a Marketplace pack

Telegram setup lives in Cloud connection settings.

The short version:

  1. create or reuse a bot token from @BotFather
  2. get your numeric user ID from @userinfobot
  3. paste those into the Cloud Telegram settings
  4. wait for the live sync status
  5. test one message in the connected room

Marketplace agents can use chat-style workflows, but the Telegram channel itself is a Cloud runtime connection. If Marketplace search does not return a Telegram pack, that does not mean Telegram is unsupported.

05

First successful launch looks boring

A healthy first launch should be uneventful:

  • the instance reaches Running
  • OpenClaw opens the coordinator WebChat
  • Hermes opens its own Dashboard
  • Instance Knowledge shows connected or indexing
  • Telegram stays optional until you connect it

If any status says pending, failed, or needs attention, use the retry button or send feedback with the support code. Do not paste passwords, API keys, Telegram tokens, or one-time login links into feedback.

Next step

Ready to run the hosted path?

Start the Cloud trial, sign in once, then use setup to bring the OpenClaw WebChat, Hermes Dashboard, shared memory, and optional Telegram connection online.