An agent without infrastructure isn’t a product
A model can answer in chat. Claweb ships what keeps an agent alive in production: placement, channels, skills, backups, and observability.
Your own server & runtime
VPS, Docker, upgrades, and 3 a.m. outages instead of product work.
Models pieced together
Chat, STT, vision, image gen, and search take weeks to wire by hand.
Blind ops
Without logs, status, and session errors you never know why the agent went quiet.
Skills from scratch
Useful workflows take months; ready, installable packs are rare.
Memory at risk
Config, vectors, and skills vanish with the container.
Slow time-to-bot
Empty account to Telegram bot is days of DevOps, not minutes.
The power is in the details
From the first Telegram message to incident diagnosis: agent, tools, skills, and clear control in one loop.
Cloud or your VPS
Start on Claweb nodes. Need “mine only” isolation — claweb-node on your VPS, same console, your capacity.
Multimodal out of the box
Text, voice (STT), speech (TTS), photo understanding, image generation, and web search — one LLM gateway.
Mission Control observability
Provisioning timeline, live logs, web terminal, session errors, and agent health — no SSH, no guesswork.
Skills ready for real work
Practical packs from the @claweb catalog install at agent boot. OmniVoice, for example — TTS and voice clone in Telegram.
What’s inside Claweb
A full operator loop: where the agent runs, how it thinks and speaks, how you see it, and which skills you can turn on today.
Placement & isolation
Each agent is a quota’d container. Shared platform node or a dedicated node on your hardware.
- Per-agent container and data volume
- Shared Claweb nodes — no server of your own
- Dedicated node: VPS + claweb-node + enroll
- TLS at the edge, mTLS to node-agent
Models, voice & images
Not a single chat endpoint — a multimodal set already wired at provision time.
- Chat models on the plan allow-list
- STT (voice → text) and TTS/speech via skills
- Vision, image generation, and search MCP
- Per-agent key with TPM / RPM / budget
Observability & control
Mission Control shows the real life of an agent — not a green checkbox.
- Step-by-step provisioning timeline
- Live logs and browser web terminal
- Session errors and degradation signals
- State and memory backups, restore in one flow
Skills that already work
The @claweb catalog: proven packs, not drafts. Installed with the plan, extended by you.
- Compose: platform ∪ plan ∪ your extra skills
- OmniVoice — TTS, voice clone, speech style
- Reconciled on every container boot
- Telegram + Control UI as delivery channels
Who Claweb is for
For people who need a production agent, not a demo chat: channels, skills, backups, and clear diagnostics.
Personal AI assistant
A long-running Telegram partner: memory, speech, skills, and backups — not a one-off chat window.
Agent fleet
Several containers, shared quotas, fleet-wide observability.
Dedicated node
Your VPS + claweb-node: only your agents, still managed from the Claweb console.
Telegram channel & support
An OpenClaw bot: provisioning, logs, session errors, and restore after incidents.
Content & voice
Images, STT, TTS/OmniVoice, and search — the agent creates and delivers media to the channel.
Ops without SSH panic
Terminal, live logs, provisioning timeline, and session-error classes when something breaks.
Three steps to a live agent
Three steps: access → a live agent with skills → operator control. Dedicated node when you need it.
Sign in and pick a plan
Register with Telegram or Yandex. The plan sets agent, CPU/RAM, and LLM limits.
- Login: Telegram Login or Yandex
- Quotas from the plan catalog (Starter / Pro / Business)
Create an agent with skills
Container on an online node; OpenClaw, models, multimodal tools, plan skills, and Telegram — one provision pass.
- Name, bot token, optional Telegram user ID
- Gateway, MCP, STT/vision/image gen, memory, Control UI
- Skills (e.g. OmniVoice) reconcile at boot
Observe, operate, scale
Logs, terminal, session errors, backups. Need your VPS — claweb-node, enroll, pin agents.
- Observability and actions in Mission Control
- Shared nodes or a dedicated node on your VPS
Plans by agent capacity
Agent and resource limits scale Starter → Pro → Business. Cards below come from the live plan catalog.
What you pay for
Agent hosting and control plane are on the platform. LLM usage sits in plan limits. @claweb catalog skills install with the plan. A dedicated node is your VPS + claweb-node.
Shared nodes — included
Default path: agents on Claweb infrastructure, no VPS required.
LLM — plan limits
TPM/RPM and budget on the agent key via the platform gateway; need more — upgrade the plan.
Dedicated node — your VPS
You rent the box, install claweb-node, enroll it — only your agents land there.
How it looks in practice
Short Mission Control scenes — not invented street testimonials.
“Voice note in Telegram → transcript → spoken reply. Skills and media aren’t “later” — they’re already on the agent.”
Scenario: voice end-to-end
“Step provisioning, live logs, session errors. If the agent goes quiet, you see the error class — not an empty chat.”
Scenario: observability
“Started on a shared node. When isolation mattered — VPS with claweb-node, same controls.”
Scenario: grow to your own node
Frequently asked questions
Cloud, skills, observability, and dedicated nodes — short and practical.
Not to start: agents run on Claweb nodes. A VPS matters when you want a dedicated node — install claweb-node and enroll it in the control plane.
STT (voice notes → text), vision (photos), image generation, web search MCP, and speech via the OmniVoice skill — with media delivered to Telegram.
The @claweb catalog: practical packs, not stubs. Plans default to OmniVoice (TTS, voice clone, speech style). Effective set = platform ∪ plan ∪ your extras; skills reconcile on every container boot.
Mission Control: provisioning timeline, live logs, web terminal, session errors with classes (OOM, MCP, tool-use, and more). Operator signals only — we don’t bulk-ingest chat transcripts.
An account (Telegram or Yandex), an active plan, and ideally a Telegram bot token. No separate server or third-party LLM keys for the default path.