Important
View full deployment instructions in the Render docs.
OpenClaw Render Blueprint: This template defines a render.yaml file you can use to deploy OpenClaw on Render. It uses the official project's container image.
By default, this template uses the latest tag.
Override this by setting the OPENCLAW_VERSION environment variable to a specific version tag.
You can find all the latest Docker builds here.
- Fork the repo: Fork the render openclaw example repo by clicking here.
- Connect Blueprint: Connect your Blueprint by clicking here and selecting your repo. Specify the following configurations:
- Blueprint Name:
openclaw - Branch:
main - Blueprint Path:
render.yaml - API Key: Specify at least one API key provider. For OpenRouter, you can get yours here.
- Blueprint Name:
Follow the deployment instructions in the Render OpenClaw docs.
You will either:
- Auto-deploy your RenderClaw when creating the blueprint (see above)
- Manually-deploy your RenderClaw if a blueprint already exists
Find your OpenClaw deployment on render, and then:
- Under
Environment, findOPENCLAW_GATEWAY_TOKENand copy the value - Find the
External URLfor your deployment and open it in your browser - Paste the token into the
OPENCLAW_GATEWAY_TOKENfield on the landing page
Note the following:
- Valid token sets a signed, HTTP-only cookie (30-day expiry)
- Sessions persist across service restarts
Security:
- Gateway binds to loopback only (never directly exposed)
- Constant-time token comparison
- Rate limiting (5 attempts/minute per IP)
- Secure cookies (HTTPS only,
SameSite=Lax)
Override the OpenClaw version with a build argument:
docker build --build-arg OPENCLAW_VERSION=2026.2.3 -t openclaw-render .