oolak / Features / Asset inventory
Asset inventory

Know every asset you own, in one place.

oolak pulls servers, devices and cloud resources from the systems you already use and turns them into one clean list. Every asset has an owner, a team and a level of importance, so nobody has to guess anymore.

A home page that shows where you stand today.

One list instead of five

Records from your inventory, virtualisation and cloud accounts are matched and merged automatically.

Nothing slips through

Hosts that show up in scans but are missing from your inventory are flagged right away.

Every asset has an owner

Owner, business unit and criticality are recorded so the right team is always one click away.

Asset inventory

What's included

  • Assets come in from NetBox, VMware, Hyper-V, AWS, Azure, Google Cloud, Kubernetes, OpenShift and Docker registries.
  • Discovery tools such as runZero and Lansweeper feed the same list.
  • Active Directory and Entra ID accounts and devices are part of the inventory.
  • Virtual machines and physical devices share one model.
  • When two sources disagree, you decide which one to trust for each field.
  • Duplicate records are merged and assets are classified by rules you define.
  • Installed software is listed per asset, together with its change history.
  • Business applications are described with their architecture diagrams.
  • The blast radius of an asset shows what else is affected if it is compromised.
  • End-of-life operating systems and software are tracked automatically.
  • Uptime is tracked through Uptime Kuma.
  • Approved changes are written back to NetBox, so your source of truth stays correct.

See oolak on your own data in 14 days.

We install oolak in your environment, connect your tools and show you your real risk picture. You keep everything it finds.

Start a free 14-day trial → Try the live demo
For engineers

Technical details

How are records from different sources matched?
Assets are matched on IP addresses, host names and source identifiers. Each attribute such as environment, owner or status is stored as a claim from its source, and the claim of the highest-priority source wins. Stale or empty claims drop out automatically.
Can oolak write back to our CMDB?
Yes. Changes to virtual machines, devices and IP addresses are made as change requests, approved by a second person and then applied to NetBox, including interfaces and primary IP assignment.
Which inventory sources are supported?
NetBox, VMware vSphere, Microsoft Hyper-V, AWS, Azure, Google Cloud, Kubernetes, OpenShift, Docker and OCI registries, runZero, Lansweeper, Active Directory, Entra ID, EfficientIP, Red Hat Satellite and ManageEngine.