> ## Documentation Index
> Fetch the complete documentation index at: https://agdiai-597e782f.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Linux Server

# Linux Server

Run the Agdi 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

> [card] [Railway](https://agdiai-597e782f.mintlify.site/install/railway.md)
>
> One-click, browser setup

> [card] [Northflank](https://agdiai-597e782f.mintlify.site/install/northflank.md)
>
> One-click, browser setup

> [card] [DigitalOcean](https://agdiai-597e782f.mintlify.site/install/digitalocean.md)
>
> Simple paid VPS

> [card] [Oracle Cloud](https://agdiai-597e782f.mintlify.site/install/oracle.md)
>
> Always Free ARM tier

> [card] [Fly.io](https://agdiai-597e782f.mintlify.site/install/fly.md)
>
> Fly Machines

> [card] [Hetzner](https://agdiai-597e782f.mintlify.site/install/hetzner.md)
>
> Docker on Hetzner VPS

> [card] [GCP](https://agdiai-597e782f.mintlify.site/install/gcp.md)
>
> Compute Engine

> [card] [Azure](https://agdiai-597e782f.mintlify.site/install/azure.md)
>
> Linux VM

> [card] [exe.dev](https://agdiai-597e782f.mintlify.site/install/exe-dev.md)
>
> VM with HTTPS proxy

> [card] [Raspberry Pi](https://agdiai-597e782f.mintlify.site/install/raspberry-pi.md)
>
> ARM self-hosted

**AWS (EC2 / Lightsail / free tier)** also works well.
A community video walkthrough is available at
[x.com/techfrenAJ/status/2014934471095812547](https://x.com/techfrenAJ/status/2014934471095812547)
(community resource -- may become unavailable).

## How cloud setups work

* 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.
  If you bind to `lan` or `tailnet`, require `gateway.auth.token` or `gateway.auth.password`.

Related pages: [Gateway remote access](https://agdiai-597e782f.mintlify.site/gateway/remote.md), [Platforms hub](https://agdiai-597e782f.mintlify.site/platforms.md).

## 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.

Security model details: [Security](https://agdiai-597e782f.mintlify.site/gateway/security.md).

## 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.

Docs: [Nodes](https://agdiai-597e782f.mintlify.site/nodes.md), [Nodes CLI](https://agdiai-597e782f.mintlify.site/cli/nodes.md).

## 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:

```bash theme={"theme":{"light":"min-light","dark":"min-dark"}}
grep -q 'NODE_COMPILE_CACHE=/var/tmp/agdi-compile-cache' ~/.bashrc || cat >> ~/.bashrc <<'EOF'
export NODE_COMPILE_CACHE=/var/tmp/agdi-compile-cache
mkdir -p /var/tmp/agdi-compile-cache
export OPENCLAW_NO_RESPAWN=1
EOF
source ~/.bashrc
```

* `NODE_COMPILE_CACHE` improves repeated command startup times.
* `OPENCLAW_NO_RESPAWN=1` avoids extra startup overhead from a self-respawn path.
* First command run warms the cache; subsequent runs are faster.
* For Raspberry Pi specifics, see [Raspberry Pi](https://agdiai-597e782f.mintlify.site/install/raspberry-pi.md).

### systemd tuning checklist (optional)

For VM hosts using `systemd`, consider:

* Add service env for a stable startup path:
  * `OPENCLAW_NO_RESPAWN=1`
  * `NODE_COMPILE_CACHE=/var/tmp/agdi-compile-cache`
* Keep restart behavior explicit:
  * `Restart=always`
  * `RestartSec=2`
  * `TimeoutStartSec=90`
* Prefer SSD-backed disks for state/cache paths to reduce random-I/O cold-start penalties.

Example:

```bash theme={"theme":{"light":"min-light","dark":"min-dark"}}
sudo systemctl edit agdi
```

```ini theme={"theme":{"light":"min-light","dark":"min-dark"}}
[Service]
Environment=OPENCLAW_NO_RESPAWN=1
Environment=NODE_COMPILE_CACHE=/var/tmp/agdi-compile-cache
Restart=always
RestartSec=2
TimeoutStartSec=90
```

How `Restart=` policies help automated recovery:
[systemd can automate service recovery](https://www.redhat.com/en/blog/systemd-automate-recovery).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.