Your OpenClaw bot,
live in a minute
Paste a model key and a channel token, pick a version, done. Robot Arms keeps the gateway up, the state safe and the upgrades painless. Your first bot is free; every next one is €19 a month, flat.
✔namespacera-chikins · quota ok✔secretsmodel key + telegram token sealed✔state volume10 GiB bound · replicated✔gatewayopenclaw 2026.10.3 running✔doctor0 warnings✔tlshttps://lobster.chikins.rbta.dev●readysay hi to it on TelegramEverything a bot needs. Nothing you have to run.
The parts of hosting that are not about your bot: storage, secrets, TLS, upgrades, metrics. Robot Arms does them the same way every time, so the only thing you deal with is the bot.
Telegram in the UI today. The runtime also speaks the rest; paste a token, pick a channel.
Three steps to a live bot.
No cluster, no YAML, no SSH. Each step is a short form; the result is a URL.
- 01
Sign in
Enter your email and open the link. That is the whole account; no card is needed for the free bot.
$ login → email link → done - 02
Create an organization
A name and a slug. It becomes an isolated namespace with its own quota and members.
$ org chikins 4 cpu · 8 GiB · 50 GiB - 03
Create a bot
Name, OpenClaw version, model key, Telegram token. Watch the steps go green, then say hi to it on Telegram.
$ bot lobster lobster.chikins. rbta. dev
One flat price per bot. Stop any time.
Compute, storage, TLS and upgrades are in the price; nothing is metered. A bot you delete stops costing anything the same minute. Prices are indicative while Robot Arms is in early access.
A CLI built for agents.
Everything the app does, from a terminal or an AI agent: bots, the openclaw CLI inside them, their files, their logs. One install line.
$ curl -fsSL https://robotarms.apartments/install.sh | sh$ rbtactl auth login signed in as you@example.com$ rbtactl workspace init --org chikins --bot lobster$ rbtactl openclaw -- channels list --json$ rbtactl config edit --restart$ rbtactl mount ~/lobster mounted chikins/lobster at ~/lobsterThe spec sheet.
What a bot is made of, in the words the admin page uses.
- runtime
- OpenClaw, official image, version pinned per bot (2026.9.6 … 2026.10.5)
- isolation
- Kubernetes namespace per organization · network policy per bot · resource quota per organization
- state
- persistent block volume per bot · replicated across nodes · snapshot before every upgrade
- secrets
- sealed in the cluster · injected as environment · never written to openclaw.json
- identity
- sign-up by email link · passkeys, no passwords · roles owner / member · invites
- access
- Control UI behind forward-auth · same sign-in as Robot Arms · org membership checked on every request
- health
- inspector sidecar runs openclaw doctor on a schedule · failing channels reported on the bot
- skills
- resolved from git repositories at start · pinned refs · status per skill
- metrics
- CPU, memory, storage per bot and per container · 5-minute rate from Prometheus
- tls
- automatic certificates · <bot>.<org>.rbta.dev
- billing
- flat price per bot · month · first bot free · stops the minute a bot is deleted
Questions, answered plainly.
Ready when you are.
Start with one bot, free. Upgrade it, invite a teammate, delete it. Nothing to install, nothing to pay until the second bot.