TREN

Deployment

On your own infrastructure. Even air-gapped.

Netronus runs on premises, on your own server, so your data never leaves. Updates arrive as signed packages, and the same packages are applied offline on networks without internet access. Sizing profiles and an automatic acceptance test make every installation repeatable.

Deployment options

  • AvailableOn-premises Linux serverInstall on your enterprise (RHEL-compatible) Linux server; virtual or physical.
  • AvailableSigned update packagesOnline or offline from a file; with rollback.
  • AvailableAir-gapped networksOffline updates, a signed license file and the security content package.
  • Coming soonReady-made VM imagesOVA (VMware), QCOW2 (Proxmox/KVM), VHDX (Hyper-V) and ISO; based on Rocky Linux 9 / AlmaLinux 9.
  • Coming soonSetup wizardA first-boot console wizard; license, module and profile steps in the web wizard.
  • Coming soonRemote collectorA small collector for branches; outbound-only connection to the center, local buffering on disconnects.
  • RoadmapNetronus ClusterMulti-node deployment on Kubernetes (Helm) or on VMs with Ansible.
  • RoadmapHigh availabilityActive-passive pair for the Appliance; multi-node components in the Cluster.

The problem

What gets in the way today

01

Data must stay inside

In government, finance and defense networks, monitoring data must not go to the cloud.

02

Updates without internet

Most products cannot deliver updates and security content to isolated networks.

03

Installations that depend on people

When every installation is done differently, support and growth get harder.

The solution

Repeatable, signed, auditable

One version number, one signed update package: the appliance verifies the signature before applying it, runs database changes in order and rolls back if something fails. Sizing profiles set component memory limits and retention to match the hardware; the acceptance test checks services, license, data flow and time and produces a report.

  • On-premises: every component runs on your own server
  • Signed update packages, also applied offline from a file
  • Offline license file and security content package
  • Sizing profiles and an automatic acceptance test

How an update is applied

  1. Signed package
  2. Signature verified
  3. Database changes in order
  4. Acceptance test

Capabilities

What you get

Signed updates

Nothing is installed until the package signature and the checksum of every binary are verified.

Offline updates

Bring the update package as a file and apply it; data platform components are included.

Offline license and content

The signed license file and the security content package are uploaded without an internet connection.

Sizing profiles

Profiles from XS to L; memory limits, retention and disk protection thresholds match the hardware.

Acceptance test

Services, license and modules, data flow, time and content freshness are checked with one command.

5651 time stamping

TÜBİTAK Kamu SM time stamps for log signing; a local or custom RFC 3161 provider for trials.

Technical summary

At a glance

ItemDetail
DeploymentOn-premises Linux server (RHEL-compatible), virtual or physical
UpdatesSigned package; online or offline from a file
License activationOnline or with a signed license file
Security contentDaily online or as an offline package
Sizing profilesXS (≤ 100 assets) · S (≤ 500) · M (≤ 2,000) · L (≤ 5,000) · Cluster (> 5,000)
Recommended hardware (L profile)24 – 32 cores, 64 GB RAM, 2 – 4 TB NVMe
Time stampingTÜBİTAK Kamu SM, local TSA or a custom RFC 3161 provider
Ready-made imagesOVA, QCOW2, VHDX, ISO: coming soon

See Netronus in your own environment

We will set up a demo on your network, show the screens with your own devices and prepare a quote for the modules you need.

Request a demo

See Netronus in your own environment

We will set up a demo on your network, show the screens with your own devices and prepare a quote for the modules you need.