Render

Render 문서는 OpenClaw 공식 문서(install/render)를 한국어로 정리한 가이드입니다. Deploy OpenClaw on Render with Infrastructure-as-Code 명령·설정 키·코드 예시는 공식 문서를 그대로 보존하며, 해석과 절차 안내는 한국어로 제공합니다. 최종 동작은 설치된 CLI 버전과 공식 원문을 확인하세요.

핵심 요약

Deploy OpenClaw on Render with Infrastructure-as-Code

한국어 가이드 범위: install/render 경로의 설정·명령·제약·예시를 학습용으로 재구성합니다.

문서 구성

공식 문서의 주요 섹션은 다음과 같습니다.

사전 요구사항
Deploy
The Blueprint
Choosing a plan
After deployment
Access the Control UI
Logs
Shell access
환경 변수
Auto-deploy
Custom domain
Scaling
Backups and migration
트러블슈팅
Service will not start
Slow cold starts (free tier)
Data loss after redeploy
Health check failures
다음 단계

상세 내용

본문

Deploy OpenClaw on Render using the repo's render.yaml Blueprint. It declares the service, disk, and environment variables in one file.

사전 요구사항

주요 항목:

A Render account (free tier available)
An API key from your preferred model provider

Deploy

Deploy to Render

The Blueprint

주요 항목:

type: web
key: OPENCLAW_GATEWAY_PORT
key: OPENCLAW_STATE_DIR
key: OPENCLAW_WORKSPACE_DIR
key: OPENCLAW_GATEWAY_TOKEN

Feature	Purpose
`runtime: docker`	Builds from the repo's Dockerfile
`healthCheckPath`	Render monitors `/health` and restarts unhealthy instances
`generateValue: true`	Auto-generates a cryptographically secure value
`disk`	Persistent storage that survives redeploys

services:
  - type: web
    name: openclaw
    runtime: docker
    plan: starter
    healthCheckPath: /health
    envVars:
      - key: OPENCLAW_GATEWAY_PORT
        value: "8080"
      - key: OPENCLAW_STATE_DIR
        value: /data/.openclaw
      - key: OPENCLAW_WORKSPACE_DIR
        value: /data/workspace
      - key: OPENCLAW_GATEWAY_TOKEN
        generateValue: true # auto-generates a secure token
    disk:
      name: openclaw-data
      mountPath: /data
      sizeGB: 1

Choosing a plan

The Blueprint defaults to starter. To use the free tier, change plan: free in your fork's render.yaml — note that with no persistent disk, OpenClaw state resets on each deploy.

Plan	Spin-down	Disk	Best for
Free	After 15 min idle	Not available	Testing, demos
Starter	Never	1GB+	Personal use, small teams
Standard+	Never	1GB+	Production, multiple channels

After deployment

이 섹션의 세부 항목은 공식 문서 After deployment를 참고하세요.

Access the Control UI

The web dashboard is available at https://.onrender.com/. Connect using the shared secret: the auto-generated OPENCLAW_GATEWAY_TOKEN (find it in Dashboard → your service → Environment), or your password if you switched to password auth.

Logs

Dashboard → your service → Logs shows build logs (Docker image creation), deploy logs (service startup), and runtime logs (application output).

Shell access

Dashboard → your service → Shell opens a shell session. The persistent disk is mounted at /data.

환경 변수

Edit variables in Dashboard → your service → Environment. Changes trigger an automatic redeploy.

Auto-deploy

Render redeploys automatically when the connected repo's branch gets a new commit. If you deployed straight from openclaw/openclaw instead of your own fork, you have no push access to trigger that, so update by running a manual Blueprint sync from the Dashboard, or point the service at your own fork.

Custom domain

Dashboard → your service → Settings → Custom Domains 2. Add your domain 3. Configure DNS as instructed (CNAME to *.onrender.com) 4. Render provisions a TLS certificate automatically

Scaling

주요 항목:

Vertical: change the plan for more CPU/RAM. Usually sufficient for OpenClaw.
Horizontal: increase instance count (Standard plan and above). Requires sticky sessions or external state management since OpenClaw keeps runtime state on the local disk.

Backups and migration

From the Render Dashboard shell, export state, config, auth profiles, and workspace at any time:

openclaw backup create

트러블슈팅

