Moltworker

What Is Moltworker? A Cloudflare Self-Deployment Pattern

The search phrase “managed hosting” can be misleading here. The project uses managed Cloudflare infrastructure, but the user deploys and operates the application in their own Cloudflare account. It is not a supported Cloudflare-hosted OpenClaw service with a dedicated customer plan.

Its architecture has several parts:

This is a cloud deployment of OpenClaw rather than a new agent runtime. OpenClaw provides the assistant, workspace, skills, conversations, and channels; the Cloudflare project provides the hosting adaptation.

Moltworker Cost Stack: Workers, Sandbox, R2 & Models

There is no standalone Moltworker pricing plan. The deployment requires a paid Workers plan for Sandbox containers, and usage can generate separate container, storage, network, logging, browser, and model costs.

The total depends on choices such as:

• Container size and how long it stays awake
• Active CPU use and provisioned resources
• Whether persistent storage is enabled
• Browser Rendering usage
• Worker, Durable Object, and network activity
• Model provider and token consumption
• Log volume and retention

Do not reduce this to “OpenClaw hosting for the base Workers subscription.” The official repository's own estimate shows that continuous container operation can cost materially more than the plan fee, and actual usage varies.

Sleeping the container can reduce compute costs, but the next request may have a noticeable cold start. Budget caps also need to account for model and platform services separately.

Source note: This section summarizes public pages available at review time. A missing public workflow or architecture detail is treated as a public evidence gap to verify with the provider, not as proof that the feature is unavailable.

Moltworker Setup Burden, Cloudflare Access & Model Keys

Moltworker packages OpenClaw's Control UI and documented Telegram, Discord, and Slack paths. Channel support still depends on the packaged OpenClaw version, required tokens, and correct policy configuration.

Setup is not one click in the SaaS sense. The operator must:

• Create the Cloudflare deployment and required bindings.
• Add model credentials or configure AI Gateway billing.
• Generate and store a Gateway token.
• Enable Cloudflare Access for the administration interface.
• Pair each new device.
• Configure R2 if state must survive container restarts.
• Add channel credentials and optional browser settings.
• Monitor costs, backups, logs, and upstream compatibility.

BYOK is supported through direct model credentials or Cloudflare AI Gateway configuration. The repository currently documents an Anthropic path most directly, while AI Gateway can provide broader routing options. Avoid claiming that every OpenClaw provider works automatically without configuration.

Source note: This section summarizes public pages available at review time. A missing public workflow or architecture detail is treated as a public evidence gap to verify with the provider, not as proof that the feature is unavailable.

Moltworker Public Evidence to Verify for Production Use

The OpenClaw process runs inside a Cloudflare Sandbox container, but the full deployment is tied to Cloudflare Workers, Access, Sandbox APIs, and optional R2, Browser Rendering, and AI Gateway services.

This creates both benefits and constraints:

Calling the design “serverless OpenClaw” hides the container. The Worker is the entrypoint, while the agent runs in a provisioned Sandbox container with memory, CPU, disk, and lifecycle behavior.

The project also requires Cloudflare Access and device pairing for the Control UI. Development mode can bypass those controls and should not be presented as appropriate for an internet-facing deployment.

Source note: This section summarizes public pages available at review time. A missing public workflow or architecture detail is treated as a public evidence gap to verify with the provider, not as proof that the feature is unavailable.

Moltworker vs MoClaw When You Do Not Want to Operate Infra

Moltworker is a build-it-yourself cloud deployment. MoClaw is a managed cloud AI computer intended for users who want to assign work rather than assemble the hosting stack.

Disclosure: We make MoClaw. Cloudflare's project is described from its official repository and engineering post.

Choose Moltworker when learning or controlling the Cloudflare architecture is part of the goal. Choose MoClaw when browser, file, skill, and scheduled work matter more than operating the infrastructure.

Security Questions: Access Policies, Pairing & Secrets

Sandboxing reduces direct host exposure, but cloud security still depends on identity, secrets, network routes, storage, and application configuration.

For Moltworker, the official setup expects:

• Cloudflare Access protecting administrative endpoints
• A Gateway token for remote Control UI access
• Explicit device pairing
• Separate secrets for channels and browser access
• R2 credentials if persistence is enabled
• Development bypasses kept away from public deployments

A local OpenClaw host has a different risk profile. It may expose personal files, browser sessions, or network resources available on that machine. The Cloudflare container separates the agent from a personal computer, but it places sensitive state and service configuration in a cloud account.

Neither model is automatically safer for every task. Minimize connected accounts, use dedicated credentials, and review what a skill or browser session can reach.

Source note: This section summarizes public pages available at review time. A missing public workflow or architecture detail is treated as a public evidence gap to verify with the provider, not as proof that the feature is unavailable.

Questions