Nostromo

A dashboard for managing networks across companies, with SSTP tunnels to reach devices behind NAT and CGNAT and full IPv6 support.

Nostromo is a project I develop in collaboration with RHX. It grew out of the practical need to manage hundreds of network devices across a distributed infrastructure. It is a web dashboard for managing the devices of one or more companies, with monitoring, host inventory, configuration tracking, backups, and SSH access.

It can be used as a managed service or installed on your own server. It can reach devices behind NAT or CGNAT without exposing them to the Internet. It supports IPv4 and IPv6; the current driver covers MikroTik with RouterOS 6.49 and 7.

Devices behind NAT and CGNAT

Devices connect to Nostromo by opening an SSTP tunnel to the server. This is the default connection method and allows them to be monitored even without a public IP address or from behind NAT and CGNAT, without opening inbound ports on the client's network.

The tunnel can use TCP port 443 and carries traffic for monitoring, configuration reads, backup uploads, and the SSH terminal. A direct connection is available in the advanced options as a fallback for installations where the server can already reach devices through a management network or a VPN.

Full IPv6 support

Nostromo supports IPv4, IPv6, and dual-stack networks. Devices can also be reached over IPv6, and the inventory keeps the IPv4 and IPv6 addresses detected for each host, together with their history.

Traffic inside SSTP tunnels also uses IPv6, with a dedicated subnet for each company. Management addresses therefore stay independent of clients' IPv4 networks, which can use the same private addresses without creating conflicts in the connection to Nostromo.

Monitoring

The dashboard brings together device status, configuration changes awaiting review, connected hosts, and CPU and memory usage. Devices can be organized into groups, for example by location, to check the state of individual networks.

Each device's detail page updates in real time and shows resources, interfaces, and connected hosts. Dashboard charts keep up to thirty days of aggregate data to show how the network changes over time.

Device enrollment

To enroll a device, operators choose a name in the dashboard and paste the generated command into the RouterOS terminal. The procedure configures the SSTP tunnel and creates the service account with the read permissions needed for monitoring.

The default method does not require an address the server can reach, because the device opens the connection. When choosing a direct connection in the advanced options, operators provide the IPv4 address, IPv6 address, or hostname and the API settings.

Host inventory

Hosts detected by devices are collected in a register for each company, with the IPv4 and IPv6 addresses they used and the interfaces where they were seen. Where the available information allows it, Nostromo identifies their manufacturer, type, operating system, and version.

Hosts can be marked as trusted, retained for investigation, or forgotten in the dashboard. The dashboard flags connected hosts that have not been recognized or trusted, helping operators identify devices that need checking.

Vulnerabilities and updates

Known versions of supported devices and hosts are compared against public vulnerability and support lifecycle data. The dashboard distinguishes actively exploited vulnerabilities from other known issues and flags unsupported versions and available updates.

Sources include NVD, CISA's catalog of exploited vulnerabilities, and endoflife.date, and are updated daily. The comparison happens on the Nostromo server without sending the networks' inventory to those sources.

Configuration changes

Nostromo reads configurations on a schedule and keeps the versions that change. Operators can compare two versions in the dashboard to examine added and removed lines; a change stays flagged until someone reviews it.

Email notifications list the devices that changed and the number of affected lines, with a link to the details. Snapshots provide a record of changes, while restoring a device uses its backups.

Encrypted backups

Devices create their own backups and upload them to Nostromo over SFTP. Operators choose the schedule and number of copies to retain in the dashboard, then install the generated command on the device.

The encryption password is chosen on the device and never passes through Nostromo, which stores the files without being able to open them. Backups can be downloaded from the dashboard and restored manually using the password kept by the client.

Browser SSH terminal

A device's detail page can open an SSH session in the browser. The SSH client and private keys remain in the browser; the Nostromo server relays encrypted traffic between the connecting person and the device.

Access requires a dedicated permission and uses the operator's keys, allowing each person to work under their own identity on the device.

Trust model

The trust model limits the privileges the server retains over devices. Monitoring and configuration reads use a service account with read permissions, while SSH sessions use the operator's keys, which remain in the browser. Backups are encrypted on the device with a password Nostromo never receives. This separation reduces the permissions available to the server when nobody is working on the devices.

Companies and permissions

A single installation can manage multiple companies. Users join by invitation and can belong to more than one company, with a different role in each.

Roles control access to features, from monitoring to backup management and the SSH terminal. System administrators can work across companies and manage the installation.

Installation

Nostromo is a single Rust executable that includes the API, web dashboard, monitoring, SSTP tunnels, and backup receiver. It uses SQLite or PostgreSQL; the dashboard is written in React and TypeScript.

Linux distributions are static and require no additional runtime dependencies. Configuration and data stay on the server chosen for the installation.