Expected receipt
The calendar knows when evidence should exist. Silence after that window is a fact, not an empty cell in a report.
Nightwatch / Evidence engineBuilt for the backup that looks successful
Backup assurance, with receipts
Like a
senior tech, watching every backup.
The green dashboard is not the evidence. Nightwatch checks that a backup arrived in its expected window, reads what happened, then compares the result with the resource’s own history. It is built for the successful-looking backup that has quietly stopped protecting anything.
Vendor-agnostic. Read-only. Evidence stays attached to the resource.
Signal types on the left, the customers carrying them on the right. Weight follows the evidence, not the alphabet.LIVE SAMPLE
One record, three readings
Read the pattern, not the colour.The same evidence stays useful to an operator and legible to a customer.01 / ReceiptDid it arrive?Expected evidence, in its actual window.
02 / OutcomeWhat did it say?Success, warning, failure or review.
03 / ContextDoes it fit?Its own normal, on that day, for that resource.
Built around the tools already sending proof
Example evidence sourcesNot a compatibility list or an endorsement. The important part is the evidence, not the vendor badge.
Built to make absence and drift visible
A backup is a chain of proof, not a status badge.
Forty-seven green ticks, and the backups were empty for a fortnight. That is the failure this exists to end: the estate that looks fine right up until the restore. Every action traces back from the expected backup to the evidence that raised it.
Actual outcome
The original backup evidence determines success, warning, failure or review. Flexible metrics do not get to quietly redefine it.
Resource context
Tuesday is compared with Tuesdays. A green job that shrinks, slows or disappears from its normal range becomes a useful signal.
The evidence desk
A working surface, not a marketing illustration.
The product is deliberately dense where the decision needs detail: status history, expected windows, source evidence and the context that turns a strange-looking result into something actionable.
Receipt gap
It stopped reporting.
Expected evidence stops arriving, and the absence is visible in the same history that establishes its normal backup rhythm.
Outcome + context
It said it was fine.
The stated outcome stays visible beside the evidence that puts it in doubt: zero transfer, a sudden size collapse, or behaviour outside its own range.
Learned normal
It was about to break.
Trend and range make a slow operational change visible early enough to plan work, rather than discover it during a failed recovery.
Operational truth, ready to explain
The risk should be visible. So should the work.
Nightwatch gives an MSP team the evidence it needs to act, then makes the result clear enough to support a customer conversation, an insurer questionnaire, or an audit. It does not manufacture confidence with a dashboard colour.
01MSP
Clear operational actions
What changed, which resource is affected, and the evidence that caused the action.
02TRACE
Resource-level history
Receipt patterns, outcome, metrics and context stay tied to the same protected resource.
03TRUST
Customer-ready proof
A reassuring view of active monitoring without dumping internal triage onto the customer.
04PROOF
Evidence that keeps
Dated report snapshots and success history, on hand for the insurer questionnaire, the audit, and the quarterly review.
Reserved for named customer proof after launch: a published outcome, recognised logo, or attributable quote. Until then, this page does not manufacture social proof.
See it without the pitch
Open the sample environment. Find the lie yourself.
The product tour uses sample data and shows the actual dashboard, action queue, intelligence and metric evidence. Nightwatch does not control backup jobs.