Every workstation
QuickBooks release and maintenance build, crashes, freezes, forced shutdowns, print/PDF failures, database-auth errors — trended, not guessed at.
Cadence
The always-on watch for QuickBooks Desktop. Endpoints, the server, and the network path between them — so you find the problem before the bookkeeper calls.
What it watches
The server and company file
Database Server Manager state, hosting mode, company-file growth and .TLG bloat.
The network path
Latency, loss, SMB latency and negotiated link speed between each workstation and the server — the single most common cause of “QuickBooks is slow”, and the thing no other tool watches.
Update control
Pin an organisation to a known-good release, or track the latest. Drift from the pinned build raises an alert instead of being discovered weeks later.
Why it exists
A twelve-machine QuickBooks office had a front-desk station crashing six to eight times a day for weeks before anyone connected the dots. The fleet had quietly drifted across four different maintenance builds of the same release — all reporting the same version number — while the actual fault turned out to be the print stack, not the network, not memory, and not the QuickBooks build.
Generic RMM never surfaced any of it, because generic RMM does not understand QuickBooks. Cadence does.
What it is not
Cadence collects health metadata only. It never reads, transmits or stores company-file contents, transactions, payroll, or any financial data. See Security.