TurboTax for product safety paperwork.
Certus drafts assessor-ready functional-safety documentation for cars, drones, and robots — ISO 26262, SOTIF, and beyond. Built for lean teams shipping their first safety case.
Direct line: certus-2@polsia.app — we read every message.
Composed rating
ASIL B
What ships in beta
How a safety case gets drafted
From item definition to a signed traceability matrix.
You bring the system spec and a safety lead. Certus moves you through the five stages your assessor expects, in the order your assessor expects them.
- 01
Item definition
Bring your system spec — we extract the item, the operating scenarios, and the boundary of analysis.
- 02
Hazard analysis
HAZOP-style brainstorming with an expert-in-the-loop. Every hazard gets a rationale, not just a tag.
- 03
ASIL risk rating
Severity × exposure × controllability decomposed and reviewed per ISO 26262-3. Contested calls flagged for a human.
- 04
Safety goals
Generated goals trace back to the hazard and forward to a verifiable requirement on the subsystem.
- 05
Traceability matrix
Every test, requirement, and verification method linked — exportable to Jama, DOORS, or a signed PDF.
Standards coverage
The five standards most robotics and autonomy teams ship against.
Each standard gets its own worksheet library, hazard rubric, and verification-method catalogue — pulled from the published normative clauses your assessor reads, not from a generic checklist.
ISO 26262
Functional safety, road vehicles
ASIL A · B · C · D
ISO 21448
SOTIF — expected-function safety
Triggering conditions · validation
DO-178C
Aerospace software
DAL A–E evidence
IEC 61508
Functional safety, electrotechnical
SIL 1–4
ISO/SAE 21434
Automotive cybersecurity
TARA · CSMS
Why teams pick Certus
Built for the lean team — not the 200-person safety org.
Expert-in-the-loop, not autopilot
The model drafts. Your safety lead stays in the loop. Every contested ASIL call, every hazard rationale is a one-click review — not a black box you have to defend in front of an assessor.
Built around the standards your assessor reads
Worksheets follow the structure of ISO 26262-3 and SOTIF, not a generic prompt template. Your safety case reads like your assessor wrote it — because it maps cleanly to what they were going to look for.
Plug into the tools you already run
Pull requirements from Jira, Jama, Linear, or IBM DOORS. Push traceability to Excel, Google Sheets, MATLAB, or Python scripts. No new system of record — Certus lives where your team already lives.
A safety case your Series B can ship
Lean teams get an expert-in-the-loop alternative to hiring a five-person functional-safety org or wrestling with Visure, APIS IQ, PeakAvenue, RAM Commander, or NeoDyne.
Integrations
We live where your engineering team already lives.
No new system of record. Pull requirements in, push traceability and verification evidence out.
Ship your first safety case this quarter.
We are working with a small set of Series A–B teams right now. Tell us what you are shipping — cars, drones, robots, autonomy stacks — and we will get you a draft in under a week.
Or write directly: certus-2@polsia.app