Registered Compute

Registered Compute lets you bring your own hardware into NVIDIA Brev. Register any Linux machine — DGX Spark, DGX Station, or any other node — to get SSH access, team sharing, and port forwarding through the Brev platform.

What is Registered Compute?

Registered Compute connects your physical hardware to Brev’s management layer. Once registered, your machine appears in the Brev console alongside cloud GPU instances, and your team can connect to it using the same CLI commands.

This is designed for hardware you own and manage — Brev handles connectivity and access control, not the machine’s lifecycle.

How It Works

Registration is a single CLI command that performs three steps:

1. Installs NetBird — A mesh VPN agent that provides secure connectivity between your machine and Brev users
2. Profiles hardware — Auto-detects GPUs (via NVML), CPU, RAM, storage, OS, and interconnects like NVLink and PCIe
3. Registers with Brev — Makes the machine visible in your Brev organization

After registration, you enable SSH access and can share the machine with teammates.

Register → NetBird installed → Hardware profiled → Node appears in Brev
    ↓
Enable SSH → Share with team → Connect via brev shell

Registered Compute vs Cloud GPU Instances

Supported Hardware

Registered Compute works with any Linux machine. Primary use cases include:

• NVIDIA DGX Spark — Desktop AI workstation
• NVIDIA DGX Station — Multi-GPU workstation with NVLink
• Any Linux node — Any machine running a supported Linux distribution

Hardware Auto-Detection

During registration, Brev automatically profiles your machine and detects:

• GPUs — Model, count, and memory via NVML
• CPU — Architecture, model, and core count
• RAM — Total system memory
• Storage — Available disk space
• Interconnects — NVLink and PCIe topology
• OS — Distribution and version
• Product name — e.g., “DGX Spark”, “DGX Station”

This profile is visible in the Brev console and helps teammates understand the machine’s capabilities.

Registration Data

Registration state is stored locally at /etc/brev/device_registration.json. This file is created during brev register and removed during brev deregister.

Next Steps