Frequently asked questions
Short answers about plans, Telegram, and the managed OpenClaw runtime.
For setup guides and feature depth, see the documentation — start with Get started or Troubleshooting.
Starter is the entry plan with clear caps (automations, RSS monitors, monthly usage). It is built for a strong Telegram-first daily loop: reminders, Google Calendar, RSS, and background automations within those limits. Pro is the full product: higher caps, HTTP/API data in automations, inbound webhooks, outbound webhooks where enabled, and more headroom for heavy weeks. See the Starter vs Pro doc and live details on checkout.
No separate API bills from us. Starter and Pro each include AI usage for the managed OpenClaw runtime within that plan’s fair-use limits and caps. Heavy usage may hit plan ceilings or fair-use safeguards — your dashboard shows where you stand.
Every paid plan includes a fully managed OpenClaw runtime, one agent per account, Telegram as the primary channel, a choice of models without you bringing API keys, and hosting. What differs by tier is limits and which integration surfaces are available (e.g. HTTP fetch and inbound webhooks are Pro-oriented).
You can try EasyClaw on Telegram with a limited number of billable runs before subscribing. Trial behavior is aligned with Starter-class guardrails so costs stay predictable — not every Pro-only integration is available until you are on Pro. Upgrade on checkout when you are ready.
Inbound webhooks, HTTP/API fetch in automations, and related glue features are Pro-oriented. Starter focuses on Calendar, RSS, and Telegram-native workflows within plan caps. Read Inbound webhooks and HTTP fetch in the docs for how they fit your setup.
Self-hosting means your own servers or VPS, Docker, model API keys and token bills, updates, and ops time. EasyClaw is a managed subscription: we run OpenClaw for you with agent-level isolation — you use Telegram and the dashboard instead of maintaining infrastructure.
No. EasyClaw runs OpenClaw for you. No servers, no Docker, no SSH, no infrastructure to manage on your side.
Security is managed for you: Row Level Security (RLS) for data, encrypted storage, and isolated execution per agent. You do not patch servers or configure firewalls for the runtime.
No. Infrastructure is shared, but each agent runs in a strict isolated namespace. Browser sessions are ephemeral per task — like a fresh private window — so data and cookies are not shared between users.
Yes. Each plan includes a bounded amount of usage and feature caps (automations, monitors, etc.). Exact numbers appear in your dashboard and on checkout — we do not treat any tier as unlimited.
Not a dedicated container per user. EasyClaw runs a shared OpenClaw runtime with strict agent-level isolation so memory and execution are separated per account.
Telegram is the supported channel today — it is the primary product surface for delivery and chat. Other channels may come later.
Self-hosting OpenClaw yourself remains an option in the broader ecosystem; EasyClaw is focused on the managed path. If you need migration guidance later, contact support.