RealmHelm
On this page

Server and network management

Find the work. Plan the change. Deliver with control.

RealmHelm collects the configuration, history, usage, health, lifecycle and security data for every server and network device you manage. Your team plans each change and approves it in the browser. You can also connect your own AI agent to look things up and draft plans.

For MSPs and internal IT teams.

Request a demo See what it does

RealmHelm / Dashboard

Issues, vulnerabilities and compliance across every site, on one screen.

What it does

Everything you manage, in one place

Servers, switches, firewalls and the rest of your network, in one browser interface.

Know what you have and when support ends

Bring in devices from the tools you already use and from network scans. RealmHelm keeps one clean record per device, including its warranty and end of support.

Every device from every source, with its health.

Back up configurations and see what changed

Back up every configuration and see exactly what changed between versions. Plan changes and firmware upgrades with checks, and roll back where the platform supports it.

A VLAN added on idf-sw-05, and the two rules it changed.

Check every device against your own rules

Turn your standards into rules and check every device against them. Track exceptions, and fix what fails through the same approval as any other change.

Seven custom policies and how many devices pass each.

Find the devices that need a fix

Match what you run against the NetPrecedent vulnerability feed, including what attackers are exploiting now. Findings are grouped by fix and ranked by urgency.

Fixes ranked by urgency, with the devices each one covers.

See what runs on your servers

See the software, services and certificates on your Windows and Linux servers, and the hardware underneath them. Catch outdated software and expiring certificates early.

Software found on srv-app-09, with when it was first and last seen.

Know when something breaks

Monitor every device and the services that run on them. See what is down or degraded, and alert your team when something breaks.

Open issues across the fleet, most severe first.

Send the reports your team and customers need

Send scheduled reports to your team or your customers. Cover any mix of inventory, health, security, compliance and changes.

The weekly operations report, as sent by email.

With your own AI agent

Ask for the work, then approve the plan

Your agent looks things up in RealmHelm and drafts the change. You review it and approve it in the browser. The networks in these examples are made up.

You said:

What runs out of support by the end of 2027?

Your agent

Searched inventory and lifecycle dates in RealmHelm

Seven devices at Site 4: a FortiGate-500E that is already out of support, four Cisco switches and two Dell servers.

I’ve drafted one project with five changes. The configs for the new firewall and switches are written before the hardware arrives.

The replacement project: five changes, in order.

You said:

Which firewall rules haven’t carried traffic in 90 days?

Your agent

Checked firewall policy usage in RealmHelm

37 policies on fw-edge-01 and fw-edge-02, counted across reboots and failover.

I’ve drafted a change that disables them, so you can turn any back on. It’s waiting for your approval.

The cleanup change, with a rollback for every policy.

You said:

Which devices are exposed to something attackers are using now?

Your agent

Checked vulnerability findings in RealmHelm

Four FortiGates run FortiOS 7.4.9, which CVE-2026-24858 affects. It is known to be exploited and was seen in honeypots this week.

I’ve planned the upgrade one HA pair at a time. It stops if a pair fails.

The upgrade plan: one HA pair at a time.

You said:

Which switches are missing our standard settings? Fix them.

Your agent

Checked switches against your policies in RealmHelm

Six switches fail your Standard switch settings policy. Four lack the logging host and two lack the NTP server.

I’ve drafted only the missing lines for each switch, with a check after each one.

Only the missing lines, on Arista and Cisco switches.

You said:

Send the customer a weekly review of what we fixed and what’s left.

Your agent

Set up a scheduled report in RealmHelm

I’ve set up a weekly network review for the customer.

This week’s lists the finished FortiGate upgrade and what’s still open: 28 lower-priority findings, 14 switches below their firmware target and 6 policy violations.

This week’s review: what was fixed and what’s still open.

Control

Check every change before it runs

Each plan lists the devices, commands and checks, and any rollback steps. Nothing changes on a device until someone approves it in the RealmHelm browser interface.

While a change runs, you can pause, retry or stop it. Where the platform supports it, you can roll back. Steps someone finishes by hand are recorded as done by hand.

How we protect access and secrets

Optional

How your AI agent connects

You can do everything on this page in the browser. If your team uses an AI agent, connect it through our MCP server or the rhctl command line.

  • Your permissionsThe agent acts as the signed-in user, with the same access.
  • Plans, not approvalsIt can look up data and plan changes. Only a person approves them, in the browser.
  • No secretsRealmHelm removes passwords and keys when it collects them, so they never reach an AI model.

Deployment

One deployment in Azure for each network you manage

Run RealmHelm in your own Azure tenant, or choose a dedicated deployment that NetPrecedent hosts.

Site agents connect out over HTTPS. You do not need a site VPN or inbound ports.

