ASSET INTELLIGENCE
Every asset. Structured. Connected. Queryable.
Servers, firewalls, workstations, domains, credentials, and how they connect—kept current by the systems your team already runs.
ENVIRONMENT CONTEXT
Stop documenting devices. Start knowing environments.
A technician opening a client should find the relevant systems, records, and relationships already in the right place.
Relationships, not folders
Model what an asset belongs to and what depends on it.
Designed for your environment
Use typed records and custom asset types where your operating model needs them.
Useful in the moment
Make the client context available when a ticket, audit, or change demands it.
THE MODEL
Every record knows what it belongs to.
The password knows its firewall, the firewall knows its client, the client knows its people:
ASSET TYPE DESIGNER
Your MSP isn't generic. Your asset types shouldn't be either.
Build custom record types in the UI, no vendor involvement.
Your fields, your rules
Custom fields, allowed values, required flags, a designated primary name.
Types that match reality
SOPs vs. work instructions as distinct types. Vertical-specific assets for that one manufacturing client.
First-class citizens
Relationships, tags, and Ask Lex answers work on custom types exactly like system types.
ALWAYS CURRENT
Synced, tracked, flagged.
FIG · AST.01
PSA + RMM sync
ConnectWise, Autotask, Halo, NinjaOne, and more feed live device data, so records reflect reality.
FIG · AST.02
Domain & SSL tracking
Certificates and domains are structured assets whose key dates flow straight into Expirations.
FIG · AST.03
Provenance on everything
Who changed what, when: version history, audit metadata, archive instead of delete.
Know the environment before the ticket asks you to.
Bring your connected asset knowledge into one operational view.
