Oracle Cloud
Deploy OpenClaw on an Oracle Cloud Always Free Arm instance behind the open-source ControlClaw firewall, with one cloud-init script.
A new Oracle Cloud instance installs Docker, Node and ControlClaw from a cloud-init 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.
Oracle's Always Free tier includes Arm (Ampere A1) capacity, and both ControlClaw and OpenClaw publish Arm images, so this setup can run on it. Oracle sets the free limits; check them in your tenancy before you create the instance.
Create the instance
In the Oracle Cloud console, open Compute, then Instances, and click Create instance.
| Setting | Choose |
|---|---|
| Image | Canonical Ubuntu 24.04 |
| Shape | Ampere, VM.Standard.A1.Flex, with 4 GB of memory or more |
| Networking | A public subnet, so you can SSH in |
| SSH keys | Your public key |
| Advanced options, Management | Paste cloud-init script, with the script below |
#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>&1Click Create. The script takes a few minutes after the instance boots.
You don't need to open any port except SSH, which the default security list already allows. The panel and OpenClaw's Control UI listen on the instance's loopback, and you reach them through an SSH tunnel.
Check the install
ssh ubuntu@<instance_ip>
sudo tail -n 20 /root/controlclaw-up.log
sudo npx controlclaw statusEvery line of status should start with ✓. If the log stops half way, run
sudo 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 ubuntu@<instance_ip>On the instance, print the panel's link and OpenClaw's:
sudo npx controlclaw open
sudo grep "Control UI" /root/controlclaw-up.log- 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. - 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.


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

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.

Remove it
Terminate the instance in the console. To keep it and remove only ControlClaw:
sudo npx controlclaw uninstall --purge, then sudo docker compose -p openclaw down.
DigitalOcean
Deploy OpenClaw on a DigitalOcean Droplet behind the open-source ControlClaw firewall, with one user data script.
Railway
Run OpenClaw on Railway with the open-source ControlClaw firewall as its proxy. Two services, a private network, and every request OpenClaw makes in the firewall's log.