Connect your own GPU hardware to VEP and run AI inference locally — with full E2E encryption.
vep-node pair YOUR_CODE with the text code shown in Compute.
| 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 |
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"Open vep.live → Add Panel → Compute Resources → + Add Node
Enter a name (e.g. "Home GPU"). VEP will show both a QR and a text pairing code.
For CLI setup, use the text code shown on the pending resource card.
vep-node pair ABC123Replace 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.
vep-node startYour 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.
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'sudo apt install nvidia-driver-550 nvidia-utils-550
nvidia-smi # verify GPU detectedcurl -fsSL https://ollama.com/install.sh | sh
ollama pull qwen3:32b # or any supported modelTo verify Ollama is ready:
curl -fsS http://localhost:11434/api/tagsIn VEP Dashboard → Compute Resources:
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. To route every employee of the company to any online node, set VEP_COMPUTE_ROUTING_SCOPE=company on the API.
vep.live:443vep-node status to see current connection statevep-node doctor to check config, vault root, GPU, Ollama, and crypto dependenciesjournalctl -u vep-node -fvep-node command not foundexport PATH="$HOME/.local/bin:$PATH"vep-node statusnvidia-smi — if it fails, reinstall NVIDIA driversvep-node startVEP — Virtual Employee Platform · vep.live