Introducing Vectry: causal data infrastructure
Why we built a data layer where every event is attributable, every outcome reconstructible, and every anomaly explainable.
Every organization already produces the raw material of explanation: thousands of actions per hour, spread across backends, browsers, devices and workflows. What almost no organization has is the thread — the structure that connects an outcome back to the actions that caused it.
That gap has a cost. Incident reviews turn into archaeology. Audits turn into spreadsheet reconstruction. AI systems act on your operation, and nobody can say precisely why a decision route fired. The data was all there; the causality never was.
Vectry is our answer: a causal data infrastructure layer.
What Vectry does
Vectry captures every meaningful action as a structured, attributable event — who acted (a user, a system, an AI, a device), what operation they performed, over which entity, with which exact changes. Events flow into traces (the local story of one entity) and causal threads (the cross-system storyline that ends in an outcome).
On top of that graph, Vectry generates explanations — the reconstructed chain of causes behind any event, with a narrative a human can read — and detects anomalies wherever the actual pattern breaks from the expected one.
Why infrastructure, not dashboards
We deliberately built Vectry as a data layer, not another analytics UI. Causality has to be captured at write time, with a formal grammar, or it degrades into guesswork. When the structure exists in the data itself, explanation stops being a project and becomes a query.
Open where it standardizes
The capture SDKs — vectry-node, vectry-js-core and vectry-react — are MIT-licensed and open source. One grammar, any stack, and a plain HTTP ingest API for everything else.
Vectry is a Blackwood Stone Holdings company, and the causal backbone of its ecosystem: Sommatic reasons over the graph, Veripass grounds it in verified identity.
Stop guessing. Start explaining.