Integrations
Four ways data reaches the Register. Most customers use two of them and never touch the others.
File import
CSV and spreadsheet import with column mapping saved as a reusable profile. Unglamorous, and still the most common way a register gets populated for the first time — the information usually already exists in a spreadsheet somebody maintains.
Re-importing an updated file produces a difference rather than a duplicate: new entries, changed fields and entries that have disappeared from the source, each accepted or rejected individually.
Scheduled connectors
Connectors run on a schedule and populate entries automatically. They are organised by category rather than by product, because the category is what determines the shape of the data:
| Category | What it contributes |
|---|---|
| Cloud platforms | Compute, storage, database and network resources with tags and account structure |
| Configuration management | Existing CMDB entries, service definitions, ownership records |
| Ticketing and service desk | Service catalogue entries, change history, incident linkage |
| Monitoring and observability | Service names in active use, and dependencies inferred from call patterns |
| Identity providers | Group and role membership for ownership validation |
| Contract and vendor management | Vendor records, renewal dates, support tier |
| Backup and recovery | Protection coverage and last successful restore point |
A connector never overwrites a human-entered field silently. Where a connector's value disagrees with what someone recorded, both are kept and the difference is raised for a decision. Automated data is good at completeness and poor at intent; the register needs both.
Read API
A read-oriented HTTP API returning inventory, dependency and evidence records as JSON. Authentication is by scoped token. Tokens are read-only by default and can be restricted to particular record types.
The API exists mainly so the register is not a dead end. Teams query it to check ownership during change review, to include continuity data in internal reporting, and to answer the recurring question of what depends on a system somebody wants to decommission.
Webhooks
Outbound notifications on the events worth reacting to: a review falls overdue, an owner is removed from the directory that supplied them, a dependency is added to a Tier 1 system, an export is generated.
A note on connector coverage
We do not publish a logo wall. Connector coverage changes, and a list of supported products tends to be read as a commitment rather than a snapshot. If a specific source matters to you, ask — the answer is either that it works today, that the file import path covers it, or that it does not and we will say so.