One file. No database, no agents.
The whole product — server, web interface, everything — is a single executable. Copy it to the machine that's always on, run it, and open a browser. Free for 14 days with every feature switched on, up to 10 devices.
Getting it running
There is no installer to step through and nothing to configure before first launch.
Windows — installer
- Run
setup_netriva.exeand accept the prompts. It installs toC:\Program Files\NetRiva\, adds a Start Menu entry, and offers to run NetRiva as a Windows service so it keeps monitoring when nobody is logged in. - It launches when the installer finishes, and the interface opens in your browser.
- Go to Discover and let it sweep your subnet.
Uninstall from Settings → Apps like any other program. Your config and history live in C:\ProgramData\NetRiva\ and survive upgrades.
Windows — portable
- Unzip the whole folder somewhere you can write to — your Documents or Desktop folder, or a USB stick. Not
C:\Program Files: the portable copy needs to write next to itself. - Double-click it. A console window opens and the interface launches in your browser.
Everything NetRiva saves — settings, logins, keys, history, logs — stays in the data folder next to netriva.exe. Delete the folder to remove it; there is nothing to uninstall. You can move the folder to another drive or PC and it keeps working, and a portable copy never touches the data of an installed NetRiva. To update, replace netriva.exe and keep data. The portable copy cannot run as a Windows service; use the installer for that.
Windows will warn you the first time. Here's why.
Nothing is wrong with the file. We would rather you heard it from us than wondered.
NetRiva is not code-signed yet. A signature is how Windows tells you who made a program. Ours has none, so Windows names the maker as Unknown Publisher, and Microsoft Defender SmartScreen warns you the first time you run setup_netriva.exe (or netriva.exe from the zip).
Why not signed? A code signing certificate costs money every year. NetRiva is a small, new product, and we chose to buy one once NetRiva has its first customers rather than before. That is the whole reason. The warning means Windows has not seen this file before; it does not mean anything was found in it.
Get-FileHash .\setup_netriva.exe -Algorithm SHA256
Compare the Hash it prints with the one above, all 64 characters. If they match, you have exactly the file we built. If they don't, don't run it and tell us. The zip and the Linux files are checked the same way: see Verify what you downloaded.
Downloading it in Edge or Chrome
- The download may appear with a warning and a Delete button. Open the … menu beside it and choose Keep.
- If a second dialog says “Make sure you trust setup_netriva.exe before you open it”, click the small arrow on the Delete button, then Keep anyway. The option is hidden inside a button that looks as if it only deletes.
When you run it
- SmartScreen shows “Windows protected your PC” with only a Don't run button. Click More info.
- It now shows Publisher: Unknown Publisher and a Run anyway button. Click Run anyway.
- Windows then asks “Do you want to allow this app from an unknown publisher to make changes to your device?” The installer needs this to install into
C:\Program Files\NetRiva\. Click Yes.
“SmartScreen can't be reached right now”
If the PC is offline, or a proxy or firewall stops it reaching Microsoft, you get this box instead, with Run and Don't run straight away. It means Windows could not look the file up, not that it found a problem. Check the checksum as above, then click Run.
If Windows still blocks it
- Right-click the downloaded file and choose Properties.
- At the bottom of the General tab, tick Unblock, then Apply.
That removes the “came from the internet” mark Windows puts on every download. It is not an extra security setting.
Linux — copy and paste
Every block below is complete: paste it into a terminal as it stands. Each one is given with curl and with wget; use whichever your system has (command -v curl wget tells you).
Pick your architecture. uname -m tells you which: x86_64 is amd64, aarch64 is arm64.
As a service — the .deb or .rpm package
Easiest for a server: the package installs NetRiva as a service that starts at boot and keeps its data in /var/lib/netriva. Shown for amd64; on arm64, change amd64 to arm64 in both lines. Afterwards follow Running as a service to reach it from your network and sign in.
Ubuntu, Debian
curl -LO https://dl.net-riva.com/1.0.5/netriva_1.0.5_linux_amd64.deb
sudo apt install ./netriva_1.0.5_linux_amd64.deb
wget https://dl.net-riva.com/1.0.5/netriva_1.0.5_linux_amd64.deb
sudo apt install ./netriva_1.0.5_linux_amd64.deb
RHEL, AlmaLinux, Rocky, Fedora
curl -LO https://dl.net-riva.com/1.0.5/netriva_1.0.5_linux_amd64.rpm
sudo rpm -Uvh netriva_1.0.5_linux_amd64.rpm
wget https://dl.net-riva.com/1.0.5/netriva_1.0.5_linux_amd64.rpm
sudo rpm -Uvh netriva_1.0.5_linux_amd64.rpm
To try it first — the archive
Downloads, extracts and starts NetRiva in the foreground. Stop it with Ctrl+C.
amd64 (most servers and PCs)
curl -LO https://dl.net-riva.com/1.0.5/netriva_1.0.5_linux_amd64.tar.gz
tar -xzf netriva_1.0.5_linux_amd64.tar.gz
cd netriva_1.0.5_linux_amd64
chmod +x netriva
[ -d /var/lib/netriva ] || sudo install -d -m 0700 -o "$USER" /var/lib/netriva
./netriva
wget https://dl.net-riva.com/1.0.5/netriva_1.0.5_linux_amd64.tar.gz
tar -xzf netriva_1.0.5_linux_amd64.tar.gz
cd netriva_1.0.5_linux_amd64
chmod +x netriva
[ -d /var/lib/netriva ] || sudo install -d -m 0700 -o "$USER" /var/lib/netriva
./netriva
arm64 (Raspberry Pi 4 / 5 on a 64-bit OS)
curl -LO https://dl.net-riva.com/1.0.5/netriva_1.0.5_linux_arm64.tar.gz
tar -xzf netriva_1.0.5_linux_arm64.tar.gz
cd netriva_1.0.5_linux_arm64
chmod +x netriva
[ -d /var/lib/netriva ] || sudo install -d -m 0700 -o "$USER" /var/lib/netriva
./netriva
wget https://dl.net-riva.com/1.0.5/netriva_1.0.5_linux_arm64.tar.gz
tar -xzf netriva_1.0.5_linux_arm64.tar.gz
cd netriva_1.0.5_linux_arm64
chmod +x netriva
[ -d /var/lib/netriva ] || sudo install -d -m 0700 -o "$USER" /var/lib/netriva
./netriva
The line before ./netriva creates /var/lib/netriva, where NetRiva keeps its configuration and data, and makes it yours and private to you. An ordinary account can't create it, so without that line the first start stops with permission denied. If the folder already exists, for example because NetRiva runs as a service, the line leaves it alone. Running the binary as root also works, but isn't needed.
Then open http://localhost:8080 and sign in with admin / admin. You'll be asked to choose a new password straight away. To reach it from another machine, start it with ./netriva -listen 0.0.0.0:8080. To run it as a service, follow Running as a service in the docs. You can do that from this same folder later, and what you set up now carries over.
Download and verify in one go — this refuses to extract anything that does not match the published checksum:
curl -LO https://dl.net-riva.com/1.0.5/netriva_1.0.5_linux_amd64.tar.gz
curl -LO https://dl.net-riva.com/1.0.5/checksums.txt
sha256sum --ignore-missing -c checksums.txt && tar -xzf netriva_1.0.5_linux_amd64.tar.gz
wget https://dl.net-riva.com/1.0.5/netriva_1.0.5_linux_amd64.tar.gz
wget https://dl.net-riva.com/1.0.5/checksums.txt
sha256sum --ignore-missing -c checksums.txt && tar -xzf netriva_1.0.5_linux_amd64.tar.gz
On arm64, use the _arm64 file name in the first and last lines.
uname -m returning aarch64 means you are good; armv7l means you are on the 32-bit build.
net.ipv4.ping_group_range. Ubuntu and Debian switch it off (Ubuntu 24.04 and Debian 12 ship 1 0), so there every device shows as down until you run the two lines below. Other distributions vary. Check with cat /proc/sys/net/ipv4/ping_group_range: 0 2147483647 is fine, and 1 0 means it is off. NetRiva then falls back to a raw socket if it has the cap_net_raw capability (sudo setcap cap_net_raw+ep ./netriva, which you have to repeat for every new binary; the service in the docs has it already). Or switch unprivileged ping on for good:
echo 'net.ipv4.ping_group_range = 0 2147483647' | sudo tee /etc/sysctl.d/60-netriva-ping.conf
sudo sysctl --system
Verify what you downloaded
Hash the file you downloaded, before unzipping it. The checksums published above are for the installer and the archives — not for the netriva binary inside them, which has a different hash.
# Windows (PowerShell) - the installer
Get-FileHash .\setup_netriva.exe -Algorithm SHA256
# Windows (PowerShell) - the portable zip
Get-FileHash .\netriva_1.0.5_windows_amd64.zip -Algorithm SHA256
# Linux - hash the archive you downloaded
sha256sum netriva_1.0.5_linux_amd64.tar.gz
Compare the result with the full SHA-256 printed beside that file above — all 64 characters, not just the start. If they differ, don't run it and tell us.
Or let the machine do the comparing, which is less error-prone than reading hex by eye:
curl -LO https://dl.net-riva.com/1.0.5/checksums.txt
sha256sum --ignore-missing -c checksums.txt
That prints OK for every file it recognises and fails loudly for anything that does not match.
What it needs
| Requirement | Detail |
|---|---|
| Operating system | Windows 10 / 11 / Server 2016 or later · Linux with glibc 2.31 or later |
| Architecture | amd64 (x86-64) or arm64. A Raspberry Pi 4 or 5 is plenty, running a 64-bit OS — 32-bit Raspberry Pi OS is not supported. |
| Memory | About 80 MB idle; roughly 250 MB monitoring 200 devices |
| Disk | Under 50 MB for the binary. Syslog retention is what actually uses space, and you set that. |
| Database | None. There is nothing to install, tune or back up separately. |
| Network | Reachability to the devices you're monitoring. Inbound UDP 5514 only if you want the syslog receiver. |
| Browser | Any current Chrome, Edge, Firefox or Safari |
| macOS | Not yet — it needs an Apple Developer account for notarisation. Say if you want it. |
Stuck on the first run?
Tell us what you're seeing. There's a one-click redacted diagnostic bundle inside the app if you'd rather send that.
The form reaches a person, not a ticket queue.