Render

Deploy on Render using Infrastructure as Code (render.yaml Blueprint). One-click deploy with persistent disk.

Render is a modern PaaS that deploys OpenClaw using Infrastructure as Code via render.yaml Blueprints. The one-click 'Deploy to Render' button creates a web service from the OpenClaw Docker image, provisions a persistent disk, sets up HTTPS with automatic certificate renewal, and configures health checks — all from a declarative YAML file. No manual server configuration required. The deployment experience is similar to Railway but with a stronger emphasis on IaC principles. The render.yaml Blueprint in the OpenClaw repo defines the service configuration — compute type, disk size, environment variables, health check endpoints, and auto-deploy settings. When you click 'Deploy to Render', it reads this Blueprint and provisions everything declaratively. You set SETUP_PASSWORD when prompted, wait for the build (~3-5 minutes), and complete the web-based setup wizard at /setup. Render's free tier is a notable advantage for evaluation. Free web services get 750 hours/month of compute, which is enough to run OpenClaw part-time. However, free services spin down after 15 minutes of inactivity and take 30-60 seconds to cold-start — not ideal for a messaging bot that needs to respond instantly. For always-on use, the Starter plan provides persistent services starting at $7/month. Persistent storage uses Render's managed disks, mounted at /data in the container. Unlike ephemeral container filesystems, disk data survives redeploys and restarts. The Blueprint configures a 1GB disk by default, expandable from the dashboard. Render also supports automatic deploys from a connected GitHub repo — push to main and Render rebuilds and deploys automatically. Render's health check integration is well-designed for OpenClaw. The Blueprint configures /healthz as the health check endpoint, and Render automatically restarts the service if health checks fail. Combined with automatic HTTPS, zero-downtime deploys, and built-in logging, Render provides a production-quality hosting environment with minimal operational overhead. The main limitation, like Railway, is no SSH access and no Docker-in-Docker for agent sandboxing.

Tags: paas, one-click, iac, blueprint

Use Cases

  • IaC-focused teams who want declarative infrastructure defined in render.yaml
  • Non-technical users who want one-click cloud deployment with the option of a free tier for evaluation
  • Small teams that need automatic HTTPS, health checks, and zero-downtime deploys without server management
  • Developers who want GitHub-connected auto-deploy for continuous deployment workflows
  • Quick evaluation of OpenClaw before committing to a more permanent deployment

Tips

  • Upgrade to Starter plan ($7/mo) for always-on services — free tier's spin-down makes messaging bots unreliable
  • Set SETUP_PASSWORD before deployment to secure the web setup wizard
  • Use Render's built-in log viewer and shell (when available) for debugging without SSH
  • Configure the persistent disk at /data to preserve OpenClaw state across deployments
  • Enable auto-deploy from your GitHub repo's main branch for seamless updates
  • Use Render's health check integration with /healthz for automatic restarts on failures
  • Set environment variables in the Render dashboard rather than in config files for security

Known Issues & Gotchas

  • Free tier services spin down after 15 minutes of inactivity — cold starts take 30-60 seconds, causing delayed bot responses
  • No SSH access to the container — you can't install system packages or debug at the OS level
  • Agent sandboxing (Docker-in-Docker) is not available on Render — tool execution runs in the gateway container
  • The persistent disk is region-locked — you can't move it between regions after creation
  • Auto-deploy on push can cause unexpected redeployments if you push non-production changes — configure branch filters
  • The render.yaml Blueprint must be in the repo root for the Deploy to Render button to work
  • Outbound bandwidth is metered — heavy API usage or file downloads may incur additional charges

Alternatives

  • Railway
  • Fly.io
  • Northflank
  • Hetzner VPS
  • Docker (self-hosted)

Community Feedback

Render's Blueprint system is the cleanest IaC for simple deployments. One YAML file defines everything. Push to deploy. Health checks included.

— Reddit r/selfhosted

Render's free tier spins down after inactivity. Your Telegram bot goes silent for 30-60 seconds on cold start. Pay for the Starter plan if you want instant responses.

— Reddit r/AI_Agents

For PaaS options, Render is the middle ground between Railway's simplicity and Fly.io's power. Good docs, reasonable pricing, and the Blueprint system is genuinely useful.

— Reddit r/Hosting

Frequently Asked Questions

Is Render's free tier enough for OpenClaw?

For evaluation only. Free services spin down after 15 minutes of inactivity, causing 30-60 second cold starts. Your messaging bot will be unresponsive during cold starts. Use the Starter plan ($7/mo) for always-on availability.

What's the render.yaml Blueprint?

It's Render's Infrastructure as Code format — a YAML file that declares your service configuration (compute type, disk, env vars, health checks). The OpenClaw repo includes a pre-configured Blueprint that the Deploy to Render button reads.

How do I update OpenClaw on Render?

If auto-deploy is enabled, push to your connected GitHub repo and Render rebuilds automatically. Otherwise, trigger a manual deploy from the Render dashboard. The persistent disk preserves your config across deploys.

Can I use custom domains?

Yes, on paid plans. Add your domain in the Render dashboard and configure a CNAME record. Render provides automatic SSL certificate provisioning and renewal for custom domains.

Is there SSH access?

Render provides a limited web shell for some plans but no full SSH access. For debugging, use the log viewer in the dashboard. If you need shell access for advanced troubleshooting, consider a VPS deployment.

How does the persistent disk work?

Render provisions a managed SSD disk mounted at /data in your container. Data persists across deploys and restarts. The default size is 1GB (expandable from the dashboard). It's region-locked to your service's datacenter.