A separate tool for every domain
When network, servers, virtualization and storage live in separate consoles, teams chase the same outage on different screens and lose context.
Platform
One platform. Only the modules you need.
In Netronus everything you monitor is an asset in the same inventory: switches, servers, virtual machines, storage arrays. Alarms, dashboards, reports, search and topology are shared. Only the modules you license are visible, and the data platform grows with you from a single server to a cluster.
The problem
What gets in the way today
Paying for what you do not use
Monolithic licenses make you buy capabilities you do not need.
Re-installing when you grow
As the device count rises, many tools force a new product or a fresh installation.
The solution
A shared core, optional modules
The core is part of every installation: asset inventory and relationships, role-based access, the alarm engine, notifications, dashboards, reports and the REST API. Network, flow, logs, configuration, security content, server, agent, virtualization and storage modules plug into that core. A module that is not licensed has no menu, no screen and no running service.
- One inventory: switches, servers, VMs and storage arrays in the same list and the same search
- One alarm stream: every module’s alarms share the same acknowledge, maintenance and notification logic
- Mixed dashboards: switch traffic, server CPU and storage latency side by side
- End-to-end relationships: VM → host → datastore → LUN → array → SAN port
Capabilities
What you get
Shared asset model
Every asset gets a page in the same frame; modules only add tabs such as interfaces, disks, services, pools and volumes.
Relationships and impact analysis
Which host, datastore, LUN and array a VM sits on is resolved automatically. While a parent asset is down, alarms for its children are suppressed.
Package, module and feature licensing
A license is made of packages, modules, features and counted metrics (network devices, servers with agents, VMs, storage arrays). You buy exactly what you need.
One search
The search bar finds assets, IPs, MACs, serial numbers, VM names and alarms; open it anywhere with Ctrl+K.
REST API and OpenAPI
The /api/v2 endpoints are described with OpenAPI; read and manage assets, alarms and alarm rules programmatically.
Modern data platform
VictoriaMetrics for time series, NATS JetStream for the event bus, ClickHouse for flow data. All on premises, on your own server.
Role-based access, AD/LDAP
Permissions are defined per asset group and per module, e.g. the server team only sees servers. Users sign in with Active Directory / LDAP.
Company logo and guest dashboards
Your logo appears next to Netronus on the sign-in screen, in the menu, on guest dashboards, in PDF reports and in e-mails.
Mobile-ready interface
Dashboards, events, inventory and maps work comfortably on a phone with a bottom navigation bar.
Scale
From a single server to a cluster
The code and the components are the same in both editions; only how many instances run and how they are spread changes.
Netronus Appliance
One server, all components
- Up to 5,000 assets
- All modules on one machine
- Sizing profiles from XS to L
- Air-gapped installations
Netronus Cluster Roadmap
Horizontal scale
- Designed for 90,000+ devices
- Designed for 1 million flows per second
- Collectors, metrics and flow storage scale out
- Kubernetes (Helm) / Ansible deployment
Design target; cluster deployment is on the roadmap.
Data platformVictoriaMetricsNATS JetStreamClickHouseMySQLRedis
Screenshots
See it in the product
Technical summary
At a glance
| Item | Detail |
|---|---|
| Interface | One web interface (HTTPS); Turkish and English, light and dark themes, mobile-ready |
| Modules | Network, flow, logs, configuration, security content, server, agent, virtualization, storage |
| Licensing | Package, module, feature and metric based, signed; offline license file for isolated networks |
| Data platform | VictoriaMetrics (metrics), NATS JetStream (event bus), ClickHouse (flow), MySQL (inventory and configuration) |
| API | REST /api/v2 with an OpenAPI description |
| Identity and access | Local users, Active Directory / LDAP; role, group and module based permissions |
| Netronus Appliance | Single server, up to 5,000 assets |
| Netronus Cluster | Horizontal scale; designed for 90,000+ devices and 1 million flows per second |
Roadmap
Coming next
These items are planned and not part of the current release.
- Roadmap Kubernetes (Helm) and Ansible deployment for Netronus Cluster
- Roadmap High availability (HA)
- Roadmap Remote collectors for branches and regions
- Roadmap Multi-tenant installations for service providers
Related
Better together
Servers and Agent
Monitor Linux and Windows servers agentless over SSH, WinRM, SNMP and Redfish, or in depth with the lightweight Netronus Agent.
Explore the moduleAlarm Engine
Thresholds with duration and hysteresis, rate of change, forecasts, seasonal baselines; maintenance and dependency suppression. One engine for network, servers and storage.
Explore the moduleDeployment
Runs on your own server. Signed updates; offline updates, licenses and content for networks without internet access.
Explore the moduleSee 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.