Do we have to replace our CMDB or asset register?

No. You keep every system you run today. Asato connects to them and finds the waste that sits between them.

Stop paying for idle hardware

Q: How does Asato know a device is not running?

The network says so. Asato matches the purchase record, the asset register, the network logs and the support contract for each device, so each device is counted once. A support line is flagged when the hardware it covers is not running. At that organization the CMDB and network telemetry agreed on device status 92% of the time, and that agreement is what made the finding actionable.

Asato checks each support line an organization pays against the hardware that is running, across network, compute and end-user devices. Where a support line covers hardware that is not running, Asato recommends what to stop paying for, with a price and an owner on each line, and acts only after a named person approves: it opens the ticket or prepares the change to the support contract, logs it, and keeps watching. A customer starts with one area and holds a priced list, the Asset Clarity Report, in one week. Asato's fee is a share of the savings, and if it finds no savings, the customer pays nothing.

Headline on the visual page: "Stop paying support on idle hardware." The sentence under it: "Asato checks each support line against what is running: network, compute and end-user devices."

Scope

The job covers network, compute and end-user devices. The published customer results on this page are for network hardware only. No result is published here for compute or end-user devices.

When to use it

The organization pays support or maintenance on hardware and cannot say which of those devices are running.
Purchase records, the asset register (CMDB) and the live network disagree about the same devices.
A hardware support or maintenance renewal is approaching.
A hardware refresh, a migration or a consolidation after a merger has left equipment switched off, in storage or never deployed, and it is still on a support contract.
Supply chain holds the support contract and infrastructure runs the network, and nobody compares the two line by line.

Not a fit

Basic inventory tracking with no need to act on the result.
Replacing an existing CMDB, asset register or IT service management system. Asato works above the tools an organization already runs.
Changing a support contract with no person approving. Nothing changes until a named person approves it.

The problem

Section heading on the visual page: "Why it happens."

Each system keeps its own records, so waste hides between them. For one device there are usually four records:

Record	What it says	Who keeps it
Purchase record	The device was bought	Supply chain
Asset register (CMDB)	The device is in service	Asset management
Support contract	The device is covered, at a yearly price	Supply chain
Network logs	Whether the device is running, and when it was last seen	Infrastructure

A device can be bought, recorded as in service and covered by a support line while the network has never seen it. The support line renews in the gap, because no one system holds all four records.

Measured, at an organization with about 940 network devices (a large US health system; its name is withheld): support renewals were priced against the CMDB. Its purchase records, CMDB and live network had never been compared.

What Asato does

Section heading on the visual page: "How it works."

Asato checks each support contract against the hardware that is running. The sentence that sums up the job: match each support line you pay to a device that is running.

Link (Asset Knowledge Graph): each device is counted once. Asato matches purchase records, the asset register, network logs and support contracts, so each device is counted once and tied to the team that owns it. The customer keeps every system it runs today.
Think (Data Intelligence Engine): each idle line gets a price and an owner. Asato's recommendation names each support line on hardware that is not running, what it costs a year, and the person or team that owns it.
Execute (Agentic AI): a named person approves, then Asato prepares the contract change. Nothing changes until a named person approves it. A person the customer names approves each fix, or sets a policy that governs fixes of that kind. Asato then acts on the approved recommendation: it opens the ticket or prepares the change to the support contract, logs it, and keeps watching for new idle hardware.

Measured, at that organization: four source systems were connected read-only and more than 60,000 records were normalized in the first week of a four-week engagement.

What the customer gets back

Section heading on the visual page: "Your Asset Clarity Report."

The Asset Clarity Report: a priced list of what to stop paying for in one area, with the owner of each item. For this job, each row is one support line that covers hardware that is not running, with the device, its site, when it was last seen on the network, its owner and its yearly support cost. It takes one week and is built with read-only access.

The report on the visual page shows example data, not a customer result.

Measured results

Every figure below is from one customer, the organization with about 940 network devices. It is described, not named. "Found", "approved" and "saved" are different figures and are reported separately. Figures that are not savings are labeled "Measured". No approved or saved figure is published on this page.

Section heading on the visual page: "What one organization found."

That organization, network hardware (Found). In a four-week engagement the customer matched about 940 network devices, bought from two network vendors since 2020, across purchase records, the CMDB and the live network. 55% of those devices were paid for and not running. Support was still billing about $466K a year on network hardware that was not running. The $466K a year is found, not yet reported as saved.
That organization (Measured). About $2.6M is the purchase value of the idle devices. It describes the equipment and is not a saving. Support was modeled at about 18% of purchase price a year.
That organization, on evidence (Measured). The CMDB and network telemetry agreed on device status 92% of the time, and that agreement is what made the finding actionable.
That organization, on scale (Measured). Four source systems were connected read-only and more than 60,000 records were normalized in the first week of the four-week engagement. Support renewals were priced against the CMDB.

Case study: Support still billing on idle network hardware

What a customer says

