Everything the V-model needs
One data model from the first stakeholder need to the last passing test, with the project work that gets you there.
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.
Specification levels
Model StRS, SysRS, SwRS or whatever your process names, in V-model order. Every requirement belongs to exactly one level.
Chapters per level
Each level carries its own table of contents. Drag requirements between chapters; the outline shows live counts from the database.
Stable keys
REQ-187 is assigned by the database, never reused and never editable, so references in reviews, commits and tests stay true.
Markdown bodies
Rich requirement text with a CodeMirror editor, inline links to other requirements and cached rendering that keeps lists smooth.
List, grid and board
Switch between a document list, a spreadsheet grid with bulk edit and CSV export, and a Kanban board over the same filtered set.
Keyboard first
Move with j and k, jump with g and G, select with x, open with Enter. A command palette reaches everything else.
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.
Nine link types
satisfies, refines, derives, realizes, verifies, triggers, depends-on, conflicts-with and relates-to, with inverse labels derived for display.
Traceability graph
An interactive, auto-laid-out graph of the whole project. Focus on one requirement and see everything upstream and down.
Impact analysis
Name the requirements a change touches and get everything linked to them, the tests that cover them ranked by risk, and the gaps with no coverage.
Cross-entity links
Link requirements to signals, test cases and work items, not only to each other. One trace spans the whole lifecycle.
Similar requirements
Vector embeddings find near-duplicates and related requirements by meaning, not just by matching words.
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.
Signal catalogue
A paged, filterable list and grid of interface signals with custom fields, in the same project as the requirements.
Linked in both directions
See the signals a requirement or test case touches from its own panel, and the requirements behind every signal.
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.
Structured test cases
Steps with expected results, shared steps reused across cases, and automation references that tie a case to the code that runs it.
Plans, cycles and runs
Plan what to run, execute step by step, attach evidence, and log a defect straight from a failed step.
Live execution
Trigger a run from CI through the public API and stream its step results as they arrive.
Coverage matrix
Requirements against the test cases that verify them, with uncovered requirements visible at a glance.
Project work beside the specification
Epics, features, stories, tasks and defects with your own workflows, linked to the requirements they implement.
Configurable workflows
Per-project work-item types, states and allowed transitions. A move the workflow forbids is refused, not silently allowed.
Board, grid, calendar, Gantt
Seven views over one shared, live set of work items, from a Kanban board to a Gantt timeline.
Iterations and effort
Plan iterations, log hours against items, and keep remaining effort honest without a separate time tracker.
History and comments
Every change to a work item or requirement is recorded, with comments for the conversation around it.
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.
Live updates
A change made by a teammate lands in your list in place, without a refresh and without losing your scroll position.
Organisations and teams
Group projects under an organisation, invite members by email, and grant access to whole teams at once.
Roles that mean it
Admins, members and viewers. Viewers read everything they are given and change nothing.
Custom fields everywhere
Typed custom fields on requirements, test cases, work items and signals, with filtering, grid columns and bulk edit.
Saved filters
AND/OR rule groups evaluated in the database, saved to your account and there on every device.
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.
Read the API referenceREST API
Requirements, links, test cases, executions, coverage, work items and more, with cursor pagination and an OpenAPI specification.
Webhooks
Signed HMAC deliveries when a test run completes, a requirement changes, coverage drops or a defect is raised.
MCP server
Give Claude or any MCP client tools to read, create, link and verify requirements, by key rather than by UUID.
Deep links
requiremancer:// links open a requirement in the desktop app straight from a review, a ticket or a commit message.
Built for teams who get audited
Tenant isolation enforced twice, an append-only audit log, and the option to run the whole stack yourself.
Isolation in the database
Row-level security policies bind every project-scoped table, behind the permission layer rather than instead of it.
Append-only audit log
Sign-ins, credential changes, access changes, deletions and exports are recorded in a log the database refuses to alter.
Single sign-on
Sign in with Google, Microsoft or GitHub, or with an email address and password.
On-premise
The same backend runs from a Docker Compose bundle on your own infrastructure, for specifications that must not leave the building.
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.