Keyhole Software · Verification proof

What's verified. By what evidence. When.

The proof page lists every verification record contributing to this provider's standing. Date and level are public; client identity is anonymised unless the client opts in; underlying data sources are held in the evidence vault.

How we verify Share on X

The record, level by level.

Every level this provider has earned, with what the records at that level actually are, not a generic description. Underlying artefacts live in the evidence vault; what's disclosable is shown here.

On the spectrum · live

ReachDepth of evidenceThe moat

L0Listed
Seeded from the public record. Not yet claimed by the provider.
L1Claimed
A verified owner claims the listing and completes the structured profile.

Cross-referenced against public record.

Trustgent-attested checks of this provider's claims against independent public sources it does not control. Each item links to the source and shows when it was checked.

L2Cross-referencedCross-referenced against 2 independent sources

2026-07-03

Zach Gardner, Chief Architect at Keyhole Software, was a featured presenter at Microsoft's Azure Cosmos DB Conf 2023, demonstrating a custom AI/data engineering solution for hospital call center agents built on Azure Cosmos DB and Azure SignalR.
devblogs.microsoft.comConferencechecked Jul 2026
“Zach Gardner, Chief Architect at Keyhole Software... built a custom solution for hospital call center agents that takes advantage of Azure Cosmos DB and Azure SignalR.”
Zachary Aaron Gardner of Keyhole Software presented 'Using OSS (SignalR, React) to Connect Users to an API in NRT (Near-Real Time)' at the Linux Foundation's Open Source Summit North America 2023 in Vancouver.

Confidentiality

Verified privately. Displayed publicly.

Trustgent verifies privately and displays publicly. The evidence vault holds the underlying artefacts, analytics screenshots, exported CSVs, dashboard read-only access tokens, audited reports. The public proof page surfaces only what the client has agreed to disclose: typically the metric, the window, and an anonymised reference to the engagement.

Every record carries its last-verified date so recency is visible on the page. Automated decay + renewal is designed but not yet live, the schedule (~24 months for L3 ratings, 18 for L4, 12 for L5) ships with the concierge intake documented on how we verify. Until then, records can be revised or retracted via the correction flow, nothing here is set-and-forget.

A cross-section of the evidence vault, records sealed behind a lockplate, a single verified thread surfacing to public view