An always-on OpenClaw worker in its own container on your own EU virtual machine — pinned at 2026.6.34, restarted when it falls over, health-checked every 30 seconds, and already wired to your Paperclip control plane when you first log in.
you.litwindow.ai
Rack your office — $29/moread the service record
PINNED 2026.6.34RESTARTS ITSELFYOUR OWN KEYSEU-HOSTED VM
The figures in this panel are illustrative sample data, not litwindow's measured performance or any customer's real usage.
DEMONSTRATION READOUT — YOUR WORKER, YOUR NUMBERS
OpenClaw is an open-source autonomous coding agent. You give it a job in plain language and it works on its own — reading files, running commands, editing code, opening pull requests — for as long as the job takes. It is the kind of agent you start and walk away from, which is exactly why the machine it runs on matters.
OpenClaw is an independent open-source project. litwindow did not write it and does not sell it. What litwindow sells is where it lives: a pinned image, a restart policy, a health check, custody of your keys, and a control plane that can already see it. The image every office runs is openclaw/openclaw:2026.6.34, the same tag on every machine we operate.
The complaint we heard most often while researching OpenClaw was not bad output. It was agents dying quietly: a container that exited hours ago looks exactly like a container with nothing to do, and you find out when the work doesn't arrive. A heartbeat is the whole answer to that, and a heartbeat needs somewhere to beat.
/healthz is probed every 30 secondsThe container, the gateway token, the volume, the health check and the Paperclip connection are built during your first boot. What is left for you is the part only you can do: prove you are the owner, and say what should pay for the thinking.
The numbers below are the ones in the compose file on your machine. You can read them over SSH and check us.
openclaw/openclaw:2026.6.34, pinned in our golden image and identical on every office. Upgrades ship as a new image, never as an unpinned pull.restart: unless-stopped, a /healthz check every 30 seconds, a 3 GB memory limit and a 2 GB Node heap ceiling, so one runaway job cannot take the rest of the office down with it./home/node/.openclaw. It survives container restarts and image upgrades, and it is in the nightly encrypted backup.openclaw-2 and openclaw-3 with the same shape and their own volumes, on the same VM.No, and we will not add it. Anthropic's terms restrict subscription auth to their own apps, so driving a Pro or Max login from a third-party harness breaks those terms and puts your account at risk. litwindow supports Anthropic API keys instead, which carry no such restriction. If you would rather spend a subscription than metered tokens, OpenClaw also runs on a GitHub Copilot subscription, which is sanctioned for agent use.
No. It binds the container network on port 18789 and is never published to the host or to a public port. The gateway refuses to bind inside a container without auth, so your VM mints a gateway token at first boot. That token stays on your machine; litwindow never receives it.
Docker restarts it. The container runs with restart: unless-stopped and a health check that probes /healthz every 30 seconds. Its state lives in a durable volume, so it comes back with its config, its sessions and any connected subscription intact rather than as a fresh install. The heartbeat is on your dashboard, so a worker that stays down is visible rather than silent.
Docker image openclaw/openclaw:2026.6.34, the same tag on every litwindow office. OpenClaw's git releases run ahead of its published images, and we track the published image. Upgrades happen when we bake a new golden image and roll it out, not as an unpinned pull that changes underneath you on a restart.
In Paperclip's own interface on your office subdomain: that is where you write tasks, assign them to OpenClaw, and read what it did. The litwindow dashboard is for the machine underneath — health, live logs, keys, SSH, plan, backups and export.
One on Solo at $29 a month, three on Team at $79 a month. The extra two run as their own containers with their own volumes on the same VM, in the same shape as the first. No second machine, and no second bill from us.
Every office ships with all of these mounted and wired to each other. You do not pick one.
One pinned worker, wired and running on your own VM, before you finish your coffee.
Rack your office — $29/mo