🖥️ VEP Compute Node Setup Guide

Connect your own GPU hardware to VEP and run AI inference locally — with full E2E encryption.

Use the text pairing code, not just the QR. In the VEP dashboard, every pending node shows both a QR and a text code. For terminal setup, always run vep-node pair YOUR_CODE with the text code shown in Compute.

Prerequisites

Requirement	Minimum	Recommended
OS	Ubuntu 22.04+	Ubuntu 24.04 LTS
GPU	NVIDIA GTX 1080 (8GB)	RTX 4090 (24GB) or better
RAM	16 GB	32 GB+
Storage	50 GB free	200 GB+ SSD
Network	10 Mbps	100 Mbps+
Node.js	22+	22 LTS

Quick Start (5 minutes)

1 Install the VEP Node Agent

mkdir -p "$HOME/vep/private-vault"
curl -fsSL https://vep.live/install-node.sh | bash -s -- --vault-root "$HOME/vep/private-vault"

This installs the agent into $HOME/.vep-node-agent, creates the CLI wrapper $HOME/.local/bin/vep-node, initializes the node config, and runs a readiness check.

If this machine is already paired and you want one command that updates the agent, installs a persistent service, and brings the node back online after logout/reboot, use a root-driven install for the target Linux user:

sudo bash -lc 'curl -fsSL https://vep.live/install-node.sh | bash -s -- --service-user vepuser --vault-root "/home/vepuser/vep/private-vault" --install-service'

If your shell does not already include $HOME/.local/bin in PATH, run:

export PATH="$HOME/.local/bin:$PATH"

Or manual install:

mkdir -p /tmp/vep-node-agent
curl -fsSL https://vep.live/downloads/vep-node-agent.tar.gz | tar -xz -C /tmp/vep-node-agent --strip-components=1
cd /tmp/vep-node-agent
bash setup/install-node-agent.sh
vep-node init --server https://vep.live --vault-root "$HOME/vep/private-vault"

2 Register Node in VEP Dashboard

Open vep.live → Add panel → Compute Resources → + Add Resource

Enter a name (e.g. "Home GPU") and click Create Node. The pending resource card shows a pairing code and the exact command to run. The code works for 10 minutes.

On a phone: Dashboard → Usage & Billing → Integrations → On-prem / BYOC → Open BYOC pairing.

3 Pair Your Node

vep-node pair ABC123

Replace ABC123 with the actual text pairing code from the VEP dashboard.

Pairing is one-time per local config. If you move to a different Linux user or a different machine, create a new pairing code or migrate the full ~/.vep-node state.

4 Start the Agent

vep-node start

Your node should appear as Online in the VEP dashboard within seconds.

When the agent starts you should see a line like VEP Node Agent v0.x.y. That version line is the fastest way to confirm which agent release is actually running.

5 Install as Service (Optional)

sudo "$HOME/.local/bin/vep-node" install-service --user "$USER"

This creates a systemd service that auto-starts on boot. If the machine will run unattended, this is strongly recommended.

Equivalent unattended one-liner after pairing:

sudo bash -lc 'curl -fsSL https://vep.live/install-node.sh | bash -s -- --service-user vepuser --vault-root "/home/vepuser/vep/private-vault" --install-service'

GPU Setup

NVIDIA Drivers

sudo apt install nvidia-driver-550 nvidia-utils-550
nvidia-smi  # verify GPU detected

Ollama (for local LLM inference)

curl -fsSL https://ollama.com/install.sh | sh
ollama pull qwen3:32b  # or any supported model

To verify Ollama is ready:

curl -fsS http://localhost:11434/api/tags

Enable Local Compute

To put a new AI employee on the resource, create it first: in Fleet Dashboard or Employee Cards, click + New Employee, enter a name, choose a role and click Create. The new employee is active right away and appears in the Assign Brain list.

In VEP Dashboard → Compute Resources:

open your resource
under Assign Brain, choose the employee and click Assign Brain
open the resource again and click Apply Recommended Local Setup, or pick a runtime and click Set Employee Runtime
under Runtime Controls, choose one of the local AIs installed on the machine and click Assign Model
the employee then runs on the resource; its knowledge, files and private data stay in VEP Cloud, and while the resource is offline the employee does not answer

When routing is active, Boss Chat for that employee should show the resource name and 🖥️ Your Hardware instead of ☁️ VEP Cloud.

Routing is opt-in per employee: only employees placed on a resource (a preferred node, or model execution mode node) run there; every other employee of the company keeps running in VEP Cloud even when "Prefer Local Compute" is on. Assign Brain alone does not move the employee: it keeps answering from VEP Cloud until you click Apply Recommended Local Setup or Set Employee Runtime. After either button the employee runs only on the resource and never falls back to VEP Cloud: if it does not answer, check that the resource is online. If the resource is online and the employee still does not answer, local compute may not be enabled for your company yet: ask VEP Support.

💡 Tip: Local inference costs €0. You save money on every AI task that runs on your hardware.

Troubleshooting

Node won't connect

Check your firewall allows outbound connections to vep.live:443
Run vep-node status to see current connection state
Check logs: journalctl -u vep-node -f

`vep-node` command not found

Run export PATH="$HOME/.local/bin:$PATH"
Then retry vep-node status

GPU not detected

Run nvidia-smi — if it fails, reinstall NVIDIA drivers
Reboot after driver installation

Pairing code expired or only QR is visible

Codes expire after 10 minutes
Use the text code on the pending resource card, not just the QR
Click Generate New Code on the pending resource card to get a new one

Auto-update has not applied yet

The node agent checks for updates automatically
The running version is shown in the first line of vep-node start
If the VEP dashboard says Waiting for Latest Node Agent, the node is still on an older agent contract and newer runtimes such as OpenHands cannot be enabled yet

Pairing code expired

Codes expire after 10 minutes
Click Generate New Code on the pending resource card to get a new one

⚠️ Security Note: Your node's private key is generated on your machine and never leaves it; VEP receives only its public key. If you enable Zero-Knowledge mode, losing your key means losing access to your data. Always download the Recovery Kit when prompted.

VEP — Virtual Employee Platform · vep.live

🖥️ VEP Compute Node Setup Guide

Prerequisites

Quick Start (5 minutes)

GPU Setup

NVIDIA Drivers

Ollama (for local LLM inference)

Enable Local Compute

Troubleshooting

Node won't connect

vep-node command not found

GPU not detected

Pairing code expired or only QR is visible

Auto-update has not applied yet

Pairing code expired

`vep-node` command not found