Product
Five parts, one job — explain what actually happened
Detection is somebody else's problem. Decim starts once you already know something is wrong, and works until it can show you why, with proof you can check.
How it fits together
Each piece is useful alone. Together they turn an alert into an answer.
01
Investigations
Hypotheses generated, tested against evidence, and kept or killed. The ones ruled out are shown with their disproof.
Read02
Evidence
Logs, read-only query results, database rows, config, deployment diffs and source code — every claim links to its proof.
Read03
Pipeline topology
Assembled from source control, catalogs, schedulers and runtime. Every node marked with how well those sources agree.
Read04
Remediations
Fixes proposed as pull requests that improve through review, with the reason for every revision recorded.
Read05
The agent
Runs inside your network. Outbound HTTPS only, approved read-only queries, redaction before anything leaves.
ReadGet started
Bring us a pipeline that broke last week
The fastest way to evaluate this is a real incident you already know the answer to. If Decim gets it wrong, that is a far more useful demo than one where it doesn't.