Jay Indrakumar, SVP and Head of Technology, WellStreet Urgent Care: "With Asato's platform, we have a real-time picture of our IT estate. We streamlined IT ops, using only what our teams need, improving our efficiency, all in weeks, not months."

WellStreet Urgent Care is a named customer. The quote is tied to none of the figures on this page. On the visual page it stands by itself, with WellStreet Urgent Care's logo and no heading, between the Asset Clarity Report section and the offer.

Figures on the visual page, with their captions

On the visual page a caption takes no room: it shows when the reader points at its figure, or taps it on a touch screen. Each caption is given here in full. The figures build up as the reader reaches them (the invoice is checked line by line, the dots turn to rings, rows arrive in turn) and then hold their complete state. The values below are the complete ones.

Support invoice, checked against the network. Example data. "One support invoice, checked line by line against the network. Three of its five lines pay for hardware that is not running: $5,610 a year." Of $30,910 a year billed on the five lines, $5,610 a year is on hardware that is not running.
About 940 network devices, bought since 2020. One organization. "Each dot is about 9 devices. The green rings were paid for and not running. Measured in a four-week engagement: the CMDB and network telemetry agreed on device status 92% of the time. Customer data, rounded." The grid draws 45 of its 100 dots as "Active" and 55 as "Paid for, not running", and keeps the key "Each dot is about 9 devices." in view. The figure states 55% (Found), about $466K a year (Found) and about $2.6M (Measured).
One device as four systems record it. Example data. "One access switch, as four systems record it. Three say bought, in service and covered. The network has never seen it, and the support line renews at $1,180 a year."
Link, Think, Execute on the same switch. Example data. "The same switch, followed through the three steps: one record, then a price and an owner, then a contract change prepared once a named person approves."
The Asset Clarity Report. Example data. "The Asset Clarity Report for one area: one row for each support line on hardware that is not running, largest first. Each line has an owner and a yearly price." The example lines come to $17,910 a year, found.

On every figure a green ring marks hardware that is not running or a figure that is Found, and plain white marks Measured.

Who uses it

CTO or infrastructure lead: sees what is running and what is not, with each device counted once and the network's own record of when it was last seen.
Hardware asset manager: gets a register matched to the network, device by device, with an owner for each item.
Supply chain: holds the support contract, and gets each support line on idle hardware priced, with the change to the contract prepared once a named person approves.
CFO: signs, and sees found, approved and saved as three separate figures.

The visual page has no section by role.

How a customer starts, and what it costs

Section heading on the visual page: "No savings, no fee." The line under it: "Your Asset Clarity Report: a priced list of savings, in one week."

The action: the button "Get your Asset Clarity Report", which leads to https://www.asato.ai/talk-to-sales.

The offer: one area, one week, read-only access, and the Asset Clarity Report. Asato's fee is a share of the savings. If it finds no savings, the customer pays nothing.

What Asato reads

Records about technology: purchase records, the asset register, network logs and support contracts. Contracts and invoices are read only if the customer connects them.
Asato never reads employees' documents, email or messages.
Read-only by default. Write access where the customer grants it. The first week, in which the Asset Clarity Report is built, is read-only.

Questions

The page shows at most five questions, the ones that belong to it. Any others are kept here for agents.

The visual page shows the first three of the questions below.

How does Asato know a device is not running?

Asato matches the purchase record, the asset register, the network logs and the support contract for each device, so each device is counted once. A support line is flagged when the hardware it covers is not running. At that organization the CMDB and network telemetry agreed on device status 92% of the time, and that agreement is what made the finding actionable.

Will Asato cancel support or switch anything off?

Only once approved. Nothing changes until a named person approves it. A person the customer names approves each fix, or sets a policy that governs fixes of that kind. Then Asato opens the ticket or prepares the change to the support contract, logs it, and keeps watching.

Does a customer have to replace its CMDB or asset register?

No. The customer keeps every system it runs today. Asato connects to them and finds the waste that sits between them.

What access does Asato need?

Read-only by default. Write access where the customer grants it. The Asset Clarity Report is built with read-only access: Asato reads records about technology, plus contracts and invoices if the customer connects them. It never reads employees' documents, email or messages.

How long until the customer holds a priced list?

One week. The customer starts with one area and, in one week, holds the Asset Clarity Report, a priced list of what to stop paying for, with the owner of each item. (The visual page answers this in its offer section, not as a question.)

What does it cost?

Asato is paid mostly on results: a small share when it finds a saving, and the larger share only once that saving shows up on the customer's invoice. If it finds no savings, the customer pays nothing. Prices are not published.

What happens after the first week?

The first week finds the waste. After that, a subscription keeps Asato running: it carries out the fixes the customer approves and keeps watching, so the waste does not creep back.

Is the $466K a year a saving?

Not yet. It is what that organization was paying in support for network hardware that was not running, measured in a four-week engagement. It is found, not yet reported as saved. The $2.6M figure beside it is the purchase value of the idle devices and is not a saving.

Next step

Request the Asset Clarity Report, or a demo, at https://www.asato.ai/talk-to-sales.

Last updated: 2026-10-06