CloudOps · Infrastructure cloud

Product update · Hardware health

Your hardware knows it’s failing before your OS does.

CloudOps now reads fault data straight from your servers’ management controllers and puts it on the same dashboard as everything else. Read-only, every hour, across your whole fleet.

rack A · node 12via iDRAC
Power suppliesredundant · OK
Fans & cooling6 of 6 · OK
Memory1 correctable ECC
Event logFULL since Jul 2025
read 4 min ago · read-only

By the time your OS notices, the spare is already gone.

A failed redundant power supply. A fan that stopped last week. A memory module throwing errors. A RAID array quietly running on one drive. Your operating system finds out about these late, or never, and your monitoring only sees what the OS surfaces.

The controller built into every server has known since the moment it happened. That is what a BMC is for. Until now, nothing was asking it, and the one place with the answer was the one place nobody looked.

The hardwarePSUs · fans · DIMMs · drivesa fault happens, the controller records itManagement controller (BMC)iDRAC · iLO · IPMI · Redfishlate, or neverread directlyOperating systemCloudOpshourly · read-onlyincompletecompleteYour CloudOps dashboard
Both paths end on the same dashboard. Only one of them carries what the controller actually recorded.

One view for a mixed fleet.

CloudOps reads the controller directly and turns what it finds into plain findings on your dashboard, next to everything else you already watch. It works the same whether a rack is Dell, HPE, Supermicro, or a whitebox speaking plain IPMI or Redfish. No separate tool per vendor, no separate tab.

Power supplies & redundancy
Fans & cooling
Temperature
Memory / ECC
Drives & RAID
Chassis intrusion
The event log itself

Dell iDRAC · HPE iLO · Supermicro · any whitebox speaking IPMI or Redfish

The first machine we pointed it at had been blind for over a year.

We switched it on against a single production server and asked for one reading. It came back in seconds with something nobody expected: that server’s event log had filled up in July 2025 and stopped recording. Every hardware event since, more than a year of them, had gone unwritten.

The server looked fine because nothing was left to say otherwise.

That is the exact blind spot this closes, and it was invisible until something finally read the controller.

Event log fillsJul 2025First readingsecondsmore than a year of events, unwrittenNothing was broken enough to page anyone. Nothing was recording either.
A full event log stops recording silently. The gap only becomes visible when something reads the controller and reports its age.

Built to be trusted on production hardware.

Read-only, always

It reads the event log, sensors and component status. It never powers a machine, changes a setting, or clears a log. Nothing it does can disturb a running server.

Automatic, plus on demand

Every server with a controller on file is checked on a schedule. Need an answer right now, after a callout or before a maintenance window? Press Check now and read it back in seconds.

Signal, not noise

Hundreds of repeated log lines collapse into one clear finding, in plain language, with what to do about it. A year-old event is shown with its age, not raised as a live emergency.

If you run bare metal, this is for you.

Colocation, on-prem, edge sites, or a single rack in the corner of the office. Especially if you run more than one hardware vendor and have been checking each one’s own console by hand, this gives you a single place to see what your hardware already knew. You point it at a server; it tells you the truth about that server.

It’s live now.

Add a controller’s address to any bare-metal server and press Check now. That is the whole setup.