AI for verification & validation of critical software.

KomAInu checks that every requirement is clear and tested. It reads your specs, challenges each requirement until it is testable (ambiguities, conflicts, missing edge cases, unstated assumptions), writes the test cases it needs, and compares them with the tests you already have to flag the missing, weak or false-positive ones. The result is a requirements-to-tests traceability matrix where every gap is shown as present or missing, never guessed. Engineers approve every proposed rewording and every test. KomAInu Individual does this for one engineer, free; KomAInu Enterprise does it for a whole team and project, connected to your ALM and test tools.

KomAInu is a French company founded in Paris in July 2026. Its registered office is at 173 rue de Courcelles, 75017 Paris, and the team works from STATION F. It was founded by three engineers: Pierre Lammers, Benjamin Chollet and Sven Juge.

Two ways. Try KomAInu Individual for free, today, on your own specs: no demo, no setup. When your team needs coverage and traceability across a whole project, talk to us about KomAInu Enterprise. For Enterprise, we start with a real verification bottleneck and determine together whether KomAInu fits the workflow, toolchain, deployment constraints, and review process. Pricing is scoped for each engagement rather than published as a fixed package.

KomAInu Individual is free, for one engineer, in its own web interface. You drop in your specs, KomAInu extracts every requirement, challenges each one, and writes the same test cases every time, ready to export as CSV. KomAInu Enterprise includes everything in Individual, for the whole team and the whole project. It connects to your ALM and test tools, flags every missing, weak or false-positive test, keeps a requirements-to-tests traceability matrix ready for the auditor, and runs in our EU cloud or on your premises, air-gapped if needed, with dedicated support.

You speak directly with the founders for 30 minutes about one concrete V&V bottleneck, the tools and artifacts involved, and any data or deployment constraints. The goal is to decide whether KomAInu is relevant to your environment. No preparation is required, and if there is a fit, the next step and commercial scope are defined with you.

KomAInu runs in two ways. In our cloud, your requirements, tests and documents are processed in the EU, with models hosted on Google Cloud in Belgium. Otherwise, our teams deploy KomAInu on your premises, with the models you already run or a local model, air-gapped if needed, so nothing leaves your network. We check which one fits your project in the first conversation.

KomAInu can work with private or open source models deployed in your own environment, including model families such as Mistral, Qwen, and similar models that you can host yourself. The choice depends on the accuracy, latency, cost, and security profile your project requires. The important point is that the model is not the product boundary. KomAInu provides the traceability workflow, retrieval context, scoring, evidence structure, and review process around the model, so the solution can be tuned to your needs instead of forcing every team into the same hosted AI setup.

Yes. KomAInu is designed to adapt to your project rather than replace your whole V&V process. We configure the solution around your standards, your requirements format, your test repositories, your ALM, and the way your team reviews and approves evidence. For example, one team may need traceability from requirements to tests for a certification audit, another may need coverage analysis, and another may need requirement reviews before a baseline. The underlying platform stays the same, but the workflow, connectors, review gates, and outputs are adapted to the certification or compliance problem you actually need to solve.

KomAInu is built to sit on top of existing engineering and ALM workflows. It can read requirements, tests, code, documentation, and traceability artifacts, then suggest corrections, generate missing test material, and keep the traceability view current after human review. The goal is not to make teams rebuild their process from scratch. KomAInu connects the audit, remediation, and prevention loop around the tools already used by the project, so approved changes can flow back into the ALM or repository while the existing system of record remains in place.

KomAInu works human-in-the-loop: every reworded requirement and every test it proposes is reviewed and approved by an engineer before it enters your project record. It supports your verification process; it does not replace it or sign off on its own. KomAInu is not a qualified tool under DO-330, and it does not need to be: like a colleague's work, everything it proposes is reviewed and approved by your engineers.

No. KomAInu is built as an engineering assistant for regulated software, not as an automatic certification authority. It detects gaps, proposes tests, suggests corrections, and updates traceability, but engineers remain in control of what is accepted. That human review gate is important because safety-critical verification still depends on engineering judgement. KomAInu reduces the manual search and documentation effort, surfaces the risky inconsistencies earlier, and prepares evidence, while your team validates the output before it becomes part of the official project record.