Know what’s connected.

from rooms to buildings to the network

Read-only software that finds and identifies every device on your network.

A drawing running left to right: a conference room with a display, camera and touch panel; a multi-storey office building; and a rack of network switches and servers. Curved connection lines link all three, marked by circles for rooms, buildings and the network.

Most people start with a discovery pass. It takes an afternoon, and it is what makes the other seven useful.

DETECT·CORRECT·PROTECT

What CybrIQ isIn one sentence

Somebody has to know what is plugged into your network, and whether it can be trusted. That is the job. We make eight tools for it, and they only ever look.

AV Technology Best of Show 2026 award, presented at InfoComm

Best of Show 2026 AV Technology, at InfoComm.

What it isBefore you pick anything

What it isSoftware

Runs on hardware you already own. There is no box to buy, and nothing gets installed on the equipment we identify.

What it touchesThe switches you already run

We sign in to the switches already carrying your traffic, using an account that can look but cannot change anything.

What it never doesChange anything, or copy your traffic

It never changes a setting on anything. It never copies the traffic on your network, and it never sits in the middle of it.

Where it stopsIt says when it cannot tell

One demo pass declined to name 14 devices out of 43. It listed all fourteen anyway, with the port each one sits on.

Which one is yoursTwo ways in

Which of these sounds familiar?

Most people arrive with one of these already burning. Find yours and read only that.

Book a 30-minute working session None of these is me

If none of those was youThen start here

Point it at one switch. See what is plugged in.

Every question above needs the same thing first: a real list of what is connected. Hardly anyone has one.

Start with a discovery pass Read the questions first

Nobody has to buy the set. Each of the eight is a whole product on its own, and it works the same whether or not you ever add a second.

Three columns from a switch's port list. The device column names a reception kiosk PC, an access point with four devices behind it, a desk phone, a camera, a presentation gateway and a control panel. The room column gives Reception, Office 210, the Training Room and the Boardroom. The confidence column runs from unknown at 10 percent to confirmed at 100 percent. — **One switch, and what is on it.** The gear, the room it sits in, and how certain the match is. Nothing here was typed in by hand. One switch
demo system

Why you do not already knowFour tools, four blind spots

You already own four things that were supposed to tell you.

Each was built to answer a different question, and each answers it well. None of them was built to answer this one. What falls between them is what the auditor finds.

Network access control

Sees

Anything that signs on to the corporate network the proper way.

Misses

The switch a contractor put in the AV closet, and the four things hanging off it.

Endpoint protection

Sees

Anything that can run its software: laptops, servers, phones.

Misses

Most of the room. A camera, a badge reader and a signage player all refuse it.

The asset register

Sees

Whatever purchasing wrote down on the day it was bought.

Misses

On one campus it accounted for roughly two thirds of what was live on the ports.

Your own drawings

Sees

Whatever was true on the afternoon somebody drew it.

Misses

Every change since. Each job now starts by working out which document is lying.

CybrIQ RoomIQ summary showing 22 rooms: 13 ready, seven at risk or drifted, and two offline. A room search field and clear room-status indicators appear below the summary. — **The meeting rooms that need attention are visible at a glance.** RoomIQ groups the estate into ready, at-risk, drifted and offline rooms, so the next check has a clear starting point. RoomIQ
room summary

Where CybrIQ fits against the tools you already own

How it worksThree steps, and that is all of it

We read your switches and leave them alone.

Your building already keeps this information. We read it without changing anything, and turn it into something you can act on this week.

All eight only read, and nothing gets installed on your equipment. Your security team approves them once, not eight separate times.

01It reads

Your switches already know what is on every port. It asks the switch, and never touches the device itself.

02It compares

That reading goes against a library of known equipment, and against your own records. When the two disagree, you get both.

03You see how sure it is

Every line says where it came from, and a poor match drags the score down until somebody fixes it.

How we tell what a device really is

What arrives, and whenThree moments

What to fix, what broke it, and what the auditor gets.

Every morning What to fix first

Everything it found overnight, worst at the top, in sentences you can act on.

A ranked findings queue. Counters read 7 critical, 335 high, 946 medium, 243 low and 1531 to act on. The highest priority finding reads: single-path AV stream, Studio B floor audio, with the plain explanation that there is no secondary path so a single switch or uplink failure drops the stream. — **The top item, in plain English.** One audio stream has no backup path, so a single failure kills it. Every row tells you what it is based on. Findings queue
demo system

The morning it breaks The change that did it

It worked Monday and broke by lunch, and everybody you ask says they changed nothing.

A verdict banner reading: found the change that broke it, healthy at 11 August 06:31, first broken by a coordinated change across 3 devices at 08:31. Below it a timeline runs green up to a point marked healthy and red after a point marked broken. — **What worked, and what broke it.** Green is the last minute it worked. Red is the first minute it did not. On the left, the line that was deleted. On the right, what replaced it. Network black box
demo system

See the network black box in CrossConnect

The week the auditor comes The pack, already written

Dated, one line per device, so you can hand it over without assembling anything.

A sample evidence pack: a dated per-device inventory record showing what was on each port, how it was identified, and the audit controls each device satisfies. — **Nobody assembles this.** It is the same record the screens are built from, dated and exported. Evidence pack

What changedOne hospital campus

One hospital campus stopped walking closets before audits.

Before every audit, somebody senior spent six weeks walking closets and rebuilding the device list by hand. We swept the campus on a Wednesday. By Friday they had a real list, and they never ran the six weeks again.

6 weeks to 4 days

Audit preparation, before and after.

Devices with no record anywhere. Found, named and dated by Friday.

Switches nobody had recorded, put in by contractors over the years.

Devices run by outside vendors that the IT team could not see.

One Fortune 500 hospital campus, Wednesday to Friday. Anonymized at the customer’s request. Read the engagement

The jobs it gets hired forWhere this shows up on a budget

What people ask on the first callAnswered plainly

No software on your gear. Nothing written. A list by Friday.

Does this put software on my devices?

No. We read your switches. Nothing is installed on anything, and we never copy your traffic.

Can it break something?

Nothing we ship can write to a device, in any product, under any setting.

What happens when it is not sure?

It says so, and the score drops. One demo pass refused to name 14 devices out of 43, and listed all fourteen anyway.

How long until there is a real inventory?

Agree on Monday what to look at. You have a real list by Friday.

Every question we get, answered

Where it stopsAnd why that is the useful part

We publish what we could not identify.

A score that never admits doubt is a score you cannot hand an auditor. So a gap is named, it lowers the number, and it arrives with the one thing that would close it.

devices one demo pass declined to name, out of 43. All fourteen stay on the map with their port, so somebody can go and look.

CrossScan

The most it scores when the firmware version came from memory. A pass needs 75, so it sends you to check the real one first.

CrossCheck

The most it scores when part of the call went unmeasured. A half-seen room reads as half-seen, never as fine.

CrossRoom

no answer

What it returns when two documents disagree and neither outweighs the other. It names the one command that settles it.

CrossTrust

Why this existsWe had the job before we built the tool

Nobody should have to walk the building with a clipboard.

We were the ones doing the clipboard walk. Ten years of running AV and network operations, and every audit opened the same way: six weeks in closets, writing down by hand what the switches already knew. Nobody was going to build the thing that made it stop, so we built it.

Where this came from, and who is doing it