Your estate, resolved.
Three sources, none of them complete on its own, and one row you can work from.
A single host row from many sources
System list
System name and system owner
Hardware inventory
Address, OS, location, vendor
Patch register
The date the last update actually landed
- Host
- SRV-DB-01
- Address
- 192.0.2.41
- Tier
- Tier 1
- Last update
- 12/05/2026
- Cadence
- 3
- Next due
- 12/08/2026
The problem
The inventory already exists. It just isn't in one place.
The system-and-owner list lives in one table, the hardware in a second, and the hosts nobody has migrated yet in a third. Regulaxy does not ask you to merge them; it reads all three and holds the rule that decides between them.
- 01
The spine
Every fully-qualified hostname appearing in any source gets a row. Matching is on the first DNS label, so a short name and an FQDN meet.
- 02
Resolution
Hardware comes from the primary source, and from the legacy one where the primary is silent — but always from the same row, so a host cannot end up with one source's OS and another's vendor.
- 03
Cadence
Exposure tier is derived from the location field, and cadence from the tier. The same derivation computes the next due date, so the two can never disagree.
- 04
Comments
A note written in Regulaxy is stored in Regulaxy's own table and joined onto the row. The source tables stay read-only — they are not ours.
Read-only, with no write-back to any source.
- Microsoft SQL Server
- Oracle
- SolarWinds
- Local patch register
One row per host
Name, address, system, owner, exposure tier, OS, last update, next due and cadence — plus an explicit answer to why a host you are looking for is not there.
Show us your worst window.
Bring the one that keeps slipping. Thirty minutes, your estate, no slides.