About KomAInu
Guarding the critical software of tomorrow.
A missing test should never be found by an auditor. It should be caught before the code ships.
We’re at STATION F, in Batch 6 of the Cegid Startup Program.
3
founders, all engineers
DO-178C
critical-software background, plus ISO 27001 and HDS in health data
1+ year
maturing the idea before founding KomAInu
July 2026
KomAInu founded in Paris
Supported by
Startup Program, Batch 6
Startup campus
Google for Startups Cloud Program
Our name
Komainu are the guardians at the gate.
In Japan, komainu are the pair of lion-dogs that stand at the entrance of Shinto shrines. One has its mouth open, the other closed. Together they watch over everything that comes in and keep evil spirits out.
That’s the job we gave ourselves. KomAInu stands guard over your software: it watches every requirement, every test and every change, and keeps out the bugs and human errors that slip in when a case is forgotten. The “AI” in the middle of the name is the help it brings.
Our story
Born from a frustration at Thales.
We are three engineers. We have lived the long verification cycles, the traceability matrix filled in by hand, and the bug that comes back because nobody thought of that one case. So we decided to build the tool that would have helped us.
At Thales
The frustration
Pierre and Benjamin build critical software at Thales. Verification cycles are long, reviews are manual, and the same bugs keep coming back because a case nobody thought of was never tested.
2025
An idea that takes its time
Sven, then an AI engineer at Arkhn, joins the conversation. For more than a year the three of us sketch the tool we wish we had: one that reads the requirements and points at the cases we forgot.
July 2026
KomAInu is founded
We stop sketching and start building. Three engineers, one goal: catch the gaps between requirements, tests and code before they turn into bugs.
Cegid Startup Program · Batch 6
Our first day at STATION F.
The three of us moved into STATION F with Batch 6 of the Cegid Startup Program. We filmed a few moments during our first tour with the other startups.
- 12
- AI startups in the batch
- 9 months
- of support from the program
- Cegid
- mentors, clients and partners to learn from
Our team
The three of us.
Why KomAInu
Why KomAInu, when any AI can write a test?
True. Ask a general-purpose assistant for a unit test and you’ll get one in seconds. The hard part comes after: proving which requirement it covers, finding the ones nothing covers, and keeping that link alive as the code changes.
That’s the gap we close. KomAInu doesn’t just generate tests. It connects requirements, tests, code and verification evidence, so V&V teams find coverage and traceability gaps before they surface in an audit.
Requirements first
Generic assistants start from the code. KomAInu starts from the requirement and asks what proves it is met.
Evidence with every gap
Each finding links the requirement, the tests and the code behind it, so a reviewer can check it in minutes.
Written for reviewers
Reports are meant to be read in an audit or a certification review, not only by the developer who ran them.
Your hardest challenge? We audit it live.
30 minutes with the founders. Bring your toughest V&V challenge, leave with clear next steps.
Lumen Rail › Door control
Dashboard
78%
covered
Covered115
Partial21
Uncovered12
Tests linked
212
Tests missing
33
Requirements 148
- DCU-SYS-014The door control unit shall prevent door opening while train speed is above 3 km/h.4 tests
- DCU-SYS-022The doors shall reopen when an obstacle is detected during closing.1 tests