vulgate.
EvidenceCorpusVendorsCompany
Request access
Capability intelligence for security evaluations

Evidence,

not answers.

An RFP requirement goes in. Ranked vendor candidates come out — every claim backed by a citable passage from the vendor’s own documentation, with a source URL and a date.

See a sourced matrixHow the evidence works
The problem

Time kills all deals.
Now it kills relationships.

Clients can’t run eight-month evaluations anymore. They expect their partners to arrive with definitive collateral — comparisons, capability matrices, deployment evidence. Yesterday.

And here’s the asymmetry nobody says out loud: a solutions provider carries hundreds of technology partnerships. No technical staff on earth is expert in all of them — but they still have to operate across every one. So they’re already leaning on AI to fill the gaps. When AI fills a gap with something that isn’t true, the damage arrives from every direction at once.

01

The client

feels misled — and remembers who misled them.

02

The winning vendor

is furious. Their win is now built on claims they never made.

03

The losing vendors

are furious. They lost to evaluation criteria that were wrong.

One hallucinated cell in one matrix, and you’ve spent trust with everyone at the table. That’s not an error rate. That’s an extinction risk.

Live example
Requirement — “Agentless discovery of OT assets across Purdue L2/L3”
VendorClaimEvidenceSource
Claroty xDomeExplicit
“Passive monitoring via SPAN/TAP requires no endpoint agent…”
qualifier: requires CTD sensor appliance
docs.claroty.com/…
last modified 2026-05-14
Dragos PlatformQualified
“Passive collection of industrial network telemetry…”
qualifier: passive collection only in Platform tier
docs.dragos.com/…
last modified 2026-06-02
Vendor CSilent
No documentation found. Silent never renders as “does not support.”
flagged for vendor verification

Three vendors, three different answers — and every one of them survivable in front of the client, because every one of them is sourced.

The evidence contract

Four things every claim carries.
One thing we will never say.

Explicit

The documentation directly states it.

Implied

Adjacent documented functionality strongly suggests it.

Qualified

Stated — with a tier, dependency, or limitation attached. The qualifier travels with the claim. Always.

Silent

Nothing found. And silent never renders as "does not support."

Vendor documentation is incomplete. Absence of evidence is not evidence of absence — and a platform that pretends otherwise is manufacturing the exact liability you came here to escape. Every claim also carries its age: retrieval date, source-modified date, and a visible flag when it’s old enough to deserve re-verification.

How it works
01 — Collect

Vendor documentation, gathered at the source — politely and transparently. No scraping arms race, no evasion. Gated docs go through the front door: partner channels and direct verification.

02 — Structure

Every page chunked with its full heading context, tagged by capability, with qualifier language — "requires," "only available in," "beta" — extracted and pinned to the claim it modifies.

03 — Rank

Each vendor scored on the strength of its best evidence, never on page count. A vendor with 40 precise pages outranks one with 4,000 pages of noise. Corpus size is a bias; we remove it.

04 — Deliver

Work inside the platform, or let the data come to you — matrices exported with citations intact, evidence pulled into your existing proposal workflow.

For vendors

Your documentation is your best salesperson.
Let it work.

Evaluations move at machine speed now — and somewhere right now, an AI is describing your product without you. Vulgate is the alternative: solutions engineers who are accurately conversant in what you build, in your own words, at the exact moment a client is evaluating your category. Enablement that’s present during the deal — not six months before it.

Your words, only

Every claim about you is quoted from your documentation — cited, dated, faithful. Not analyst takes, not reviews, not our opinion. Improve your docs, and your representation improves the same day.

Credible because no one can edit it

No vendor can massage their row — including you. That neutrality is exactly what makes your row worth believing when a buyer reads it.

Silence is never "no"

Where your docs are quiet, we say "no documentation found" — never "does not support." Qualifiers travel with every claim, so your nuance survives the matrix.

Verify your documentationVerification is free. It always will be.
Where this is going

The parity gate

Capability evidence answers "who can do this." It deliberately doesn’t answer "who should we lead with" — that’s a business decision. Deal-context overlays (delivery history, margin, certifications) apply only after vendors tie on documented capability. Evidence ranks. Business breaks ties. The layers never blend silently.

Delivery evidence

Capability evidence says the product can do it. Delivery evidence says you’ve done it — deployment counts and outcomes from your own CRM, cited like everything else, just with an internal source.

Living coverage

Two tracks: automated collection where vendors publish openly, verified partner submissions where they don’t — plus a standing intake sweep of funding rounds, startup showcases, and analyst lists, so the corpus already knows the vendor your client just asked about.

Fast enough for the deal.
Sourced enough for the relationship.

Request access