Innovexus is no longer a paid product. The appliance below is the complete NOC/SOC platform — privileged access, session monitoring, configuration compliance — packaged as a virtual machine you import and own. No licence key, no seat count, no trial clock.
Downloading requires a free account — hitting Download will ask you to create one (or sign in) first. The account is the whole transaction: there is nothing to buy afterwards.
Import the OVA into VMware, VirtualBox, or Proxmox. Give it 4 vCPU and 8 GB of RAM. Everything else is asked for on first boot.
Innovexus NOC/SOC appliance v2026.08.24 - unattended installer ISO (Ubuntu 22.04.5 LTS base). Closed appliance: first boot asks for the admin password, network, hostname and certificate on the console, then serves the web UI only; console/SSH open the appliance CLI (no OS shell); application tree on an encrypted volume. Jammy-built TACACS+ daemon. Boots BIOS or UEFI.
47eb815b166cf2dbb269ffb86b475db09014adab92fe46eae1df964a122e40dfInnovexus NOC/SOC appliance v2026.08.24 OVA (vmx-20, 4 vCPU / 8 GB, 150 GB thin). Closed appliance: first boot asks for the admin password (with a one-time recovery key), network, hostname and certificate on the console, then serves the web UI only; console/SSH open the appliance CLI (no OS shell); application tree on an encrypted volume; bootloader locked. Jammy-built TACACS+ daemon.
3066584d60a77a0880dfd917f68773d39cdd283e43192c21567c6a2780b3516cThe appliance generates its own cryptographic identity, then asks you a handful of things on the console — network, name, certificate — before the web interface starts.
DHCP out of the box, on whatever the hypervisor names the NIC. Or choose static at the console and the wizard asks for the address, gateway and DNS servers, validates them, applies them, and verifies the link before moving on.
The DNS name you will reach the appliance by. It has to be a real name rather than an IP address, because it also becomes the WebAuthn relying-party ID — and an IP literal cannot be one.
By default the appliance issues its own from a private CA it generates, which lands in ADMIN > PKI where it can later be replaced with one imported from your organization's CA. Let's Encrypt is also built in. This is not optional hardening: browsers only expose the passkey and security-key APIs on an HTTPS origin, so FIDO2 login does not work without it.
Deploying more than one? Both answers can be pre-seeded from a kickstart, cloud-init, or an OVF property, and the console wizard is skipped entirely.
The appliance is assembled from the same source that produces the image above. Nothing in the download is closed.