Doorstop

Doorstop is a requirements-management tool for teams that keep textual requirements with source code in version control. It suits Python- and Git-capable teams that want traceability and document publishing without a license cost. Its file-based approach is compelling for code-centred work, but it is not a fit for teams that need formal approval workflows.

Overview

Requirements and other linkable items are stored as YAML files within documents, which form a hierarchy Doorstop can validate for traceability. Keeping those files in a version-control system gives teams a way to track changes alongside their code and use their existing process for managing revisions. That is a practical advantage for engineering groups already working this way; it also makes Python and version control operational prerequisites rather than optional extras.

Doorstop publishes document hierarchies and trace matrices as plain text, HTML, LaTeX, or Markdown. Templates allow teams to tailor output styling, and the tool can import and export YAML, CSV, TSV, and Excel files. These capabilities cover both publishing and file exchange, though they do not add a review or sign-off process.

Key features

Traceability and baselines

The document tree lets teams validate links across requirements and related items. Baseline support and version history help maintain a record of changes, making Doorstop more than a folder of requirement files. Teams still need another process or tool for approvals: Doorstop does not provide approval workflows.

Publishing and interchange

Plain-text and Markdown publishing require no additional tools; HTML publishing uses templates. LaTeX and PDF publishing require a LaTeX distribution, so those formats bring an extra setup burden. YAML, CSV, TSV, and XLSX import and export support can help teams move requirements between Doorstop and other file-based processes.

Deployment and desktop editing

Doorstop can run as a standalone web server or as a WSGI application under Apache or another web server. The project also describes an experimental desktop GUI for basic editing, but that status makes it a less dependable basis for a team's primary editing workflow. macOS may require python-tk for the GUI.

Pricing

Doorstop is free and open source under the LGPLv3 license. Its Doorstop plan costs nothing and requires Python and a version control system. There is no paid tier to unlock the core traceability or publishing features, but the cost advantage comes with responsibility for the required environment and for any approval process Doorstop does not supply.

Platforms

Doorstop supports Linux, macOS, and Windows, as well as API and self-hosted use. The repository requires Python 3.10 or later and a version control system. HTML and Markdown publishing need no additional tools, while LaTeX/PDF output requires a LaTeX distribution.

Who it's for

Doorstop is best for engineering teams that want requirements, test cases, or certification-related items maintained alongside source code, and that are comfortable with Python, Git, or another version-control system. Its hierarchical traceability, baselines, version history, and multiple publishing formats are useful where those practices matter more than a dedicated approval interface. Organisations that require formal review gates and sign-off should look elsewhere.

Pros and cons

• Pros: Requirements stored as YAML in version control can be maintained alongside source code, keeping changes within a code-centred workflow.
• Pros: Hierarchical traceability, baselines, and version history support structured change management without a license fee.
• Pros: Publishing in four formats and import/export across YAML, CSV, TSV, and Excel give teams useful options for output and interchange.
• Cons: Python 3.10 or later and a version control system are required, which limits suitability for teams seeking a self-contained, nontechnical workflow.
• Cons: No approval workflows means teams needing formal review and sign-off must provide that process elsewhere.
• Cons: The desktop GUI is experimental, and LaTeX/PDF publishing depends on a separate LaTeX distribution.

Alternatives

For other options, browse Requirements Management Software.

• MATLAB Grader is a free alternative for teams already holding a current MATLAB license; LMS integration requires a qualifying academic license.
• ReqView is worth considering if a GUI-based product across desktop and web platforms better suits the team; its free plan is limited to one document, 150 objects per document, and one custom attribute, while PRO costs €440 a year per user.
• OSRMT is another free, self-hosted option, but it requires hardware to run.
• Innoslate may suit educators or students who can use its free Academia plan with a .edu account.
• ICEM Surf is an alternative for personal learning on Windows, though its Learning Edition is not for industrial, commercial, or business use and includes no support.
• RequirementONE has a free Try plan for one user, limited to three sources from a shortlist, a predefined topic filter, and a personalised newsletter.
• NETVIBES is another option, with an Enterprise Data Science plan that lists 17 portfolio roles.
• StrictDoc is a free alternative available across Linux, macOS, web, Windows, API, and self-hosted use.

Verdict

Choose Doorstop if your team already uses Python and version control and wants free, code-adjacent requirements with traceability, baselines, and flexible publishing. Its strongest reason to choose it is that requirements can live and change alongside source code; its clearest reason to look elsewhere is the absence of approval workflows.