Hands-On Lab

Deploy OpenClaw AI Gateway

Deploy OpenClaw on Cloudflare Containers with Workers AI, R2 persistence, and admin dashboard.

openclaw-cf-demo-r2

OpenClaw AI Gateway running on Cloudflare Containers, powered by Workers AI (Kimi K2.5) via AI Gateway — with R2-backed persistence and a built-in admin dashboard.

One-Click Deploy

Deploy to Cloudflare's global network instantly

Workers AI

Kimi K2.5 via AI Gateway, no external keys

R2 Persistence

Device approvals & chat history survive restarts

Admin Dashboard

Stats, device management & CLI terminal

Auto-Onboarding

Self-configures on startup with R2 restore

Architecture

Browser ──► Cloudflare Worker ──► Container (OpenClaw Gateway)
                                    │
                                    ├── /admin/       Admin Dashboard (HTML)
                                    ├── /admin/api/*  Management Server (:18700)
                                    ├── /persist/*    R2 Persistence Endpoints
                                    ├── /openai/v1/*  AI Gateway Proxy → Workers AI
                                    └── /*            OpenClaw Control UI (:18789)

Choose Your Deployment Path

1 Verify Your Access ~5 min

Before we begin, let's confirm you have access to the workshop Cloudflare account.

Open the Cloudflare Dashboard and log in with the email you registered with.
Check the invitation email from Cloudflare — accept the invite to join the workshop account.
Once logged in, verify you can see the workshop account in the account selector (top-left).
Navigate to Workers & Pages — you should see the Workers Paid plan is active.

Trouble? If you don't see the invitation, check your spam folder. Ask a workshop helper if you're stuck.

2 Prepare GitHub Account ~2 min

You'll need a GitHub account to fork the repository. If you don't have one:

3 Prepare API Credentials ~10 min

You'll need the following values ready before deployment:

Getting the values:
• GATEWAY_AUTH_TOKEN: Generate with openssl rand -hex 16
• AI_GATEWAY_ACCOUNT_ID: Find in Dashboard → Overview → right sidebar
• AI_GATEWAY_ID: Create at Dashboard → AI → AI Gateway
• AI_GATEWAY_AUTH_TOKEN: Create API Token at My Profile → API Tokens

4 Deploy to Cloudflare ~5 min

Once you have all credentials ready, click the button below to start the deployment wizard:

Deploy to Cloudflare

Note: The wizard will guide you through forking the repo and entering your credentials. First deploy takes a few minutes to pull the container image (~784 MB).

5 Access Your Deployment ~5 min

After deployment completes, you'll have three URLs:

# Admin Dashboard
https://<your-worker>.workers.dev/admin/

# Chat UI
https://<your-worker>.workers.dev/#token=<your-token>

# Health check
https://<your-worker>.workers.dev/healthz

Approve Your First Device:

Open the Chat UI link above
Open the Admin Dashboard → Devices tab
Click Approve on the pending device
Return to Chat UI — it should connect automatically

6 Explore & Cleanup ~10 min

Admin Dashboard at /admin/ has three tabs:

Overview — Container status, uptime, memory usage
Devices — Manage paired devices, approve/revoke
CLI — Run commands inside the container

Persistence: OpenClaw uses R2 to persist data across container restarts. R2 supports objects up to 5 GB, so there are no practical size limits for chat history.

Post-Workshop Cleanup — If you want to remove your deployment:

npx wrangler delete

1 Verify Your Access ~5 min

Before we begin, let's confirm you have access to the workshop Cloudflare account.

Open the Cloudflare Dashboard and log in with the email you registered with.
Check the invitation email from Cloudflare — accept the invite to join the workshop account.
Once logged in, verify you can see the workshop account in the account selector (top-left).
Navigate to Workers & Pages — you should see the Workers Paid plan is active.

Trouble? If you don't see the invitation, check your spam folder. Ask a workshop helper if you're stuck.

2 Environment Setup ~10 min

Install the required tools on your machine.

1. Check Node.js — You need Node.js 18 or higher:

node --version
# Should output v18.x.x or higher

If not installed, download from nodejs.org (LTS recommended).

2. Install Wrangler CLI

npm install -g wrangler

3. Login to Cloudflare

wrangler login
# This will open a browser window — authorize the CLI

wrangler whoami
# Should show your email and the workshop account

3 Clone & Install ~5 min

Clone the OpenClaw R2 demo project and install dependencies:

git clone https://github.com/lllxpr/openclaw-cf-demo-r2.git
cd openclaw-cf-demo-r2
npm install

Note: If you don't have Git installed, you can download the repo as a ZIP from the GitHub page.

4 Create R2 Bucket & Configure Secrets ~10 min

1. Create an R2 bucket

npx wrangler r2 bucket create openclaw-data

2. Configure Secrets — Copy the example secrets file:

cp .dev.vars.example .dev.vars

Edit .dev.vars with your values:

GATEWAY_AUTH_TOKEN=your-secret-token
AI_GATEWAY_ACCOUNT_ID=your-account-id
AI_GATEWAY_ID=your-gateway-id
AI_GATEWAY_AUTH_TOKEN=your-api-token

3. Set Production Secrets

npx wrangler secret put GATEWAY_AUTH_TOKEN
npx wrangler secret put AI_GATEWAY_ACCOUNT_ID
npx wrangler secret put AI_GATEWAY_ID
npx wrangler secret put AI_GATEWAY_AUTH_TOKEN

5 Deploy & Access ~10 min

1. Deploy to Cloudflare

npm run deploy

Note: First deploy will take a few minutes to pull the container image (~784 MB).

2. Access Your Deployment — After deployment, you'll have three URLs:

# Admin Dashboard
https://<your-worker>.workers.dev/admin/

# Chat UI
https://<your-worker>.workers.dev/#token=<your-token>

# Health check
https://<your-worker>.workers.dev/healthz

3. Approve Your First Device

Open the Chat UI link above
Open the Admin Dashboard → Devices tab
Click Approve on the pending device
Return to Chat UI — it should connect automatically

6 Explore & Cleanup ~10 min

Admin Dashboard at /admin/ has three tabs:

Overview — Container status, uptime, memory usage
Devices — Manage paired devices, approve/revoke
CLI — Run commands inside the container

Persistence: OpenClaw uses R2 to persist data across container restarts. R2 supports objects up to 5 GB, so there are no practical size limits for chat history.

Post-Workshop Cleanup — If you want to remove your deployment:

npx wrangler delete

Troubleshooting

Container takes too long to start

The first start can take 1-2 minutes as the container image is pulled. Subsequent starts are faster. If it takes more than 3 minutes, try refreshing.

"Unauthorized" error on Control UI

Make sure you're using the correct gateway token in the URL. Check your .dev.vars file for the GATEWAY_AUTH_TOKEN value.

Devices not showing in Admin Dashboard

The devices list caches every 30s. Click Refresh in the Devices tab for a fresh read. If still not showing, check /persist/status endpoint and verify R2 bucket name in wrangler.toml matches your actual bucket.

wrangler login fails

Try running wrangler login --browser or clear existing credentials with wrangler logout first. On corporate networks, you may need to configure proxy settings.

Deploy OpenClaw AI Gateway

openclaw-cf-demo-r2

Choose Your Deployment Path

Option 1: One-Click Deploy

Option 2: Manual Setup

1 Verify Your Access ~5 min

2 Prepare GitHub Account ~2 min

3 Prepare API Credentials ~10 min

4 Deploy to Cloudflare ~5 min

5 Access Your Deployment ~5 min

6 Explore & Cleanup ~10 min

1 Verify Your Access ~5 min

2 Environment Setup ~10 min

3 Clone & Install ~5 min

4 Create R2 Bucket & Configure Secrets ~10 min

5 Deploy & Access ~10 min

6 Explore & Cleanup ~10 min

Lab Complete!

Troubleshooting