Designed for these patterns.
Guardian Gaze is in early access during 2026, with design partner engagements running across UK financial services, healthcare, e-commerce and managed service providers. Named case studies will appear here as those engagements complete and we have permission to publish.
Used by teams at
What we built the platform around
Five patterns, drawn from how the platform is actually used. These are the workflows that earn their keep against the cost of running it.
Third-party risk management
A CISO office monitoring a portfolio of vendors, typically 50 to 500, across financial services, healthcare or another regulated industry. Continuous external ratings replace static questionnaire-driven reviews, and new vendors are baseline-rated automatically. Read the use case →
Supply chain monitoring
Going beyond direct vendors to map shared infrastructure dependencies, so hybrid attack paths are explicit rather than assumed. Visible to the board, exportable to the auditor. Read the use case →
Own enterprise and subsidiaries
An organisation rating its own external attack surface continuously, including subsidiaries, regional brands and dev or staging domains. Hybrid and multi-cloud posture scored from outside. Read the use case →
Brand and impersonation defence
Lookalike domains and impersonation found continuously, with the takedown workflow tracking each one to closure and credential exposure surfaced alongside it. Read the use case →
Reporting to the board
A trend report the board can read without a translator, with every number traceable back to a dated finding if anyone asks. Read the use case →
Design partners rather than a logo wall
We are early, and the honest position is that we are running design partner engagements rather than presenting a customer roster. Putting up borrowed logos or unattributed quotes would be the conventional move and it would be the wrong one, the buyers we want are precisely the ones who check.
What a design partner engagement means in practice: a defined scope, direct access to the people building the platform, and influence over the roadmap, in exchange for real feedback on findings quality and workflow fit.
It also means we will tell you when something is not ready. A vendor at this stage claiming complete coverage of every workflow is describing an ambition, and the mismatch surfaces three months later when it is expensive for both parties.
Rate your own organisation first
Nearly every serious evaluation begins the same way, and it is the way we would recommend: rate your own company before you rate anybody else's.
It is the only assessment where you can check every finding against what you already know to be true. If the findings are accurate on the environment you understand best, including the inconvenient ones, the ratings on your vendors are worth acting on. If they are not, you have learned that in a week at no cost, rather than after a procurement cycle.
It also answers a commercially live question. Enterprise buyers increasingly rate suppliers before signing, so your own score is what a prospective customer sees, and a poor one costs deals with people who never tell you why.
Ten vendors, one quarter
The pattern that works is narrow and short. Pick the ten to forty vendors whose failure would actually hurt you (not the longest list, the one where a compromise reaches your data or your ability to operate) and rate them for a quarter.
Read the outliers rather than the average. The operational value is in specific findings: the vendor with expired TLS on a payment subdomain, the one whose SPF record permits the whole internet to send as them, the one with credentials in recent breach data.
Then judge it on one question: did the alerting tell you something you would not otherwise have known, in time to do something about it? That is the whole product, and if the answer is no after a quarter, the honest conclusion is that it is not for you yet.
Common questions
Do you have named reference customers?
We are running design partner engagements rather than presenting a customer roster, and we would rather say that than put up logos we cannot stand behind.
What does a design partner get?
Defined scope, direct access to the people building the platform, and influence over the roadmap, in exchange for genuine feedback on findings quality and workflow fit.
How should we start an evaluation?
Rate your own organisation. It is the one assessment where you can check every finding against what you already know, including the inconvenient ones.
How long should a pilot run?
A quarter, across ten to forty critical vendors. Judge it on whether the alerting told you something you would not otherwise have known, in time to act.
What if it does not work for us?
Then it does not, and a quarter is a cheap way to find out. We would rather that than a mismatch surfacing three months into a contract.
Become a design partner
Engagements start with a free rating on your own organisation, which is also how most of them decide whether to continue.
Assessed by domain. No access to your environment required.