For MSPs: run a separate deployment for each customer, all in your Azure tenant. Add staff to a deployment’s Operators group to give them access.

Your team, RealmHelm, and your environmentYour team, and your AI agent if you use one, work through RealmHelm in Azure. Site agents connect outbound over HTTPS from each location. Changes require your approval. Your teamOptional AI agent RealmHelmIn Azure · you approve changes Outbound HTTPS Data centerBranch office

Passwords and keys never reach an AI model

RealmHelm removes secrets from configurations when it collects them. They are never sent to an AI model.

Microsoft Entra ID

Admin, Operator and Read-only groups for each deployment.

Azure Key Vault

RealmHelm fetches device credentials from Key Vault for each run.

Appliance protection

Signed updates and a web application firewall.

Supported platforms

Check support for your equipment

Every platform gets monitoring. Backups, changes and firmware upgrades depend on the platform.

Network platformBackupsMonitoringChangesFirmware
Arista EOS✓ yes✓ yes✓ yes✓ yes
Cisco IOS and IOS XE✓ yes✓ yes✓ yes✓ yes
Cisco NX-OS✓ yes✓ yes✓ yes✓ yes
Fortinet FortiOS✓ yes✓ yes✓ yes✓ yes
Cisco IOS XR✓ yes✓ yes– no– no
Dell OS9✓ yes✓ yes– no– no
Cradlepoint, through NCM– no✓ yes– no– no
Siklu EtherHaul✓ yes✓ yes– no– no
Ubiquiti airFiber✓ yes✓ yes– no– no
Arista EOS
Backups
Yes
Monitoring
Yes
Changes
Yes
Firmware
Yes
Cisco IOS and IOS XE
Backups
Yes
Monitoring
Yes
Changes
Yes
Firmware
Yes
Cisco NX-OS
Backups
Yes
Monitoring
Yes
Changes
Yes
Firmware
Yes
Fortinet FortiOS
Backups
Yes
Monitoring
Yes
Changes
Yes
Firmware
Yes
Cisco IOS XR
Backups
Yes
Monitoring
Yes
Changes
No
Firmware
No
Dell OS9
Backups
Yes
Monitoring
Yes
Changes
No
Firmware
No
Cradlepoint, through NCM
Backups
No
Monitoring
Yes
Changes
No
Firmware
No
Siklu EtherHaul
Backups
Yes
Monitoring
Yes
Changes
No
Firmware
No
Ubiquiti airFiber
Backups
Yes
Monitoring
Yes
Changes
No
Firmware
No

Servers and virtualization: Windows and Linux servers; VMware inventory and captured state through vCenter and its ESXi hosts.

Server controllers: Redfish, including Dell iDRAC, HPE iLO, Supermicro, and Lenovo XClarity.

Cameras and other equipment: Milestone XProtect camera inventory and image checks. Monitoring for devices that answer SNMP or ping.

Inventory sources: PRTG, Active Directory, Milestone XProtect, Cradlepoint NCM, network scans, and CSV imports.

Pricing

Priced per deployment and device

Each deployment has a base subscription. Device charges depend on the types and number of devices.

Buy directly or through Azure Marketplace

Buy directly from NetPrecedent, or ask us to set up an Azure Marketplace private offer.

One agreement for MSPs

Each customer keeps a separate deployment. Ask about one agreement that covers all your customer deployments.

Talk to us about pricing for your network

FAQ

Questions

Do I need an AI agent?

No. Your team can do everything in the RealmHelm browser interface. An AI agent is optional.

Which AI agent can I use?

The one you already use. It connects through our MCP server or the rhctl command line, and acts with your permissions.

Can the agent change a device without me?

No. Your agent can read data and plan changes. A change runs only after someone approves it in the RealmHelm browser interface.

What can the agent see?

Inventory, lifecycle dates, configurations and their history, topology, usage, health, vulnerability findings and past changes. It cannot see passwords or keys.

What happens if a step fails?

The run stops at the failed step. You can retry it, skip it with a note, record it as done by hand, or roll back where the platform supports it.

Where is our data kept?

In your RealmHelm deployment in Azure, either in your own tenant or in a dedicated deployment we host. Site agents connect out over HTTPS.

How do MSP staff get access to each customer?

Each customer has its own deployment. Add staff to that deployment’s Operators group.

How is pricing worked out?

A base subscription for each deployment, plus charges based on the types and number of devices. We invoice directly or through an Azure Marketplace private offer.

Talk to NetPrecedent

See RealmHelm in a demo

We’ll walk you through the product and these examples, and talk about setting up RealmHelm for the networks you manage.

Request a demo contact@netprecedent.com

Product screenshot

Enlarged product screenshot