retivo Docs
  1. Docs
  2. Getting started

Install the Retivo Node

Requirements, the one-line installer, Docker Compose, and what the node needs to reach.

The Retivo Node runs next to your devices. It does the work (status checks, backups, pushes, vulnerability matching) and keeps your data.

Requirements

Minimum
OS 64-bit Linux: Ubuntu 22.04 or 24.04, Debian 12, RHEL 9 or similar. Windows and macOS with Docker Desktop work for testing.
CPU and memory 2 cores, 4 GB RAM
Disk 20 GB, plus room for firmware images if you upgrade devices through Retivo
Software Docker with Compose v2 (the installer adds it if missing)

Network access

From the node to Port Why
Your devices TCP 22 SSH: backups, pushes, data over SSH, terminal
Your devices UDP 161 SNMP: status, model, serial, version, neighbours
Your devices ICMP Ping for online status (a TCP check is used where ping does not pass)
dash.retivo.net TCP 443 The node's connection to your account
services.nvd.nist.gov, www.cisa.gov TCP 443 Vulnerability data
endoflife.date TCP 443 OS support dates
upgrade.mikrotik.com TCP 443 RouterOS release list

Nothing needs to reach the node from outside. If you use remote copies of backups, see Keep backups off the box for the extra addresses.

Install with one command

Get the command from Download & setup on dash.retivo.net. It contains your company's enrollment token.

curl -fsSL https://dash.retivo.net/install.sh | sudo sh -s -- rtv_your_enrollment_token

The installer:

  1. Installs Docker if it is not there.
  2. Checks that the server can reach dash.retivo.net.
  3. Writes /opt/retivo-node/docker-compose.yml and /opt/retivo-node/.env.
  4. Downloads and starts the node, which enrolls itself with your company.

Caution

The enrollment token links a node to your company. Treat it like a password. If it leaks, press Make a new token on Download & setup; nodes that are already enrolled keep working.

Install with Docker Compose

On Windows, macOS, or when you prefer to do it by hand, save this as docker-compose.yml (your own token is on Download & setup) and run docker compose up -d in the same folder:

services:
  retivo-node:
    image: ghcr.io/jaba0x/retivo-node:latest
    container_name: retivo-node
    restart: unless-stopped
    environment:
      RETIVO_CLOUD_URL: https://dash.retivo.net
      RETIVO_ENROLL_TOKEN: rtv_your_enrollment_token
    ports:
      - "8080:8080"
    volumes:
      - retivo-data:/data
volumes:
  retivo-data:

Where the data is

Everything the node keeps (database, encryption key, uploaded firmware) is in the Docker volume retivo-data, mounted at /data. docker compose down keeps it; docker compose down -v deletes it.

Stored credentials are encrypted with the key in /data/secret.key. A backup of the database without that key cannot decrypt them, so always back up the whole volume. See Update and back up the node.

What's next

Last modified October 15, 2026