Request Demo
ZENQIX Discover
Available

Hardware inventory

Maintain the hardware facts an IT team needs to identify, support and plan endpoint lifecycle decisions.

AvailabilityAvailable
WorkflowDiscover → Act → Verify → Prove
Evidence model4 evidence elements
EvaluationAcceptance checklist
Operational need

What the administrator needs to solve.

Inventory becomes unreliable when hardware facts are collected manually or only during procurement. Distributed devices change, move and age outside a central spreadsheet.

Current approach

How ZENQIX handles it.

ZENQIX collects endpoint hardware and operating-system facts into the same device record used for operational status and site context.

Workflow

Requested action and verified outcome stay separate.

01Agent collects supported hardware facts
02Control plane normalizes the record
03Administrators search or filter the fleet
04Changes can be reviewed against device history
Capability

What is currently in scope.

Manufacturer/model where supported

CPU and architecture

Memory

Disk capacity where supported

Operating-system version/build

Serial/platform identifier where supported

Platform status

Availability by operating system.

macOSAvailable

Private-pilot collection path exists.

WindowsPreview

Cross-platform agent build exists; physical acceptance is pending.

LinuxPreview

Cross-platform agent build exists; physical acceptance is pending.

Synthetic product model

Inspect the state the UI needs to expose.

This panel uses synthetic data. A genuine ZENQIX Endpoint screen can replace it only after sanitization and publication approval.

Open Product Proof
ZENQIX Endpoint · Hardware inventoryAvailable
Requested / observed stateCapability-specific endpoint state
EvidenceTimestamped, bounded and tenant scoped
VerificationShown separately from execution

Security

  • Collect only operationally useful fields
  • Keep customer telemetry separate from public website analytics
  • Restrict inventory access through product authorization

Evidence

  • Collection timestamp
  • Observed hardware values
  • Agent identity
  • Device record association

Technical detail

  • Inventory is treated as current evidence, not a permanent truth
  • Unsupported fields should remain unknown rather than be fabricated
FAQ

Technical questions for this capability.

Does ZENQIX collect every hardware field available?

No. The goal is a trusted operational record, not indiscriminate collection.

Can inventory be used without endpoint status?

It can be viewed independently, but combining inventory with heartbeat and site context is what makes the record operationally useful.

Evaluate hardware inventory in your environment.

Use the capability matrix and the written acceptance checklist to confirm whether the current status matches your pilot needs.