Discovery & Inventory

Build a client inventory your team can work from.

Bring device, software and network observations together, then reconcile duplicates and gaps. Check where each record came from and how recently it was observed.

Book a walkthrough Explore asset management

Target scope · verify support before purchase ↗

Discovery and inventory

Observed source, normalized identity, owner, and last-seen state

Scope bounded

Authorized discoveryNo arbitrary scanning

01Scope

Site, subnet, and rate approved

Bounded

02Observe

Device and service signals

Collected

03Normalize

Identity candidates compared

Prepared

04Reconcile

Owner resolves conflicts

Pending

Illustrative Discovery and inventory concept—not a live product screenshot.

The operator’s path

Find the issue. Act in context. Check the result.

Illustrative workflow · explore the steps · no action is executed

Define scope

Choose the authorized site, subnet, collector, endpoint set, credentials, schedule, and scan methods.

Confirm this step for your release, permissions and environment.

Find what exists without silently declaring every observation authoritative.

Collect supported device, software, network, service, address, and relationship observations inside approved scope.

Preserve source and time, surface conflicts, and reconcile before changing authoritative records.

Inside the workflow

The work this connects.

Network discovery: Use supported subnet enumeration, ARP, SNMP, service detection, fingerprinting, and scheduled rescans.
Software inventory: Track installed applications, versions, update intelligence, observed use, and uninstall history by device.
Hardware inventory: Collect supported CPU, memory, disk, board, interface, serial, manufacturer, model, and agent attributes.
IPAM context: Connect IP addresses, DHCP scopes, DNS names, MAC addresses, gateways, and interfaces to observed devices.
Normalization and deduplication: Retain each source observation while resolving records toward one governed device or asset identity.
Custom classification: Apply approved owner, site, cost center, tag, lifecycle, and custom fields without overwriting observed facts.

Try one useful scenario

Resolve conflicting observations

Fictional example: two sources report different owners and an ambiguous software version for one serial number. Preserve both observations and let the authorized asset owner resolve the authoritative record.

Illustrative evaluation scenario, not a recorded product result.

What a useful result must show

Record source, timestamp, confidence, exception, reviewer and accepted identity. Recheck the installed version after remediation; a failed check remains unresolved.

Get the evaluation worksheet →

Check the support boundaries

Scan prerequisites and permission scope
Observed versus declared asset identity
Software publisher/version confidence
IPAM, license usage and retirement evidence

Observed IP relationships are not DNS/DHCP administration or address planning. Software presence is not reliable usage/license compliance evidence; depreciation and QR workflows need their own support record. IPAM on this evaluation page means observed address and relationship context; active DNS/DHCP administration or address allocation is not established. Request the supported inventory field list and scan permission/rate prerequisites.

Check public evidence and availability →

Scope, availability and evaluation details

Scopes, sites, subnets, credentials, protocols, rates, and schedules must be explicitly authorized.

Observation freshness and confidence remain visible; conflicts are not silently resolved.

The proposed $99 monthly model includes the target product scope for evaluation, unlimited technicians, unlimited customers, and the first 50 managed devices. Final terms require confirmation. See transparent pricing →

Review full environment and integration scope

Agent and collector coverage

Agents collect bounded Windows registry, Linux dpkg/RPM/APK/pacman, macOS system_profiler/Homebrew, hardware, and software context; collectors add authorized network and topology observations.

Inventory feeds operational owners

Normalized observations connect to version intelligence, endpoint operations, network operations, IT asset, vulnerability, topology, IPAM, CMDB, policy, and reporting records while preserving provenance.

Discovery feeds RMM, IT asset, network, vulnerability, service, reporting, and migration workflows without replacing their owning records.

Questions, answered

Before you choose your next step.

What can Dayrook discover?

Supported network devices and services, endpoint hardware and software, IP and MAC relationships, and agent or collector observations within authorized scope.

Does discovery require an agent on every device?

No. Network collection can identify supported agentless devices, while an endpoint agent provides deeper hardware, software, and operating-state detail.

How are duplicate devices handled?

Dayrook uses stable identifiers and source-aware matching, surfaces ambiguous candidates, and preserves observation history during reconciliation.

Can scans run on a schedule?

Target design: Authorized sites and subnets can use bounded scheduled rescans with collector health and last-run state.

Your next step

Reconcile a small, known client estate.

Bring an inventory you can compare against. Check discovery coverage, duplicate handling, record sources and freshness before trusting a larger rollout.