NEURU is 100% self-hosted — it runs on your hardware, on your network. Deploy it with Docker in minutes, then activate your license against this portal.
A Linux server (Ubuntu 22.04+ recommended) with Docker & Docker Compose. 2 vCPU / 4 GB RAM is plenty to start. Outbound HTTPS to this portal for activation.
Log in to your account → Downloads → grab the latest NEURU build your plan entitles you to. Verify the SHA-256.
Find it on your Dashboard (click to copy). One key activates the machines your plan allows.
From Downloads, get neuru-installer-vX.tar.gz, copy it to your server, and unpack:
NEURU uses an external Docker network, then Compose brings up the app + database:
Open http://YOUR-SERVER:8090 → the first-run wizard imports the schema and creates your admin. Default login is admin / [email protected] — change it immediately under your profile.
In NEURU → Site Configuration → Licensing: set the License portal API URL to https://neurunetpr.com/api.php, paste your license key, and click Activate. NEURU binds to the machine and receives a signed token.
Run discovery or add nodes in Config, then explore the Command Deck. Updates appear in NEURU's Licensing panel and here under Downloads.
.lic file — contact us for one.Every NEURU release is a complete build — the same package you install with. To update, you simply deploy a newer build over the old one. Your data is safe: all your nodes, history, settings and users live in the database volume, which is never touched by an update.
In NEURU → Site Configuration → Licensing you'll see when a newer build is available. New builds also appear here under Downloads.
A quick safety net before any update:
From Downloads — or pull it straight onto the server with the wget/curl command shown there (authenticated by your license key, logged to your history).
This replaces only the program files — your database is untouched:
Open NEURU — the version in About shows the new number. Any schema changes apply automatically on first load.
Downloads may show stable builds (recommended for production) and, when available, beta builds (early features, marked with a badge). Stick to stable unless we ask you to test a beta.
/api.php, and that your server can reach the portal over HTTPS.:8090 by default (plus 514/udp syslog and 2055/udp NetFlow). Put a TLS reverse proxy in front for production..lic file.