Skip to content

ARROW Manager Overview

ARROW Manager is the dashboard that lives on your ARROW device itself. It is the control panel for a single, deployed device. Open it in a browser and you can see whether the device is healthy and online, deploy virtual machines onto it, drop into a terminal, and adjust its settings, without touching a separate SSH client or another tool.

Think of ARROW Manager as the device’s own front panel, served over the web. It is where you go when you want to know what one specific device is doing right now, and where you go to put it to work. From it you can:

  • See device health at a glance, with CPU, memory, storage, and temperature
  • Confirm the device is connected the way you expect, across network, cellular, and the NetBird VPN
  • Verify the device can actually reach its VPN host, which is the check that tells you remote access will work
  • See which route the device is currently reachable on, and why that route was chosen
  • Deploy and manage virtual machines from a built-in app library
  • Open a terminal on the device
  • Change device settings such as network mode, cellular, drop mode, and appearance
ARROW Manager dashboard showing system, network, cellular, and VPN status ARROW Manager dashboard showing system, network, cellular, and VPN status
The ARROW Manager dashboard with live device health, connectivity, and VPN status
  1. 1 The health banner is the first thing to check, since it tells you in plain language whether the device can reach the VPN, and offers a re-check.
  2. 2 Live device resources, covering CPU (with temperature), memory, and storage usage.
  3. 3 Connectivity at a glance, covering the wired network, the cellular modem and signal, and the NetBird VPN with its address and peer count.
  4. 4 Where the device is on a map, and the Access path card naming the route the device is reachable on right now.

The Dashboard is what you land on, and it is designed to answer one question fast. Is this device fine, or does it need me? A top bar runs across the screen with the device hostname, live CPU, RAM, and uptime, the current time, your device tag, your signed-in account, and a Logout button.

Start here. The health banner at the top of the Dashboard tells you whether the device can reach its VPN host, which is the single most useful signal that remote access is working. When all is well it reads “VPN can connect over Ethernet” with a green HEALTHY badge and shows the individual checks it ran, which are Ethernet, Network IP, VPN host, and Secure (TLS). If any of those fail, this is where you see it first. Click Re-check after you have changed something, and it runs a full set of connection tests and opens the results in a VPN Connection Diagnostics window you can move, resize, or minimize while you keep working.

Drop mode changes what the banner asks. A dropped device is meant to run entirely on cellular and to stay off the network it is plugged into, so instead of reporting a blocked wired path the banner confirms the device is running on cellular by design, and the wired checks (VPN host and Secure (TLS)) show as not applicable rather than failures. The one thing it raises there is drop mode being engaged while the device is not actually on cellular, which means it is either unreachable or using a network it is not supposed to use.

Below the banner, a row of cards break the device’s state down further:

CardWhat It Shows
CPUCurrent processor load and temperature
RAMMemory used out of total
StorageSpace used on each drive (for example eMMC and NVMe)
NetworkInterface IP address, connection type, and public IP
CellularCarrier, signal strength, band, and mode
VPN (NetBird)VPN IP address, connected peer count, and device FQDN

A location map and an Access path card round out the view. If the default layout does not match how you work, click Customize to rearrange, resize, or hide cards; your layout is saved automatically, so you set it once.

The map is scoped to the current boot. A device works out where it is when it starts up and never carries a position across a restart, so a box that was just rebooted reads “Locating…” until its first scan of that boot lands, which takes up to 30 seconds. A precise fix needs at least three WiFi access points in range and a radio that is not serving a hotspot; without them the device falls back to its public IP address, which places it within roughly 25 km. If the map stays empty, or the pin is nowhere near the site, open the Location section of Settings. Rescan runs the scan again, and the section shows each stage of the last scan and anything blocking a precise fix.

The Access path card answers a different question from the health banner. Not “is the VPN healthy” but “which route is this device reachable on right now, and why that one”. It draws the current path as a line, from the uplink (Ethernet or LTE), through whatever is carrying it (NetBird or Nullpath), to the device, and states the reason underneath in a sentence. Next to the title it reads Connected when traffic is confirmed to be moving, and Unconfirmed when a route has been selected but nothing has proved it carries traffic yet.

Show more details opens a window that lists all the paths in preference order, wired NetBird first, then the Nullpath tunnel over the CDN, then cellular, with the device’s local hotspot as the last resort. The same window shows the device’s uplink, VPN, and gateway addresses along with the connections it currently has open, which saves you a terminal when you need to know what the device is actually talking to. Those endpoint details need an administrator account; without one the rest of the card still works.

Everything else lives behind the icon rail down the left side of the screen. Each icon opens one section:

SectionWhat You Can Do
DashboardMonitor device health and connectivity
Virtual MachinesDeploy, start, stop, and open consoles for VMs
VPNView NetBird status, peers, relays, and identity
CellularInspect LTE signal, tower, modem, and data usage
TerminalOpen an interactive shell on the device
SettingsConfigure network, cellular, drop mode, location, monitoring, updates, and appearance

When you need a shell on the device, the built-in terminal saves you from opening a separate SSH client. It supports multiple tabbed sessions and an adjustable font size.

ARROW Manager built-in terminal with a tabbed session ARROW Manager built-in terminal with a tabbed session

The built-in terminal, with tabbed sessions and adjustable font size

ARROW Manager built-in terminal with a tabbed session ARROW Manager built-in terminal with a tabbed session

ARROW Manager is built for a dark interface, and that is what you get out of the box. It works on both desktop and mobile browsers, so you can check on a device from a phone in the field.

Light mode still exists, but it is hidden. To bring it back, open Settings, choose Appearance, and turn on Enable light mode. That restores the light theme and puts the light and dark toggle back in the top bar. Turning it off again returns the interface to dark straight away, and most people should leave it off.

If something is not working, the fastest fix is usually to confirm your own network or VPN connection to the device, since most problems are connectivity rather than the device itself. The Troubleshooting guide covers the common cases. If it persists, contact your administrator.