Choose what your team needs to do.

Polls interface counters and router CPU, memory and temperature every minute, and turns the counters into rates without mistaking a reboot for a traffic drop.

Checks each internet link at the gateway and beyond it, so a link is reported as up, degraded or down, and knows which link is the backup.

Measures each provider’s uptime against the figure in your contract, 99.5 per cent unless you set another, and leaves out the periods PureView itself was not collecting.

Raises an alarm when CPU, memory or temperature passes a threshold you set for your environment.

Reads CPU, memory, disk and service state from a server over SSH, and scores each host against a compliance baseline.

Where a host should report in by itself, a small agent sends its metrics using a token issued for that host alone.

Sweeps the ranges you give it, resolves names, and marks the hosts it has never seen before.

Identifies vendor and model from hardware addresses and SNMP, including Cisco model and serial numbers, and declines to guess when the answer is unclear.

Turns a discovered device into a managed one in a single step, with a stored credential attached.

Receives device logs over UDP and TCP, handles time zones, and keeps 30 days before clearing them.

Checks your rules every minute and collects what fires in one inbox. A threshold has to stay crossed before an alert opens, and nothing opens during an approved maintenance window.

When a failure takes out everything behind it, those alerts are marked as consequences and point at the device that broke.

A desktop application that opens your PureView server and adds what a browser cannot reach: a console cable and a scan of the network the operator is sitting on.

In the same application, an engineer can probe a Cisco switch over the console cable, save or push its configuration, and scan the local subnet with no server in reach.

A separate build for people who should watch and not change. The management features are left out of the build, not hidden in the interface.

A full-screen view for the operations room screen, which can run on the local network without anyone signing in.

Applications for phones and tablets, for the people who need to see status away from a desk.

Takes a structured snapshot of a device configuration and keeps what it does not recognise. Two snapshots can be compared section by section.

Generates configuration in each vendor’s own syntax: MikroTik base, VLAN, hotspot and CAPsMAN setups, Cisco including HSRP router pairs, Palo Alto, Omada and UniFi.

Sends configuration to MikroTik and Palo Alto devices and checks it took, and pushes to Cisco over SSH or a console cable.

A hotspot deployment that fails part way is returned to the state it started from.

Tracks address pools, suggests the next free address, and reconciles the plan against what answers on the network.

Describes an intended network independently of vendor, checks it, and produces a deployment plan only once critical problems are resolved.

Device credentials are encrypted with a key belonging to your installation and are never shown back through the interface.

Runs authorised operations on a server: services, processes, users, packages, scheduled jobs, firewall, networking and power.

Power, snapshots, cloning, migration, backups, storage and networking for virtual machines, through each platform’s own interface.

Records sites, buildings, rooms, rows and racks, and draws each rack unit by unit.

Records how power reaches each item, so you know in advance what else goes dark when a feed fails.

Tracks equipment through its life, with what feeds, hosts and depends on what. Imports from a spreadsheet.

Beyond a role, a person can be given a site, a room, a rack, a group or a single device, and sees only that.

A service provider can run one appliance for several client organisations and keep each one’s records apart.

Installs, detects and removes about twenty common applications on a host, among them Nginx, PostgreSQL, Redis, Docker, Grafana and Fail2ban.

Prepares a new server, creates its administrator account and applies a hardening baseline.

Backs up the PureView database, its settings and its certificate authority every day, with a documented restore.

A second appliance that takes over if the first one fails.

Installs from a bundle that carries everything above the operating system, checked against its checksum. The installer refuses a bundle built for the wrong processor.

A new version installs from a newer bundle. Your settings are kept and the database is brought up to date when the appliance starts.

How promptly updates arrive will be yours to choose, including holding them until somebody approves the change locally.

Each installation will carry a signed licence it can verify without a connection.