Design partners
No logos yet, and we are not going to invent any
Decim is pre-release. Rather than a wall of borrowed credibility, here is the honest position: we are working with design partners on real production incidents, and there is room for more.
Who we are looking for
Your pipelines are in code you control
Services and scheduled jobs in Python, .NET, Java or SQL, with the code in GitHub. Decim discovers pipelines from the repository, so that is where a pilot starts.
You have had a silent failure
A run that reported success while the numbers were wrong. If you already know the cause, that makes you a better partner, not a worse one: you can check our answer.
You will tell us when we are wrong
A conclusion you challenge, with the reason, is worth more to us than one you accept. It is the most useful feedback we get.
What a pilot looks like
- Connect. Install the GitHub App on the repositories that hold your pipelines, connect Google Cloud Logging or set up the Windows agent where your logs live, and optionally connect Jira.
- Discover. Decim scans a repository and lists the pipelines it finds, each with its trigger and a step graph tied to the code. You tell us where it got something wrong.
- Investigate. Open incidents you care about, ideally including one you have already solved. Read the timeline, the cited log lines and the hypotheses, and run the checks Decim writes.
- Judge. Challenge conclusions you disagree with, look at the draft fixes, and tell us where the investigation was slow, wrong, or blocked by evidence it could not reach.
| Source | Needed | Why |
|---|---|---|
| A GitHub repository | Required | Decim reads it to find your pipelines and cites its code in every investigation. |
| Logs in Google Cloud Logging | If you have them | Define named log sources as filters; the investigation reads them with read-only access. |
| Logs on a Windows host | If that is where they are | The optional Windows agent reads configured directories and Event Log channels. |
| A Jira Cloud ticket | Optional | Linked to an incident, its description, comments and attachments become evidence. |
| Files | Optional | Exports, logs or screenshots you already have, attached to the incident. |
| Someone who can run a query | Helpful | When the deciding evidence is in a database, Decim writes a read-only query for your team to run. |
What you get, and what we ask
You get the product free through the pilot, direct access to the people building it, and influence over what ships next. We ask for real incidents, honest verdicts on the conclusions, and permission to learn from what went wrong. We do not use your evidence to train models shared with anyone else. Evidence is processed by a third-party language-model provider and is not redacted, so the security page is worth reading before you connect anything.
Related: security for what Decim reads and how long it keeps it; pricing for what follows a pilot; and the product for how an investigation works.
Get started
Apply as a design partner
Tell us what you run, how it breaks, and one incident you already know the answer to.