Asset Management

The problem

Nobody can say what the company owns. The hardware list is a spreadsheet a technician last touched in March. The software licences are in a folder of PDFs, so the true seat count only surfaces during an audit, when it is expensive. The rack diagram is a photograph on somebody’s phone. IP addresses are handed out from memory until two devices collide. When a laptop is finally retired, it goes into a cupboard and stays on the insurance schedule for three more years, because no record says otherwise.

What Solidlio does about it

Assets are captured where they enter the business — at goods-in — and carried through to disposal in one record. A received carton becomes a line item, the line item becomes an asset with its serial and MAC already attached, and that asset stays linked to its location down to the rack unit, its licences, its tickets, its contracts, and its IP addresses. Licences are counted against observed installations, so over- and under-licensing are numbers on a dashboard rather than a discovery during an audit. When the asset reaches end of life, retirement and disposal are recorded actions with a reason and a certificate number, not a status somebody remembered to change.

Capabilities

Built for MSPs and their clients

The same records serve both sides. An MSP works across every client it manages from one screen; each client sees only its own estate.

Tenant isolation is enforced in the data layer rather than the UI: a request carrying no tenant context matches no rows, and a request for another account’s record returns 404 rather than 403 — the existence of the record is not disclosed.

How it works

1. Receive — Open a receiving session against a location and, for an MSP, a client organization. Record each line with quantities, unit cost, serials and MACs.
2. Convert — Turn any line into a tracked asset. Serial and MAC carry over; the owning organization comes from the session, never from the request.
3. Place — Assign the asset to a location, down to a numbered rack unit, and record its power draw and cabling.
4. Licence — Record the software entitlement, assign seats to people or assets, and let the compliance dashboard compare seats against installations.
5. Operate — Link tickets, contracts, change requests and monitoring alerts to the asset. Warranty and end-of-life dashboards surface what is about to lapse.
6. Retire — Record retirement with a reason, then disposal with a method, recipient and certificate number. The asset stays in the record with its history intact.

Compliance and audit

• Creating, editing, deleting, retiring, disposing, transferring an asset and filing a warranty claim each write an audit entry with the actor, the entity, the before and after values, and the caller’s IP.
• Locations carry a separate audit log, readable per location.
• Every IP address, subnet, VLAN, DNS and DHCP change is audited.
• Warranty claims record whether the warranty was valid at the moment of filing, so a later dispute does not depend on recalculating dates.
• Disposal records the method, the recipient or vendor, and a certificate number — the evidence chain a WEEE or data-destruction auditor asks for.
• Software compliance reports over-licensed and under-licensed positions per product, which is the number a vendor audit opens with.
• Credential secrets are stored encrypted and are never returned by the credential list API.

Editions

Asset Management is included in every edition. Editions differ in how many assets an account may own.

The cap applies to creation only. Changing plan never hides or deletes assets already recorded, and the limit is enforced identically across the create form, CSV import, and goods-in conversion.

Integrations