이 섹션의 세부 항목은 공식 문서 트러블슈팅를 참고하세요.

Service will not start

Check the deploy logs in the Render Dashboard. Common issues:

주요 항목:

Missing OPENCLAW_GATEWAY_TOKEN — verify it is set in Dashboard → Environment
Port mismatch — ensure OPENCLAW_GATEWAY_PORT=8080 so the gateway binds to the port Render expects

Slow cold starts (free tier)

Free tier services spin down after 15 minutes of inactivity; the first request after spin-down takes a few seconds while the container starts. Upgrade to Starter for always-on.

Data loss after redeploy

Happens on the free tier (no persistent disk). Upgrade to a paid plan, or regularly export a backup with openclaw backup create from the Render shell.

Health check failures

If builds succeed but deploys fail, the service may be taking too long to start or /health may not be reachable. Check:

주요 항목:

Build logs for errors
Whether the container runs locally with docker build && docker run

다음 단계

주요 항목:

Set up messaging channels: Channels
Configure the Gateway: Gateway configuration
Keep OpenClaw up to date: Updating

실습 체크리스트

공식 문서와 로컬 버전을 대조합니다: https://docs.openclaw.ai/install/render
관련 CLI는 openclaw --help 및 하위 명령 --help로 옵션을 확인합니다.
설정 변경 시 openclaw config / openclaw doctor로 유효성을 검사합니다.
Gateway·채널·플러그인 변경 후에는 필요 시 Gateway를 재시작합니다.

자주 쓰는 명령·설정 예시

services:
  - type: web
    name: openclaw
    runtime: docker
    plan: starter
    healthCheckPath: /health
    envVars:
      - key: OPENCLAW_GATEWAY_PORT
        value: "8080"
      - key: OPENCLAW_STATE_DIR
        value: /data/.openclaw
      - key: OPENCLAW_WORKSPACE_DIR
        value: /data/workspace
      - key: OPENCLAW_GATEWAY_TOKEN
        generateValue: true # auto-generates a secure token
    disk:
      name: openclaw-data
      mountPath: /data
      sizeGB: 1

openclaw backup create

Render

핵심 요약

Deploy OpenClaw on Render with Infrastructure-as-Code

한국어 가이드 범위: install/render 경로의 설정·명령·제약·예시를 학습용으로 재구성합니다.

문서 구성

공식 문서의 주요 섹션은 다음과 같습니다.

사전 요구사항
Deploy
The Blueprint
Choosing a plan
After deployment
Access the Control UI
Logs
Shell access
환경 변수
Auto-deploy
Custom domain
Scaling
Backups and migration
트러블슈팅
Service will not start
Slow cold starts (free tier)
Data loss after redeploy
Health check failures
다음 단계

상세 내용

본문

Deploy OpenClaw on Render using the repo's render.yaml Blueprint. It declares the service, disk, and environment variables in one file.

사전 요구사항

주요 항목:

A Render account (free tier available)
An API key from your preferred model provider

Deploy

Deploy to Render

The Blueprint

주요 항목:

type: web
key: OPENCLAW_GATEWAY_PORT
key: OPENCLAW_STATE_DIR
key: OPENCLAW_WORKSPACE_DIR
key: OPENCLAW_GATEWAY_TOKEN

Feature	Purpose
`runtime: docker`	Builds from the repo's Dockerfile
`healthCheckPath`	Render monitors `/health` and restarts unhealthy instances
`generateValue: true`	Auto-generates a cryptographically secure value
`disk`	Persistent storage that survives redeploys

services:
  - type: web
    name: openclaw
    runtime: docker
    plan: starter
    healthCheckPath: /health
    envVars:
      - key: OPENCLAW_GATEWAY_PORT
        value: "8080"
      - key: OPENCLAW_STATE_DIR
        value: /data/.openclaw
      - key: OPENCLAW_WORKSPACE_DIR
        value: /data/workspace
      - key: OPENCLAW_GATEWAY_TOKEN
        generateValue: true # auto-generates a secure token
    disk:
      name: openclaw-data
      mountPath: /data
      sizeGB: 1

Choosing a plan

The Blueprint defaults to starter. To use the free tier, change plan: free in your fork's render.yaml — note that with no persistent disk, OpenClaw state resets on each deploy.

