Contact
We're working with a small number of safety and certification teams. If you'd like to see Adducia on your own analysis, or just want to talk about the problem, reach out. A real person will read it.
The fastest way to reach us. The link starts a short template; a couple of lines about your team and what you work on is plenty.
Founder. Connect or message there if that's easier than email. Based in the United States; we can meet on a call wherever you are.
What happens next
Your note lands with a person, not a queue. You'll hear back quickly, usually the same day.
Thirty minutes on how your team works today: where the documents live, where the hours go, and whether this actually fits.
We walk through the tool on documents shaped like yours, synthetic or sanitized. Controlled data stays in your environment, always.
FAQ
No. Structured documents are extracted deterministically, row by row. Every artifact ID in an answer is validated against the graph built from your documents, quotes are verbatim and checked against the source, the one judgment step (how columns are read) is shown and correctable, and reports are computed with no AI in the pipeline at all. The model is the interface. The graph built from your documents is the truth.
It stays in your environment. Adducia is built to run where your controlled program data already lives. Anything public, including demos and this site, uses synthetic data that is clearly labelled as such.
No. Your documents are used to build your graph and answer your team's questions, not to train models.
FMEA and FMECA (including multi-tab Excel workbooks with their severity, occurrence, and detection rating scales), FHAs and hazard logs, fault trees, reliability block diagrams, requirements, and V&V matrices, as PDF, XLSX, CSV, or pasted text, including the tables and figures where the real content lives.
Neither. It sits alongside your requirements and analysis tools and hands the engineer organised, source-linked information. Low-confidence reads are flagged for review, and the safety call always stays with the engineer.
We're an early-stage company working closely with a small number of teams. The usual shape is a scoped pilot on your kind of documents, built around one live question your team is actually working. Reach out and we'll shape it together.