01
The spreadsheet nobody trusts.
Picture a company of 150 people with two IT admins. They keep a spreadsheet of servers and programs. Someone updates it after a migration, someone forgets, and six months later nobody trusts it. Then the mail server stops at two in the morning, and the question is not “which server is it”. It is “what else stops with it”. The spreadsheet does not know.
AverDesk keeps the same list, but every record is linked to what it serves. The mail server knows which services run on it and which product those services belong to, so “what breaks with it” is one click away. (The record types: products, services, service instances, hosts, hardware, IP addresses, subnets, software, licences, locations, accounts, monitors and backup requirements.)
02
Big lists that still open fast.
The two admins start with 300 records. A year later, after file imports and the agent (a small helper program on the servers) have done their work, there are 20,000. The list still opens in a second, because the server does the filtering, not the browser. They narrow it by any field (facets), save the views they use every Monday, and switch between a compact table and a detailed one. Ctrl+K takes them to any record by name.
03
Your words, not ours.
The company calls its locations “branch” and “warehouse” and wants to know who approved each licence. The admins add those fields themselves (custom dictionaries and attributes). Values can be inherited down the tree: set the location on a rack and every server in it gets it. When two sources disagree, nothing is overwritten quietly. The conflict waits for a person to decide.
04
Who changed this, and when.
A licence count looks wrong. Instead of asking around, the admin opens the field and reads its history: what the value was, who changed it and when. Every field keeps its own log.
05
Documentation that updates itself.
Because the list records which servers, ports, outside services and backup sites each service uses, the list is the documentation. Add a server or retire one, and the documentation changes with it. Nobody has to find a free afternoon to edit the wiki.
