Akamai / Linode

Deploy OpenClaw on an Akamai (Linode) server behind the open-source ControlClaw firewall, with one user data script.

A new Linode installs Docker, Node and ControlClaw from a user data script, then runs npx controlclaw up --all. That starts the firewall and a new OpenClaw as two containers. OpenClaw's container sits on a network whose only other member is the firewall, so every request it makes, its shell commands included, goes through the firewall.

Create the Linode

In Akamai Cloud Manager, click Create, then Linode.

SettingChoose
RegionOne that supports the Metadata service (user data)
ImageUbuntu 24.04 LTS
PlanShared CPU, Linode 4 GB or larger
SSH KeysYour key
Add User DataThe script below
User data
#cloud-config
runcmd:
  - curl -fsSL https://get.docker.com | sh
  - curl -fsSL https://deb.nodesource.com/setup_22.x | bash -
  - apt-get install -y nodejs
  - npx --yes controlclaw up --all > /root/controlclaw-up.log 2>&1

Click Create Linode. The script takes a few minutes after the Linode boots.

Leave the ports closed

You don't need to open any port except SSH. The panel and OpenClaw's Control UI listen on the Linode's loopback, and you reach them through an SSH tunnel. If you add a Cloud Firewall, allow only port 22 in.

Check the install

ssh root@<linode_ip>
tail -n 20 /root/controlclaw-up.log
npx controlclaw status

Every line of status should start with ✓. If the log stops half way, run npx controlclaw up --all again: it checks what is there and goes on.

Open the panel and OpenClaw

On your computer, open a tunnel to both:

ssh -L 8800:127.0.0.1:8800 -L 18789:127.0.0.1:18789 root@<linode_ip>

On the Linode, print the panel's link and OpenClaw's:

npx controlclaw open
grep "Control UI" /root/controlclaw-up.log
  1. Open the panel's link (http://127.0.0.1:8800/#setup=…) and set the admin password. Until you do, anyone with that link can set it.
  2. Open OpenClaw's Control UI link (http://127.0.0.1:18789/#token=…). It starts on Model Setup: pick your provider and add your key. You can also add the key in the firewall's panel, so OpenClaw never holds it.

The panel's first page: the setup token is filled in from the link, and you choose the admin password

OpenClaw's Control UI on its first run, on Model Setup

Ask OpenClaw something that needs the web. Its requests show in the panel's Overview, under the agent's name.

The panel's Overview with OpenClaw's requests in Live requests

Lock it down

A new firewall allows every site and logs it. In the panel, open Internet access and set Every other site to Block. Keys and bots you add in the panel keep working, because the firewall adds a rule for each. A key you keep in OpenClaw needs its provider's host allowed.

Internet access in the panel, with Every other site set to Allow or Block

Remove it

Delete the Linode in Cloud Manager. To keep it and remove only ControlClaw: npx controlclaw uninstall --purge, then docker compose -p openclaw down.

On this page