Doorstop

Doorstop is an open-source requirements management tool for teams that keep requirements with source code in version control. It is a strong fit for Python and Git users who need traceability and portable publishing; teams that rely on formal approvals should look elsewhere.

Overview

Doorstop stores requirements and other linkable items as YAML files organized into documents. Documents form a hierarchy that Doorstop can validate for traceability, while version control keeps changes in the same system used for code. That file-based approach fits teams that want requirements managed alongside development work. It asks users to bring their own version control setup and comfort with Python, so it is less suitable for teams seeking a self-contained requirements system.

Doorstop can publish document hierarchies and trace matrices as plain text, HTML, LaTeX, or Markdown. Templates let teams tailor output styling; HTML and LaTeX publishing use templates. YAML, CSV, TSV, and Excel import and export provide practical routes for exchanging requirements with other tools and processes.

Key features

Traceability and change control

Hierarchical documents let teams validate traceability across requirements and related items. Baseline support and version history help manage changes over time. These are useful foundations for maintaining requirements, but Doorstop has no approval workflows. Teams whose process depends on formal review and sign-off will need another tool or process to provide that control.

Publishing and interchange

Publishing both document hierarchies and trace matrices in four formats makes Doorstop useful for teams that need readable outputs beyond the YAML source files. HTML and Markdown publishing need no additional tools; LaTeX and PDF publishing require a LaTeX distribution. The range of import and export formats also helps with exchange, though the underlying requirements remain organized as files in documents.

Integration and access

Doorstop requires Python 3.10 or later and Git or another version control system, and it can be added to a Poetry project. It 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; macOS may require python-tk. That GUI is a limited option for users who prefer desktop editing, not a reason to choose Doorstop as a polished desktop application.

Pricing

Doorstop is free and open source under the LGPLv3 license. Its Doorstop plan costs nothing and includes requirements traceability, baseline support, version history, and import and export in YAML, CSV, TSV, and XLSX. There is no paid tier or trial to weigh against a seat limit: the practical costs are the required Python and version control setup, plus a LaTeX distribution if publishing to LaTeX or PDF.

Platforms

Doorstop supports API use, Linux, macOS, Windows, and self-hosted deployment. Its Python and version control prerequisites make platform support most relevant to teams able to manage that environment. The optional desktop GUI is experimental, and macOS users may need python-tk for it.

Who it's for

Doorstop suits engineering teams that want requirements tracked alongside source code, with traceability checks, version history, baselines, and output they can publish or exchange in common formats. It is particularly practical when Python and version control are already part of the team's workflow. Teams needing built-in approval and sign-off workflows, or a mature desktop editing experience, should consider alternatives.

Pros and cons

• Requirements live with code: YAML files and version control keep requirements in the same change-management environment as source code.
• Useful traceability controls: Hierarchical validation, baseline support, and version history cover important maintenance needs.
• Flexible output and exchange: Four publishing formats and YAML, CSV, TSV, and Excel interchange serve teams with varied documentation and handoff needs.
• No built-in approval workflows: Teams requiring formal review and sign-off will need another system or process.
• Setup depends on Python and version control: It is a poor fit for teams that want a standalone managed service without those prerequisites.
• Desktop editing is experimental: The basic GUI is not a dependable centerpiece for teams that need a mature desktop client.

Alternatives

Browse Requirements Management Software for more options. MATLAB Grader is a free alternative for Linux, macOS, web, and Windows users, but its free use depends on a MATLAB license current under maintenance, and LMS integration requires a qualifying academic license. Choose ReqView if a web option and a free plan capped at one document, 150 objects per document, and one custom attribute fit better; its PRO plan is €440 a year, billed per user.

OSRMT is another free, self-hosted option across Linux, macOS, web, and Windows, with hardware required to run it. ICEM Surf offers a free learning edition for personal learning only, with no industrial, commercial, or business use and no support; commercial licenses use custom pricing. Innoslate has a free Academia plan for educators and students who sign up with a .edu account, alongside a custom-priced Enterprise plan. RequirementONE has a free Try plan with one user, three sources from a shortlist, a predefined topic filter, and a personalized newsletter. StrictDoc is another free option across API, desktop, web, and self-hosted platforms. NETVIBES is a paid option with a free plan and a listed Enterprise Data Science plan at custom pricing.

Verdict

Choose Doorstop if your team wants free, version-controlled requirements with traceability, baselines, and flexible publishing, and already has the Python and version control foundation to support it. Its key advantage is keeping requirements close to code while retaining useful interchange and output options. Look elsewhere if approval workflows are central to your process or you need a mature desktop client.