Linux server

Linux server 문서는 OpenClaw 공식 문서(vps)를 한국어로 정리한 가이드입니다. Run OpenClaw on a Linux server or cloud VPS — provider picker, architecture, and tuning 명령·설정 키·코드 예시는 공식 문서를 그대로 보존하며, 해석과 절차 안내는 한국어로 제공합니다. 최종 동작은 설치된 CLI 버전과 공식 원문을 확인하세요.

핵심 요약

Run OpenClaw on a Linux server or cloud VPS — provider picker, architecture, and tuning

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

문서 구성

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

Pick a provider
How cloud setups work
Harden admin access first
Shared company agent on a VPS
Using nodes with a VPS
Startup tuning for small VMs and ARM hosts
systemd tuning checklist (optional)
관련 문서

상세 내용

본문

Run the OpenClaw Gateway on any Linux server or cloud VPS. This page helps you pick a provider, explains how cloud deployments work, and covers generic Linux tuning that applies everywhere.

Pick a provider

A community video walkthrough is available at x.com/techfrenAJ/status/2014934471095812547 (community resource -- may become unavailable).

How cloud setups work

If you bind to lan or tailnet, the Gateway requires a shared secret (gateway.auth.token or gateway.auth.password) unless auth is delegated to a trusted proxy.

주요 항목:

The Gateway runs on the VPS and owns state + workspace.
You connect from your laptop or phone via the Control UI or Tailscale/SSH.
Treat the VPS as the source of truth and back up the state + workspace regularly.
Secure default: keep the Gateway on loopback and access it via SSH tunnel or Tailscale Serve.

Harden admin access first

Before you install OpenClaw on a public VPS, decide how you want to administer the box itself.

주요 항목:

For Tailnet-only admin access: install Tailscale first, join the VPS to your
Without Tailscale: apply the equivalent hardening for your SSH path before
This is separate from Gateway access. You can still keep OpenClaw bound to

Shared company agent on a VPS

Running a single agent for a team is a valid setup when every user is in the same trust boundary and the agent is business-only.

주요 항목:

Keep it on a dedicated runtime (VPS/VM/container + dedicated OS user/accounts).
Do not sign that runtime into personal Apple/Google accounts or personal browser/password-manager profiles.
If users are adversarial to each other, split by gateway/host/OS user.

Using nodes with a VPS

You can keep the Gateway in the cloud and pair nodes on your local devices (Mac/iOS/Android/headless). Nodes provide local screen/camera/canvas and system.run capabilities while the Gateway stays in the cloud.

Startup tuning for small VMs and ARM hosts

If CLI commands feel slow on low-power VMs (or ARM hosts), enable Node's module compile cache:

주요 항목:

NODE_COMPILE_CACHE improves repeated command startup times; the first run warms the cache.
OPENCLAW_NO_RESPAWN=1 keeps routine Gateway restarts in-process, which avoids extra process handoffs and keeps PID tracking simple on small hosts.
For Raspberry Pi specifics, see Raspberry Pi.

grep -q 'NODE_COMPILE_CACHE=/var/tmp/openclaw-compile-cache' ~/.bashrc || cat >> ~/.bashrc <<'EOF'

mkdir -p /var/tmp/openclaw-compile-cache

EOF
source ~/.bashrc

systemd tuning checklist (optional)

NODE_COMPILE_CACHE=/var/tmp/openclaw-compile-cache

주요 항목:

Service env for a stable startup path: OPENCLAW_NO_RESPAWN=1 and
Explicit restart behavior: Restart=always, RestartSec=2, TimeoutStartSec=90
SSD-backed disks for state/cache paths to reduce random-I/O cold-start penalties.

systemctl --user edit openclaw-gateway.service

[Service]
Environment=OPENCLAW_NO_RESPAWN=1
Environment=NODE_COMPILE_CACHE=/var/tmp/openclaw-compile-cache
Restart=always
RestartSec=2
TimeoutStartSec=90

실습 체크리스트

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

자주 쓰는 명령·설정 예시

grep -q 'NODE_COMPILE_CACHE=/var/tmp/openclaw-compile-cache' ~/.bashrc || cat >> ~/.bashrc <<'EOF'

mkdir -p /var/tmp/openclaw-compile-cache

EOF
source ~/.bashrc

systemctl --user edit openclaw-gateway.service

[Service]
Environment=OPENCLAW_NO_RESPAWN=1
Environment=NODE_COMPILE_CACHE=/var/tmp/openclaw-compile-cache
Restart=always
RestartSec=2
TimeoutStartSec=90

Linux server

핵심 요약

