Fennec helps organizations build safer machines that work alongside people. Our Advanced Safety Acceleration Program (ASAP) unites a functional safety platform and automated physical test cells into one connected system.
THE PROBLEM
The constraint on modern autonomy isn't building intelligent machines. It's demonstrating they're safe to assessors, insurers, enterprise customers, and the people working alongside them. Spreadsheets, disconnected documents, and end-of-program testing were never designed for systems that perceive, decide, and change with every software release.
)
OUR SOLUTIONS
ASAP brings together the software and the physical infrastructure required to build and validate intelligent machines, and carry the evidence through certification. Together Fennec's solutions form a continuous safety workflow: define and trace every requirement in the platform, validate it physically in the cell, and carry connected evidence from concept through certification.
)
Functional safety software that connects requirements, hazard analyses, verification evidence, and safety evidence in one traceable system. The platform keeps the work connected while engineers retain every safety-relevant decision.
Explore the Platform)
Automated physical test cells that generate repeatable, measurable validation evidence at the full-system level, in hours rather than weeks, catching what virtual-only testing can't.
Explore TestingFrom Fortune 500 manufacturers to advanced robotics companies, the world's most demanding organizations trust ASAP to power their safety programs.
){kind=logo}
){kind=logo}
){kind=logo}
){kind=logo}
WHO WE SERVE
Ship machines with a certification-ready safety case.
Standardize the safety evidence you require from every supplier.
Replace manual traceability with structural traceability an assessor can trust.
Deploy fleets with defensible, always-current safety evidence.
){kind=logo}
){kind=logo}
){kind=logo}
)
){kind=icon}
ABOUT FENNEC
Our founders built functional safety programs for autonomous systems operating at unprecedented scale, and saw the industry's real constraint firsthand: engineering was moving faster than the tools used to prove systems were safe. Fennec is the company we built to change that, and ASAP is the system we built to do it.
RESOURCES
Assessor and builder: what connected safety evidence changes in practice.
Industry news, company updates, and perspectives from our team, all in one place.
ASAP is our Advanced Safety Acceleration Program, developed inside Amazon Robotics to document, trace, and manage every aspect of the safety lifecycle for an autonomous system. It was created by functional safety engineers who lived the problem firsthand: the spreadsheet morass and traceability bottleneck of designing, certifying, and deploying autonomous systems at scale. In April 2025, Fennec externalized the program from Amazon to bring it to the broader market. Read the origin story. Today, our program includes the ASAP Platform and ASAP Testing.
ASAP is designed for anyone building an autonomous system: mobile robots, drones, vehicles, factory machinery, smart hardware like battery management systems, and software agents making consequential decisions. If your product senses, decides, or acts on its own, functional safety applies to it, whether you're at concept stage, deep in product development, or integrating systems into environments where machines and people work together. In place of disconnected documents and manual administration, ASAP gives you one connected system that carries intelligent machines from design to defensible compliance. Learn more about ASAP.
The platform is standards agnostic by design. It is built around IEC 61508, the parent functional safety standard nearly every sector standard derives from, so its tracking and evidence mechanisms support whatever standard your program answers to. Customers use it today for ISO 12100, ISO 13849-1 (PL supported natively alongside SIL), ANSI/RIA R15.08-1 (builders) and R15.08-2 (integrators), and UL 3100. For AI-driven systems it aligns with ISO/IEC TR 5469, and we're tracking and accommodating the forthcoming ISO/IEC TS 22440.
Both, in one connected safety case. Hardware: upload your Bill of Materials and ASAP calculates reliability metrics (SFF, Diagnostic Coverage, PFH) using the integrated Siemens SN 29500 dataset, replacing hand-built FMEDA spreadsheets. Software: manage software and firmware safety requirements, track releases against them, and maintain IEC 61508-3 compliance, with everything traceably linked so the safety case knows exactly what each change requires you to re-verify.
Adopting ASAP is not a rip-and-replace decision, and it doesn't strand the safety work you've already done. Integration happens at three levels.
Your existing safety data comes with you: Fennec provides migration services that move requirements, hazard analyses, and FMEAs out of spreadsheets and static documents into the platform's traceable structure, so years of prior engineering become the foundation of your safety case rather than a filing cabinet next to it. Your requirements ecosystem stays in sync, with bidirectional API integrations across Jama Connect, IBM DOORS Next, Polarion, Jira, and Confluence, so safety and systems engineering work from one live set of requirements instead of reconciling exports. And safety evidence connects to where engineering actually happens: CI/CD (GitHub, Azure DevOps), simulation (NVIDIA Isaac Sim, MATLAB/Simulink, Gazebo, Unity), and field telemetry (ROS 2, AWS IoT Core), with a REST/GraphQL API for everything proprietary.
This matters because safety evidence is only as strong as its weakest handoff. Every manual transfer between tools is where traceability breaks and assessor questions begin; integration keeps the chain intact from requirement to code to test to field data.
In service of the safety case, never in place of it. AI in ASAP works strictly in an advisory capacity, automating documentation and repetitive analysis across the lifecycle, while any change to your safety case, system state, or configuration requires explicit human approval.
The architecture is built for enterprise scrutiny. Every AI recommendation is generated through a structured intent-and-reasoning engine and permanently logged, recording the user's intent, the AI's suggested path, and the human approval that followed, so AI-assisted work is end-to-end auditable, exactly the way the rest of your safety evidence is. Deployment flexes to your security posture: standard secure enterprise endpoints, or full bring-your-own-model isolation where AI actions route entirely through your own cloud infrastructure inside your VPC boundary. Access runs through enterprise SSO with role-based control, customer data is fully siloed, and for organizations that want no AI at all, ASAP runs in a fully non-AI mode with every AI dependency disabled.
Fennec's specified ASAP tools are qualified by TÜV Rheinland as Tool Class 2 (T2) offline support tools under IEC 61508-3:2010, Clause 7.4.4. The reports define the applicable tools, versions, and scope. Project-specific tool use and safety evidence still require review.
The qualification provides independent evidence about the named tools and versions. It does not qualify the entire platform, predetermine an assessor's conclusions, or replace project-specific review.What T2 qualification means for users.
We see this constantly, and it's worth saying plainly: the problem is almost never the engineering. Experienced functional safety teams do rigorous work in spreadsheets every day. The problem is that the rigor isn't legible. Leadership can't see it, auditors can't efficiently trust it, and the traceability that lives in your senior engineer's head walks out the door when they do. A spreadsheet safety program is only as defensible as the person defending it.
ASAP doesn't replace your safety expertise; it makes that expertise visible, durable, and provable. Hazard analyses, requirements, and verification evidence live in one connected, traceable safety case. When leadership asks whether the organization can demonstrate compliance, the answer is a live, auditable record rather than a walkthrough of disconnected workbooks. Engineers can spend more time on safety analysis and less on cross-referencing, version reconciliation, and report assembly.
The same evidence stands ready beyond the internal case: third-party certification, customer audits, and insurers, whenever your program calls for them. Compliance by design, not compliance by scramble. Book a Discovery Call
)
Autonomous systems change with every release. Safety evidence has to keep up. See what a connected safety lifecycle looks like for your program.
30 minutes. No prep required.
We use optional analytics to measure site use and performance. They run only if you accept. Privacy Policy
FENNEC
)
)