Plan	Spin-down	Disk	Best for
Free	After 15 min idle	Not available	Testing, demos
Starter	Never	1GB+	Personal use, small teams
Standard+	Never	1GB+	Production, multiple channels

After deployment

이 섹션의 세부 항목은 공식 문서 After deployment를 참고하세요.

Access the Control UI

Logs

Dashboard → your service → Logs shows build logs (Docker image creation), deploy logs (service startup), and runtime logs (application output).

Shell access

Dashboard → your service → Shell opens a shell session. The persistent disk is mounted at /data.

환경 변수

Edit variables in Dashboard → your service → Environment. Changes trigger an automatic redeploy.

Auto-deploy

Custom domain

Dashboard → your service → Settings → Custom Domains 2. Add your domain 3. Configure DNS as instructed (CNAME to *.onrender.com) 4. Render provisions a TLS certificate automatically

Scaling

주요 항목:

Vertical: change the plan for more CPU/RAM. Usually sufficient for OpenClaw.
Horizontal: increase instance count (Standard plan and above). Requires sticky sessions or external state management since OpenClaw keeps runtime state on the local disk.

Backups and migration

From the Render Dashboard shell, export state, config, auth profiles, and workspace at any time:

openclaw backup create

트러블슈팅

이 섹션의 세부 항목은 공식 문서 트러블슈팅를 참고하세요.

Service will not start

Check the deploy logs in the Render Dashboard. Common issues:

주요 항목:

Missing OPENCLAW_GATEWAY_TOKEN — verify it is set in Dashboard → Environment
Port mismatch — ensure OPENCLAW_GATEWAY_PORT=8080 so the gateway binds to the port Render expects

Slow cold starts (free tier)

Free tier services spin down after 15 minutes of inactivity; the first request after spin-down takes a few seconds while the container starts. Upgrade to Starter for always-on.

Data loss after redeploy

Happens on the free tier (no persistent disk). Upgrade to a paid plan, or regularly export a backup with openclaw backup create from the Render shell.

Health check failures

If builds succeed but deploys fail, the service may be taking too long to start or /health may not be reachable. Check:

주요 항목:

Build logs for errors
Whether the container runs locally with docker build && docker run

다음 단계

주요 항목:

Set up messaging channels: Channels
Configure the Gateway: Gateway configuration
Keep OpenClaw up to date: Updating

실습 체크리스트

공식 문서와 로컬 버전을 대조합니다: https://docs.openclaw.ai/install/render
관련 CLI는 openclaw --help 및 하위 명령 --help로 옵션을 확인합니다.
설정 변경 시 openclaw config / openclaw doctor로 유효성을 검사합니다.
Gateway·채널·플러그인 변경 후에는 필요 시 Gateway를 재시작합니다.

자주 쓰는 명령·설정 예시

services:
  - type: web
    name: openclaw
    runtime: docker
    plan: starter
    healthCheckPath: /health
    envVars:
      - key: OPENCLAW_GATEWAY_PORT
        value: "8080"
      - key: OPENCLAW_STATE_DIR
        value: /data/.openclaw
      - key: OPENCLAW_WORKSPACE_DIR
        value: /data/workspace
      - key: OPENCLAW_GATEWAY_TOKEN
        generateValue: true # auto-generates a secure token
    disk:
      name: openclaw-data
      mountPath: /data
      sizeGB: 1

openclaw backup create

Render

핵심 요약

문서 구성

상세 내용

본문

사전 요구사항

Deploy

The Blueprint

Choosing a plan

After deployment

Access the Control UI

Logs

Shell access

환경 변수

Auto-deploy

Custom domain

Scaling

Backups and migration

트러블슈팅

Service will not start

Slow cold starts (free tier)

Data loss after redeploy

Health check failures

다음 단계

실습 체크리스트

자주 쓰는 명령·설정 예시

관련 링크

관련 가이드

Render

핵심 요약

문서 구성

상세 내용

본문

사전 요구사항

Deploy

The Blueprint

Choosing a plan

After deployment

Access the Control UI

Logs

Shell access

환경 변수

Auto-deploy

Custom domain

Scaling

Backups and migration

트러블슈팅

Service will not start

Slow cold starts (free tier)

Data loss after redeploy

Health check failures

다음 단계

실습 체크리스트

자주 쓰는 명령·설정 예시

관련 링크

관련 가이드