Requirements · Tests · Delivery

Engineer the whole V‑model in one place

Requiremancer brings requirements, test management and project work into a single traceable tool. A faster, more flexible alternative to DOORS, RQM and Jira stitched together.

Get started free Download for desktop

Free for small teams · More room for students on an academic address

Built on the V-model

Both sides of the V, and the trace between them

Most teams keep requirements in one tool, tests in another and work in a third, then reconcile them by spreadsheet before every audit. Requiremancer models the whole lifecycle in one schema, so the trace is never a reconstruction.

  • Specification levels with their own outlines
  • Typed links that read as sentences: SwRS refines SysRS
  • Coverage computed from real test cases and runs
  • Work items linked to the requirements they implement
  1. StRSStakeholder needsWhy the system exists
    verifies
    AcceptanceAcceptance testsDid we build the right thing?
  2. SysRSSystem requirementsWhat the system shall do
    verifies
    SystemSystem testsDoes the whole system comply?
  3. SwRSSoftware requirementsWhat each component shall do
    verifies
    IntegrationIntegration & unit testsDoes each part behave?
  4. Work itemsImplementationStories, tasks and defects linked to what they implement
20,000+requirements in one project, scrolled without a stall
~9 msper page of 200, whether it is page 1 or page 50
Liveedits from teammates land in place as they happen
Everything in one project

From stakeholder need to passing test

Eight areas, one data model. Each links to the others, so nothing you write is an island.

Decomposition

Requirements that stay fast at twenty thousand

Write and organise requirements across specification levels, each with its own outline, the way a DOORS module works — without the wait.

Traceability

A trace you can read as a sentence

Typed, directed links with IEEE and INCOSE semantics. Every stored edge reads true from source to target, so the graph means what it says.

Interfaces

Signals alongside the specification

Define the signals that cross your system boundaries next to the requirements that constrain them, and trace one to the other.

Verification

The right-hand side of the V, built in

Test levels, suites, cases, plans, cycles and executions in the same tool as the requirements they verify, so coverage is a query, not a spreadsheet.

Delivery

Project work beside the specification

Epics, features, stories, tasks and defects with your own workflows, linked to the requirements they implement.

Collaboration

Real time, for the whole team

Edits appear for everyone in the project as they happen. Organisations, projects, teams and roles decide who sees and changes what.

Automation

An API for CI, scripts and AI assistants

A public REST API with project-scoped API keys, signed webhooks, and an MCP server that lets an AI assistant work in your project.

Trust

Built for teams who get audited

Tenant isolation enforced twice, an append-only audit log, and the option to run the whole stack yourself.

Two ways in

At your desk, or in any browser

The desktop app is the full engineering workstation. A lighter browser edition is on its way for reviewing and editing from anywhere.

Desktop

Early access

The complete tool for the people who write and verify the specification every day.

  • Every view: list, grid, graph, board, Gantt, coverage
  • Opens requiremancer:// links from reviews and commits
  • Sign-in kept in your operating system's keychain
  • Built for Windows, macOS and Linux
Download

Browser

In development

A lighter edition for stakeholders, reviewers and quick edits, with nothing to install.

  • The same projects and live updates as the desktop app
  • Read, review and comment from any machine
  • Share a link to a requirement with anyone on the project
Create an account to be first in
Automation

Your CI and your AI assistant are on the project too

Push test results from a pipeline, react to changes with signed webhooks, or let an AI assistant draft, link and verify requirements through the built-in MCP server.

See the API and MCP tools API reference
curlRead a requirement by its key
curl https://api.requiremancer.com/api/v1/requirements/REQ-214 \
  -G -d project_id=$PROJECT_ID \
  -H "X-API-Key: $REQUIREMANCER_API_KEY"

{
  "data": {
    "sequential_id": 214,
    "title": "Detect the loss of a wheel-speed sensor within 20 ms",
    "status": "approved",
    "priority": "critical",
    "custom_fields": { "asil_level": "D" }
  }
}

Put your next specification on one V-model

Start free with a small team. Dedicated and on-premise deployments are there when you need them.

Get started freeDownload the desktop app