Run OpenClaw on a Linux server or cloud VPS — provider picker, architecture, and tuning

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

문서 구성

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

Pick a provider
How cloud setups work
Harden admin access first
Shared company agent on a VPS
Using nodes with a VPS
Startup tuning for small VMs and ARM hosts
systemd tuning checklist (optional)
관련 문서

상세 내용

본문

Run the OpenClaw Gateway on any Linux server or cloud VPS. This page helps you pick a provider, explains how cloud deployments work, and covers generic Linux tuning that applies everywhere.

Pick a provider

A community video walkthrough is available at x.com/techfrenAJ/status/2014934471095812547 (community resource -- may become unavailable).

How cloud setups work

If you bind to lan or tailnet, the Gateway requires a shared secret (gateway.auth.token or gateway.auth.password) unless auth is delegated to a trusted proxy.

주요 항목:

The Gateway runs on the VPS and owns state + workspace.
You connect from your laptop or phone via the Control UI or Tailscale/SSH.
Treat the VPS as the source of truth and back up the state + workspace regularly.
Secure default: keep the Gateway on loopback and access it via SSH tunnel or Tailscale Serve.

Harden admin access first

Before you install OpenClaw on a public VPS, decide how you want to administer the box itself.

주요 항목:

For Tailnet-only admin access: install Tailscale first, join the VPS to your
Without Tailscale: apply the equivalent hardening for your SSH path before
This is separate from Gateway access. You can still keep OpenClaw bound to

Shared company agent on a VPS

Running a single agent for a team is a valid setup when every user is in the same trust boundary and the agent is business-only.

주요 항목:

Keep it on a dedicated runtime (VPS/VM/container + dedicated OS user/accounts).
Do not sign that runtime into personal Apple/Google accounts or personal browser/password-manager profiles.
If users are adversarial to each other, split by gateway/host/OS user.

Using nodes with a VPS

Startup tuning for small VMs and ARM hosts

If CLI commands feel slow on low-power VMs (or ARM hosts), enable Node's module compile cache:

주요 항목:

NODE_COMPILE_CACHE improves repeated command startup times; the first run warms the cache.
OPENCLAW_NO_RESPAWN=1 keeps routine Gateway restarts in-process, which avoids extra process handoffs and keeps PID tracking simple on small hosts.
For Raspberry Pi specifics, see Raspberry Pi.

grep -q 'NODE_COMPILE_CACHE=/var/tmp/openclaw-compile-cache' ~/.bashrc || cat >> ~/.bashrc <<'EOF'

mkdir -p /var/tmp/openclaw-compile-cache

EOF
source ~/.bashrc

systemd tuning checklist (optional)

NODE_COMPILE_CACHE=/var/tmp/openclaw-compile-cache

주요 항목:

Service env for a stable startup path: OPENCLAW_NO_RESPAWN=1 and
Explicit restart behavior: Restart=always, RestartSec=2, TimeoutStartSec=90
SSD-backed disks for state/cache paths to reduce random-I/O cold-start penalties.

systemctl --user edit openclaw-gateway.service

[Service]
Environment=OPENCLAW_NO_RESPAWN=1
Environment=NODE_COMPILE_CACHE=/var/tmp/openclaw-compile-cache
Restart=always
RestartSec=2
TimeoutStartSec=90

실습 체크리스트

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

자주 쓰는 명령·설정 예시

grep -q 'NODE_COMPILE_CACHE=/var/tmp/openclaw-compile-cache' ~/.bashrc || cat >> ~/.bashrc <<'EOF'

mkdir -p /var/tmp/openclaw-compile-cache

EOF
source ~/.bashrc

systemctl --user edit openclaw-gateway.service

[Service]
Environment=OPENCLAW_NO_RESPAWN=1
Environment=NODE_COMPILE_CACHE=/var/tmp/openclaw-compile-cache
Restart=always
RestartSec=2
TimeoutStartSec=90

Linux server

핵심 요약

문서 구성

상세 내용

본문

Pick a provider

How cloud setups work

Harden admin access first

Shared company agent on a VPS

Using nodes with a VPS

Startup tuning for small VMs and ARM hosts

systemd tuning checklist (optional)

관련 문서

실습 체크리스트

자주 쓰는 명령·설정 예시

관련 링크

관련 가이드

Linux server

핵심 요약

문서 구성

상세 내용

본문

Pick a provider

How cloud setups work

Harden admin access first

Shared company agent on a VPS

Using nodes with a VPS

Startup tuning for small VMs and ARM hosts

systemd tuning checklist (optional)

관련 문서

실습 체크리스트

자주 쓰는 명령·설정 예시

관련 링크

관련 가이드