01 / Start here
Managed OpenClaw · one instance
A ready runtime for the agent.
Managed availability is reviewed with the team.
Review the term, GST, AI credits, and shared-infrastructure scope before adding a plan.
Managed OpenClaw / clear operating boundaryUnited States / availability by request
The agent, without the server chores
Put OpenClaw to work.Keep the runtime managed.
Start with one managed instance, connect the agent after sign-in, and keep the subscription, AI usage, and private credentials clearly separated.
See plans
Managed runtime
Telegram pairing
Maintenance handled
AI credits separate
One managed service, three responsibilities
Know what the service does.
Connect the agent
Start with the channel and provider your workflow actually needs.
- Built-in Telegram pairing
- Provider setup after sign-in
- Human help before go-live
Run the service
Use a prepared runtime instead of assembling the server by hand.
- Managed OpenClaw instance
- Dashboard access
- Service health visibility
Keep it operating
The Cloud Market handles the routine infrastructure work around the agent.
- Updates and maintenance
- Monitoring and recovery
- Shared-infrastructure fair use
Authenticated setup path
Four steps to a verified agent.
01
Choose the term
Compare the annual and monthly instance charges before continuing.
02
Create or sign in
Private provider and channel details are only handled after authentication.
03
Connect the channel
Pair Telegram and review any additional integration requirements with the team.
04
Verify before go-live
Confirm the runtime, connection, credits, and service health before using the agent.
Before the first instance
OpenClaw questions, answered.
It includes one managed OpenClaw instance, dashboard access, the prepared runtime, maintenance, monitoring, and recovery support. AI model usage is not included in the instance subscription.
No. AI usage is handled through separate managed credit packs after setup. This keeps the fixed instance charge separate from usage that can vary with the model and workload.
Only inside the authenticated setup. This public page does not collect, save, or test credentials. The setup flow explains which connection is needed before any secret is entered.
Telegram pairing is built into the managed OpenClaw path. Other channels can have their own provider, account, and integration requirements, so confirm those needs with the team before choosing a plan.
Ask the team to review the active instance and current billing term before changing plans. The exact renewal and any effective date should be confirmed before the billing change is approved.
A dedicated KVM path is available for workloads that need more control or dedicated resources. Review the workload, storage, and operating responsibility before moving to that route.