Five products. Three jobs.
Your rooms run on a network nobody documented.
Two of these tools tell you what is on that network. One checks the documentation you already have and tells you which parts of it are still true. Two tell you whether the room is going to work, and why it did not. You buy, install and use each one on its own, but they share a way of working: they only read, and every answer arrives with the evidence behind it.
Know what is there.
the recordNobody signs off on an upgrade to a building they have to guess about. One of these gives you the answer this week and leaves; the other stays and runs the estate off it.
CrossScan
The scanner. One read-only pass over a switch and you have the inventory: every port, the device on it, the room it is in, and how sure it is. It reads 9 standard MIBs and matches against 250 device fingerprints across 155 vendors.
"We inherited this building and we have no idea what is in it."
See CrossScan →The platform. It documents the whole estate on its own, then operates it: troubleshooting, capacity, blast radius, and an assistant that answers from the record. 141 SNMP OIDs, 15 collectors, 9 compliance frameworks, and a dashboard that stays under 4 ms from 1,000 devices to 100,000.
"The diagram was wrong before we finished saving it."
See CrossConnect →One is a scanner. The other is a platform.
They are not two sizes of the same thing. CrossScan produces an inventory. CrossConnect runs your estate off an inventory. If you need a list of what is in a building, CrossConnect is far more product than you need, and you will pay for all of it.
| CrossScan | CrossConnect | |
|---|---|---|
| What it is | A scanner.You point it, it reads, it hands you the answer and gets out of the way. | A platform.It holds the estate and everything you do to the estate runs through it. |
| What it produces | An inventory.Every port, the device on it, the room, the confidence, the evidence. Plus low-level health: PoE draw, link errors, per-room AV readiness. | An operating picture.It takes the inventory as a starting point and then goes further: what is misconfigured, what breaks if this link dies, where capacity runs out, what changed at 2am, and why the application is slow. |
| How far it reaches | A site.One seed switch, out to the switches behind it. | The whole estate.Every site, continuously, with routing, addressing, capacity, compliance and change history on top. |
| How long it lives | An afternoon.Run it, export the report, close it. Run it again next quarter and it tells you what moved. | Permanently.It keeps discovering on its own, so the picture is still true in eight months. |
| Where it runs | Your laptop.A desktop app on Windows or macOS. Nothing to host, nothing to stand up. | Your server.One command, inside your walls. It brings its own database. |
| Do you need both? | Usually no. Start with the job you have.If the job is "tell me what is in this building," a scanner does it and a platform is overkill. If the job is "run this estate without being wrong," a scan will not keep you honest past the first cable move. | |
Know what you were told.
the paperworkBefore any of that, there is a folder of drawings, spreadsheets and configs that somebody already paid for. It describes your network. Nobody can tell you which parts of it are still true, so nobody acts on any of it.
CrossTrust
The fact-check. Point it at a folder and it reads your existing documentation, then shows you where your own records contradict each other, with both sides cited to the line. It reads 11 configuration languages, runs 71 settings checks, and when two sources are evenly matched it refuses to pick and tells you the command that settles it.
"We have documentation. Nobody trusts a word of it."
See CrossTrust →It never touches your network. Everything CrossTrust knows came out of a file you already had, which is why it needs no credentials, no access and no change window. That also fixes its limit in place: when it tells you a switch is set a certain way, it means a file in your folder says so, and it dates that file on screen so you can weigh it yourself.
If you want the network read directly rather than the paperwork about it, that is CrossScan above, or CrossConnect.
Know it works.
the verdictThe room has to work on Monday, and knowing what is in it does not get you there on its own. One of these clears a change before you make it; the other explains the meeting that went wrong when nobody else could.
CrossCheck
Checks a firmware or device change against a model of your own gear and returns Go, Caution or No-Go, with the fix. 15 checks, 23 AV protocols, 7 room types, and published bands: Go at 75, No-Go below 50.
"We upgrade Saturday night and I cannot sleep."
See CrossCheck →
CrossRoom
Reconstructs what the room would have sounded like to the person complaining, then names the device that did it. 11 layers on one clock, in 30-second slices, scored with the ITU-T G.107 model the carriers use.
"The CFO says the call was unusable. Every dashboard is green."
See CrossRoom →How they fit together
Five questions. One rule: show the evidence or say nothing.
Buy one and it works alone. There is no shared login here and no bundle price. What they share is a discipline. All five read and never write. All five show you the evidence behind every number they put on a screen.
CrossScan
“What is even on my network?”
An afternoon, once
Point it at one switch. It follows the wire to the switches behind it, names the gear on every port, works out which room each device sits in, and hands you the as-built nobody has been keeping.
CrossConnect
“Is it right, and what breaks if it fails?”
Every day, from now on
It keeps discovering the network and holds what you meant to build apart from what it found. Ask it in plain English about health, capacity or what goes dark if a link drops, and every answer cites the record behind it.
CrossTrust
“Can I believe any of this paperwork?”
Before you trust a document
Point it at the folder your drawings, configs and spreadsheets already live in. It reads them, shows you where they contradict each other with both sides cited to the line, and refuses to pick a winner when neither source outweighs the other.
CrossCheck
“Will this change break the room?”
Before you touch anything
It rehearses a firmware change against a model of your gear and checks the things that quietly take AV down: clocking, multicast, QoS, headroom. Then it answers Go, Caution or No-Go, with the fix for your vendor and how to undo it.
CrossRoom
“Why was that call so bad?”
After the meeting
It rebuilds the call thirty seconds at a time and scores what the people in the room actually heard. Then it blames one layer and names one device, or says inconclusive when the evidence will not carry more.
The same three rules, in all five
Which one do I need?
Find the sentence you have said out loud this year.
Most people arrive here because one question is on fire. Start with that one. You are not expected to want all five.
"We just took over this campus and nobody knows what is in the racks. I need an as-built and I need it this week."
CrossScan →
"We have a diagram. It is wrong, and it has been wrong for two years, and every audit starts with three weeks of rediscovering our own network."
CrossConnect →"We have drawings, a spreadsheet and a folder of configs. They do not agree with each other, and every job starts with somebody walking to the comms room to find out which one is lying."
CrossTrust →
"There is a firmware upgrade in Saturday's window and the last one took the boardroom down for a day."
CrossCheck →
"An executive said the call was terrible. Every device was up. I have nothing to tell them and it will happen again."
CrossRoom →
The thing all five do
When one of these tools is not sure, it lowers the score and tells you why.
Any tool can sound confident. The hard part is being uncertain in a way you can act on. So a gap in the evidence is never rounded away or quietly filled with the likeliest answer: it comes off the score, it gets named, and the one thing that would close it is named beside it. Here is what that costs, in each product, as a real number.
no answer
What CrossTrust returns when two documents disagree and neither outweighs the other. It names the command that settles it instead.
60
The highest a CrossCheck verdict can reach when the firmware came from your memory. A Go starts at 75.
74
The highest a CrossRoom verdict can reach when a layer was not instrumented. Good starts at 80.
14
Devices in the CrossScan demo it declined to name, out of 43. All fourteen still on the map, in grey.
unknown
What CrossConnect returns for a service it has no telemetry for. Never green.
- CrossTrust: it will not break a tie it cannot break A value is only ever named as current on a strict win: it has to be legal, outrank every source that disagrees, and be no older than any of them. Two evenly matched documents get no winner and a named next step instead, because the satisfying answer and the true one are not reliably the same answer.
- CrossScan: unknown is a finding In the scan on its own page, fourteen of forty-three devices stayed quiet and it could not identify them. They are all still on the map, in grey, listed by port, with the little it does know about each. Leaving them off would be the easiest lie in the product.
- CrossCheck: you cannot type your way to a Go A firmware version you typed from memory is trusted at 60%, and the whole verdict is multiplied by it. A perfect change on a model you typed still lands on 60, which is a Caution. Read the device instead and the multiplier disappears.
- CrossRoom: a half-seen room cannot look healthy Miss a layer that mattered and the verdict is capped at 74. Good starts at 80. The arithmetic makes it impossible for an under-instrumented room to present as fine, and the report names the integration that would lift the cap.
- CrossConnect: it will say it does not know A service with no telemetry comes back unknown rather than green. A service that is healthy inside your walls says, in writing, that the far end is unobserved because no flow source is wired. It never claims to have checked something it did not check.
The limits
The same honesty, drawn as a line none of them will cross.
A score that lowers itself is one half of it. The other half is a set of things these tools simply will not do, no matter how convenient it would be to do them.
- Read-only. No SNMP set, no config push, no traffic mirroring. They read what the network already knows about itself and hand you the change to make.
- Everything runs on your own machine or your own server. Each product has a feature or two that reaches outside your walls, the AI assist among them. Every one is off until you switch it on, and shows you what it would send. Leave them all off and the products still work.
- A red light is where the work starts. These are diagnostic tools, and a tool that hands you an alarm and stops has left you where it found you.
- None of them is finished on day one. Each starts with what it can read on its own and gets sharper as you connect the next source. The first verdict is a to-do list. The tenth is one you would stake a change window on.
Try one
Nothing you click will change anything. Neither does the product.
Five demos, one per product. Nothing to fill in and nothing to install. Each one takes about a minute and ends on a real screen, with a line telling you what to look at.