vciy

Make the call with confidence. Keep the proof.

Paste what you run and see every CVE that touches it, with the evidence behind each one. Record your call with that evidence frozen beside it. When the evidence moves, you hear, and the next reviewer opens your record instead of rebuilding the case.

Or load a sample stack:
Open our public Log4Shell record

No account. Your browser removes IP addresses and host names before sending, and nothing you paste is kept.

Is it being exploited? What changed?

CVE-2025-62593 in Ray. A CVE is the identifier for a known software vulnerability.

Open this CVE

Read the state. See exploitation, severity and movement together. Open a receipt to inspect the source behind a value.

vciy evidence for the Ray vulnerability: exploitation, severity and movement, with receipts to inspect their sources.

Actual page, captured 19 September 2026. Open this CVE to inspect the sources and check a version.

Why vciy exists

Public feeds overwrite history. Your team pays the reconstruction tax.

Compliance by standard
Eliminate repeat triage

Stop rebuilding the case from scratch

NVD, CISA KEV and EPSS update in place. Six months after you defer or accept a CVE, the public page shows today's scores, not what was true when you signed off. vciy freezes the upstream state at the moment of your call so no engineer ever reconstructs old evidence by hand.

Pass audit sampling in seconds

Hand the reviewer a verifiable receipt

SOC 2, ISO 27001, PCI-DSS 4.0 and CISA BOD 26-04 examiners sample exceptions past their SLA and ask what you knew on the day you made the call. Replace screenshot folders and Slack archeology with one dated, hash-chained link the reviewer can verify independently.

Reclaim engineering focus

Cut routine feed noise to zero

Once a CVE is decided, routine score churn stays held back. You are paged only when new facts invalidate your specific premise: an accepted risk enters CISA KEV, a federal deadline moves inside your window, or a revised version range hits what you run.

Why engineers trust the evidence

Every value carries a dated receipt. Nothing is taken on faith.

Read the validation disclosure
Bitemporal receipts

Valid time and knowledge time on every fact

Every score, version range and exploitation flag records when it became true upstream and when our index learned it. Where CNA and NVD authorities disagree, both are shown side by side rather than overwritten.

Browse this week's CISA KEV hub
90.86 vs 0.0

Post-cutoff accuracy where frontier models guess

Evaluated on post-cutoff CVEs (receipt 1bad6b0f9c8287eb) with a 0 / 3 vs 7 / 17 fabrication gate. No model output ever enters the fact plane.

Inspect the scored gates
Checks & Balances

Independent verification before a reading ships

When you ask for an analytical reading, a separate verifier model checks every cited CVE, version and claim against the frozen index before a single sentence reaches your screen.

Compare against NVD, EPSS and Kenna
Step 1 · Freeze the call

Your call is the part the feeds don't keep.

The CVE page gives you the public evidence. Your decision record keeps your verdict, your reason and the evidence frozen when you record it. Put its link in the ticket so the next reviewer can inspect the basis for your call.

Sign in to keep your first 100 decision records free. Reading the CVE stays public.

See how Decision Vault works
vciy's own public exampleMitigated

CVE-2021-44228 Log4Shell

Upgraded log4j-core to 2.17.1 across every service during the December 2021 disclosure window.
Recorded
12 September 2026
Evidence
Frozen when the record was created
Check
Inspect the evidence and verify the hash chain
Open this decision record

Retrospective worked example: the 2021 action was recorded in September 2026. Its frozen evidence is from record creation, not 2021. Customer records are private.

Step 2 · Watch the premise, silence the noise

Record the call once. Hear only when it breaks.

How Decision Watch works

While your call holds, the routine alerts on that CVE are held back, and the weekly all-clear says how many. When new evidence breaks the call, you hear first, with the reason in one sentence: CISA lists an accepted risk as exploited, CISA's deadline moves before your patch-by date, or a revised range now covers your version. Decision Watch runs on every record, free ones included.

Step 3 · Compounding institutional memory

Smarter alerts. See what matters and why.

The more you use it, the better it gets: AI that learns your preferences and helps you reclaim your inbox. Press "Not relevant to us" and the CVE goes quiet until new evidence breaks that call. Every preference is a line you can read and remove. vciy's own model reads them before an alert reaches you, and a KEV listing, a CISA deadline change or a broken call always reaches you.

Step 4 · Cross-team incident records

An investigation your whole organisation can find.

How investigations work

Had an incident, or a near miss? Open an investigation from the CVE page. It keeps what happened, who owns it, the products and CVEs involved and when to check back, with the evidence on its CVE frozen the day it opened. A year later, someone in another team finds it by searching your records. New evidence reaches you while it is open, and closing it adds a version that says what you found.

When the public record is not enough, go deeper inside the investigation: run automated deep code analysis ($49.99 per run) against your code path or call stack, or choose Send me an expert ยท contact us to bring an engineer into the thread.