VCIY is a product of Voxell, Inc., built and run by Jonathan Corners. It keeps vulnerability decisions with the dated facts behind them, for the person who has to explain the call later. The builder's background, record export and continuity arrangements are below.
Jonathan has shipped at every scale this industry has. Through the 1990s he ran mission-critical, 24/7 infrastructure for a global trading company: five datacenters, an in-house multi-currency ERP, and systems that carried the business from $5 million to $100 million in annual sales. He founded and led a 200-engineer consultancy for eleven years. At Avanade he directed solution architecture across a $2 billion portfolio in Japan and North America and led delivery at Visa. He served as Principal Architect at Pariveda Solutions and as Lead Technical Architect for AI at AHEAD. In 1997 he co-wrote Microsoft’s Windows NT Step by Step and tested every walkthrough himself. The habit stuck. His company, Voxell, is an NVIDIA Inception member whose retrieval model held first place on Hugging Face’s MTEB leaderboard at its release. VCIY is what that record builds when it decides vulnerability decisions deserve records of their own.
Vulnerability decisions get made every week and remembered by no one. The evidence that justified them evaporates the day the feeds update. VCIY exists so a decision and the facts it stood on stay together, dated, and answerable for years.
Every screen here was designed by a practitioner-architect, not a growth team, and the product runs on rules that experience wrote. A wrong “not affected” is worse than an honest “unknown,” so clears require exact matches. A claim without a date is a rumor, so every value carries two clocks and opens a receipt. A decision without its evidence is indefensible, so the snapshot is the product. Silence you can trust is worth something, so it gets checked and said out loud. None of that came from a whiteboard. It came from decades of being the person the auditor calls.
Voxell, Inc. owns and operates VCIY. There is no support tier between you and the builder: Custody customers get a direct line, and OTel installs happen in a working session with your own SRE team. We test ourselves in public and publish the losses with the wins: the validation battery and the honest comparisons.
Evidence that depends on its vendor is not evidence. So this one was built to be left, and the commitments are in the contract rather than on a slide.
That is the whole architecture in one sentence: a vendor you can walk away from is the only kind that can honestly hold your audit evidence.