Skip to main content

Every requirement, linked to the code and tests that fulfil it.

For teams building safety-critical software, such as automotive suppliers, defence and aerospace.

See the whole loop in one minuteA requirement is written, linked to code and a test, and checked.

Write, link, check.

  1. Step 1 of 3

    Write the requirement

    A requirement is a plain text file, kept in the same repository as your code.

    WriteA requirement written as text, next to the code.
  2. Step 2 of 3

    Link it to code and a test

    A short reference connects it to the code that implements it and the test that verifies it.

    LinkThe requirement linked to its code and its test.
  3. Step 3 of 3

    Run the check

    DevKit compares the links with the model your team has set and points out any that are missing or broken.

    CheckA broken link is flagged, fixed, and the check passes.

Use it where you already work.

All three do the same job. The command-line tool works on its own, with any editor.

Where you workOne requirement, seen from the command line, the editor and an AI assistant.
  • Command line

    Run the check in any terminal. It needs no particular editor.

  • Editor extension

    See and follow links while you write code.

  • AI coding assistants

    Your assistant reads and adds links the same way you do.

What changes for your team.

Traceability today compared with DevKit
TodayWith DevKit
Traceability is rebuilt by hand before an audit.Links are added in the same change as the code.
Gaps show up late, when they are costly to fix.The check points out a missing link right away.
The picture is out of date after the next change.The trace stays current, as evidence for your compliance work.

Who it's for, and how to start.

For anyone who works with requirements, code and tests, and wants to see how they connect. Start free in your own repository.

Starter

Free limited access to APEQS DevKit

Try for free, Starter

Includes:

  • CLI, VS Code extension and basic MCP server
  • Up to 500 elements and 10 element types
  • 2 connected repositories and 5 reports per month

Professional

Recommended for teams

For professional engineers working in more complex development environments

Book a demo, Professional

Includes:

  • CLI, VS Code extension and MCP server
  • More than 500 elements and 10 element types
  • More than 2 connected repositories per multirepo project
  • More than 5 reports per month

Try APEQS on your own repo, or plan a pilot with us.