Guide

Add a VPS to your fleet.

Any Linux server can be a fleet machine: a small runtime keeps your agent sessions alive on it, and it shows up in the same rail as your desktop and laptop. About five minutes, outbound connections only — you never open a port to the internet.

  1. 1. Provision a server
  2. 2. Install git and an agent CLI
  3. 3. Install the runtime
  4. 4. Sign in from any browser
  5. 5. Verify and name it

1Provision a server

Any provider works — Hetzner, DigitalOcean, Vultr, Linode, AWS, whatever you already use. Pick a recent Ubuntu or Debian image. Agents are mostly CPU-and-RAM bound while they work, so 2 vCPUs and 4 GB of RAM is a comfortable floor; the smallest instances work for light use.

Choose an x86_64 instance. ARM servers (AWS Graviton, Hetzner CAX, Ampere) aren't supported yet — ARM builds are coming.

No firewall changes are needed. The runtime only dials out over HTTPS (port 443) and listens on localhost — nothing is exposed to the internet.

2Install git and an agent CLI

Agents run in ordinary terminal sessions on the machine, so the tools they use must be installed there: git, plus at least one agent CLI — Claude Code, Codex, Cursor Agent, OpenCode, or PI. For example, on Ubuntu with Claude Code:

$ sudo apt-get update && sudo apt-get install -y git curl
$ curl -fsSL https://deb.nodesource.com/setup_22.x | sudo bash - && sudo apt-get install -y nodejs
$ npm install -g @anthropic-ai/claude-code

Install whichever CLIs you actually use — the fleet doesn't care which. You'll authenticate the agent CLI itself the first time you start a session on this machine.

3Install the runtime

Download the installer and run it. It fetches the latestruntime-host build, verifies its checksum, installs it under ~/.aulay, and registers a systemd service so the runtime starts on boot and restarts if it ever crashes.

$ curl -fsSL https://market.aulay.io/runtime.sh -o runtime.sh
$ sh runtime.sh

Download first rather than piping to sh — the next step is an interactive sign-in that needs your terminal. Running as a regular user installs a per-user service; running as root installs a system service.

4Sign in from any browser

The installer prints a sign-in link. Open it in a browser on any device — your laptop or your phone, it doesn't have to be the server — sign in to your Aulay account, and the page shows a one-time code. Paste that code back into the terminal prompt. That's the whole enrollment: the server mints its own runtime credentials and connects to the fabric.

5Verify and name it

Check the runtime is healthy, then open Aulay on any device — the new machine is in your fleet rail, ready for sessions.

$ sh runtime.sh status

Two finishing touches worth doing:

  • Installed as a regular user? Enable lingering so the service keeps running after you log out of SSH: sudo loginctl enable-linger $USER
  • Name the machine. The fleet shows the hostname by default. To use a friendlier name, set AULAY_NAME="vps-01" in the environment before running the installer.

Good to know

Updates are automatic
The runtime updates itself between sessions. To force one: sh runtime.sh update. To remove everything: sh runtime.sh remove.
Network footprint
Outbound HTTPS/WSS to *.aulay.io (and the release CDN for downloads). Local ports bind to 127.0.0.1 only. Nothing inbound, no VPN, no port forwarding.
Containers
Inside a container, run the runtime in the foreground instead of installing a service: sh runtime.sh run.
Where things live
Binary, config, and credentials under ~/.aulay; agent workspaces under ~/.aulay/workspace. Set AULAY_WORKSPACE before installing to put work somewhere else (a bigger disk, for example).

That's a fleet machine.

Kick off an agent on it from your desktop, close the laptop, and check on it from your phone — the session lives on the VPS now.

Open Aulay