Three tools, three inventories, three truths. One right answer.
Your CMDB reports 1,083 machines, your EDR 715, your directory 472. None of them is wrong: each one only sees part of your infrastructure. Unicity matches their records on the identifiers they share, and builds a single inventory where every asset carries the list of tools that see it.
The CMDB record joins the EDR one on the serial number, the EDR record joins the directory one on the MAC address. The CMDB and the directory share no identifier at all: matching them step by step is what brings all three together.
- Nothing is overwritten: you always know which source said what
- Two records from the same tool are never merged
- Recomputed on every sync, and tracked over time
WHY EVERYTHING DEPENDS ON IT
Without one inventory, everything built on top is unreliable
“The same device appeared in AD, MDM and EDR with different information. Several inventories coexisted, but there was no single reliable one.”
Nobody agrees on the number
Every tool reports a different total, and each is right within its own scope. The meeting starts with an argument about numbers instead of what to do about them.
Without a denominator, a rate means nothing
“92% EDR coverage”: out of what? If the real number of assets is unknown, the metric is decoration. Unicity provides the denominator that makes the measure honest.
Blind spots live in the gaps
A machine seen by the directory and by nothing else is either decommissioned but still live, or live but unprotected. Both cases call for action.
HOW IT WORKS
What happens between your tools and your inventory
Matching two inventories is not a join on the machine name. Identifiers are not all worth the same, and no source is reliable on every field. That is where the quality of the result is decided.
- 01
Your tools carry on as they are
Every source sends its records, through an API, through OutPost or through DropPoint. No data re-entered, no migration: your tools remain the system of record.
- 02
OverView spots what describes the same asset
Serial number, MAC address, machine fingerprint, hostname: OverView cross-checks the identifiers your tools provide. Matching is tuned to your stack, not applied blindly.
- 03
One record, with nothing lost
Records describing the same asset become a single record, which keeps every identifier, every attribute, and the trace of the source behind each value. A gap between two tools shows up instead of disappearing.
- 04
Every asset knows which tools see it
The unified asset carries the list of tools reporting it. You stop comparing totals: you see which asset is missing from which tool, and who needs to fix it.
- 05
Recomputed on every sync
Your infrastructure moves, and so do the sources. Matching is redone at every collection and kept over time, so the inventory does not go stale between audits.
BEFORE · AFTER
The same infrastructure, two ways of talking about it
Without one inventory
With Unicity
Without one inventory Three tools, three totals, a meeting to settle it
With Unicity One number, the same for everyone
Without one inventory Coverage rates worked out against an unknown base
With Unicity Rates measured against the real inventory
Without one inventory Machines known to one tool only, and nobody aware
With Unicity Those machines surface on their own, ready to be dealt with
Without one inventory A spreadsheet cross-checked by hand every month
With Unicity Matching is recomputed on every sync
Without one inventory An AI assistant answering with the first number it finds
With Unicity An assistant reading an inventory it never had to guess
NOT JUST MACHINES
Ten asset families, one reference
Unicity does not stop at hardware. Anything that shows up in more than one tool deserves to be matched.
Machines
Workstation, server, mobile, virtual machine: one record, whatever its names in the directory and in the EDR.
Users
One person stays one identity, however many accounts they hold in your directory, your IAM and your applications.
Software
An installed version counts as a single entry, instead of one per vendor naming convention.
Business applications
The link between an application and the machines that run it, whichever source declares it.
Agents
Which tool is actually deployed, on what, and and most importantly where it is missing.
Backups, licenses, roles, compliance
Same treatment, same reference: matching is not limited to the hardware inventory.
WHAT IT UNLOCKS
Metrics that do not exist without Unicity
These measures compare sources against each other. They are impossible to produce while every tool stays in its silo.
- Machines by number of sourcesSpots assets seen by a single tool
- Unicity directory ↔ other sourcesInventory inconsistencies and undeclared assets
- Unicity CMDB ↔ other sourcesWhat your CMDB is missing, by asset type
- EDR coverage of serversAgainst the real inventory, not the EDR’s own scope
- Machines active in the directory, inactive in the ITSMRecords to close, workstations to find
- Duplicate hostnamesThe naming conflicts that break your automation
THEY DID IT
Métropole Européenne de Lille unified three siloed inventories in two months
Infrastructure, applications, users: three inventories maintained by hand, with no link between them, under NIS 2 pressure and a change of leadership. They were matched into a single inventory kept up to date automatically, without rebuilding anything.
Read the case study →
3 inventories out of 3 unified in 2 months
FREQUENTLY ASKED
What your teams will ask
Ready to take back control?
Plug in your sources, see for yourself in 14 days. Free access, no commitment, 45-minute setup.
Start for free