NetStacksNetStacks

System Requirements

Supported operating systems and architectures for NetStacks Terminal, optional tools, network access, and what a NetStacks Controller server needs.

NetStacks Terminal

PlatformMinimum versionArchitecturesNotes
macOSmacOS 10.15 (Catalina)Apple Silicon (arm64), Intel (x64)Separate download for each architecture
WindowsWindows 10 or 11x64Uses Microsoft Edge WebView2 (built into Windows 11 and current Windows 10). Installs per user, with no admin rights needed.
LinuxA distribution with WebKitGTK 4.1 and GTK 3x86_64Built on Ubuntu 22.04, so Ubuntu 22.04 or later and Debian 12 or later work. The .deb depends on libwebkit2gtk-4.1-0 and libgtk-3-0. The AppImage needs FUSE 2 (libfuse2). Installing the agent certificate needs polkit (pkexec).

The window opens at 1400×900 and can be made as small as 800×600. Your data is kept in a single SQLite database that grows with your sessions, documents and recordings.

Not supported

There are no Windows ARM64 or Linux ARM64 desktop builds, and no mobile apps. On those platforms, use the web terminal of a NetStacks Controller.

Optional Tools

NetStacks works without any of these. If they are present, it uses them to unlock extra features:

ToolUsed for
gitGit features in Workspaces (NetStacks uses the system Git command)
nmapExtra device fingerprinting during topology discovery
Ollama, or another local OpenAI-compatible serverRunning the AI assistant against a local model instead of a cloud provider

Some tools are downloaded automatically the first time you use the feature that needs them: uv for Python scripts (from GitHub), the Pyrefly Python language server (from PyPI), and the IEEE MAC vendor database for enrichment.

Network Access

From the computer running NetStacks Terminal:

DestinationPort / protocolNeeded for
Your network devicesTCP 22 (SSH), TCP 23 (Telnet), or the ports you configureTerminal sessions and SFTP (standalone mode)
Your network devicesUDP 161 (SNMP v2c)Topology discovery, live link stats and SNMP quick looks (standalone mode)
releases.netstacks.netHTTPS 443Update checks and downloads
Your AI provider (for example api.anthropic.com, api.openai.com)HTTPS 443The AI assistant (standalone mode, if configured)
NetBox, LibreNMS, Netdisco, other APIs you addHTTPS (as configured)Integrations and API Resources
Your NetStacks ControllerHTTPS, normally port 3000Enterprise mode (all traffic, including proxied SSH, goes to the Controller)

In enterprise mode the Terminal only talks to the Controller (plus the update server). The Controller needs to reach your devices.

Web Terminal (Browser) Enterprise

The web terminal at https://<controller>:3000/terminal/ runs in a current version of Chrome, Edge, Firefox or Safari. The browser must trust the Controller's certificate, or you must accept the certificate warning. Nothing is installed on the client.

NetStacks Controller Server Enterprise

RequirementDetails
HostLinux server on x86_64 (amd64). The container images are amd64-only.
Container runtimeDocker Engine with the Docker Compose v2 plugin. The installing user must be able to run Docker. The Controller uses the Docker socket to run jumpboxes and plugins.
Toolsopenssl and curl (used by the installer)
DatabasePostgreSQL 16 with pgvector, either bundled (the default) or your own external server. An external server must have the pgvector extension available.
InboundTCP 3000 (HTTPS) from engineers' computers and browsers. It serves the admin console, the web terminal, the REST API and the WebSocket connections.
Outboundghcr.io to pull images. www.netstacks.net to activate the license, which is also re-validated every 24 hours. Your devices over SSH, Telnet and SNMP. Your LLM providers, if you use cloud AI.
LicenseA Team or Enterprise license key. Each user signed in from the Terminal uses one seat; admin console sign-ins don't use seats.

NetStacks does not publish fixed CPU, memory or disk sizes. Size the server for PostgreSQL plus the number of SSH sessions, AI requests and plugins you expect to run, and monitor it from Administration → Platform Health. Fully offline (air-gapped) installs are not supported, because images and license activation need internet access.

Installation steps: Installing the Controller.