Skip to content
This repository was archived by the owner on Feb 10, 2026. It is now read-only.
/ render_clawdbot Public archive

Run Clawdbot on Render with your own web UI.

Notifications You must be signed in to change notification settings

ojusave/render_clawdbot

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

🦞 OpenClaw on Render


⚠️ ARCHIVED

This repository is archived. Please use the official Render deployment instead:


Deploy OpenClaw on Render with a built-in installer and a proxied Control UI (including WebSockets).

Deploy to Render

Docs · Discord · GitHub

UI preview

OpenClaw on Render UI (preview 1)

OpenClaw on Render UI (preview 2)

What you get

  • Install Wizard at /install (password protected)
  • Control UI at / and /openclaw (reverse-proxied, including WebSockets)
  • Persistent disk mounted at /data for state + workspace
  • Export / Import backups to migrate deployments

Installation

Plan requirement: This Blueprint targets Render's Standard plan (paid) because it uses a persistent disk at /data. See: https://docs.render.com/pricing#services.

  1. Click the Deploy to Render button above.
  2. Render will detect render.yaml and automatically create the web service and persistent disk.
  3. When prompted during deployment, set the required environment variable:
    • RENDER_SETUP_PASSWORD: Choose a secure password to protect the installer (required)
  4. Wait for the deployment to complete. Render will automatically generate RENDER_GATEWAY_TOKEN for you.

Configuration

After deployment, you need to configure OpenClaw using the install wizard:

  1. Access the installer: Navigate to https://<your-service>.onrender.com/install
  2. Authenticate: The installer uses HTTP Basic Auth:
    • Username: any value (can be left blank)
    • Password: the value you set for RENDER_SETUP_PASSWORD
  3. Complete the setup: Follow the install wizard to configure OpenClaw:
    • Select your authentication group and method
    • Configure any required settings
    • The installer will set up OpenClaw with your preferences

Usage

Once configured, you can access and use OpenClaw:

  • Control UI: Navigate to https://<your-service>.onrender.com/ or https://<your-service>.onrender.com/openclaw
  • The Control UI is reverse-proxied and includes full WebSocket support
  • All state and workspace data is persisted on the disk at /data

Persistence

This template stores state and workspace on the persistent disk:

  • OPENCLAW_STATE_DIR=/data/.openclaw
  • OPENCLAW_WORKSPACE_DIR=/data/workspace

Backups

  • Download: GET /install/export (Basic Auth) → .tar.gz
  • Upload: POST /install/api/import (Basic Auth) → restores .openclaw/ + workspace/ into /data

Environment variables

  • Required
    • RENDER_SETUP_PASSWORD: protects /install
  • Generated by Blueprint
    • RENDER_GATEWAY_TOKEN: gateway admin token used by the Control UI (auto-generated in render.yaml)
  • Optional (advanced)
    • OPENCLAW_GIT_REF: Docker build arg to pin the OpenClaw version (tag/branch/commit)
  • Optional (branding)
    • RENDER_LOGO_FILE: filename inside public/ to show in the header (default: Render logo - Black.jpg)
    • RENDER_DEPLOY_URL: URL used by the "Deploy on Render" button (default: https://render.com/deploy?repo=https://github.com/ojusave/render_clawdbot)
  • Optional (gateway startup tolerance)
    • GATEWAY_READY_TIMEOUT_MS (default 60000)
    • GATEWAY_READY_PATH (default /healthz)
    • GATEWAY_READY_POLL_MS (default 300)
    • GATEWAY_READY_REQ_TIMEOUT_MS (default 2000)

Troubleshooting

  • WebSocket closes (code 1008) / "proxy headers detected": this wrapper strips Forwarded / X-Forwarded-* headers when proxying to the internal loopback gateway, because forwarding them can make local clients appear "remote behind an untrusted proxy".

Contributing

Thanks for helping improve this repo.

What's welcome

  • Bug fixes
  • Documentation improvements
  • Small, focused features that improve reliability on Render

Fixes and improvements are welcome. If you're unsure about an approach, open an issue or draft PR.

Development

  • Run locally: npm install && npm run dev
  • Lint: npm run lint

Guidelines

  • Keep changes small and easy to review.
  • Prefer backwards-compatible changes to the Render Blueprint (render.yaml).
  • Avoid committing secrets (tokens, API keys, .env files).

License

MIT License

Copyright (c) 2026 ojusave

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

About

Run Clawdbot on Render with your own web UI.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •