AXISDesign ToolsRequest a demo

For DO-178C and DO-254 programs

Requirements in plain files, reviews tied to exact revisions

reqx keeps every requirement as a readable file in Git repositories you own, and gives engineers, systems leads, and quality staff a browser application to create, trace, and baseline them. The optional revx add-on runs planned, independent peer reviews from the same version history.

Request a demoSee how reqx works
reqx project page showing the trace structure of an electric brake control unit: system requirements and a shared platform document at the top, an interface control document below, software and FPGA requirement branches, and verification documents and source repositories at the bottom.
Project trace structure in reqx, from system requirements down to verification, code, and VHDL.

Why reqx

Built for engineering data that has to stand up to an audit

Requirements tools often trade away the things certification work depends on: data you can read without the tool, real configuration management, and traceability that notices when it goes stale.

Requirements locked in a proprietary database that is hard to audit, migrate, or archive
Each requirement is a Markdown file with YAML front matter in a Git repository you own, readable without reqx and archivable for the life of the program.
Configuration management added after the fact
Git is the database. Every change is a commit with author, time, and change reference. Baselines are tags, and the history is complete.
Traceability that drifts out of date
Each link records a fingerprint of the upstream requirement. When its normative content changes, downstream links are flagged suspect until someone reviews and accepts them.
Tools only specialists can use
A browser application with document views, an item editor, drag-and-drop outlining, and commits from the browser, with no Git or command-line knowledge needed.
Reviews tracked in spreadsheets and email
revx ties every review to the exact versions reviewed, checks reviewer independence where the plan requires it, and produces an evidence package for audits.

Products

One hub for requirements and the reviews that cover them

revx runs in the same reqx server and appears as a review mode in the same browser application, enabled per licensed deployment.

reqx

Requirements management in your own Git repositories.

  • Browser editing with locking, field-level merge, and validated commits
  • Upstream and downstream traces with suspect-link detection
  • Configurable traceability matrices and reports
  • Document labels and project baselines
  • Import from ReqIF, CSV, and Word; export to HTML, PDF, and Word
Explore reqx
A reqx requirement page with a suspect-link warning: the software requirement still says 4 seconds, while the upstream system requirement it traces to now says 6 seconds.

revx optional add-on

Planned, independent peer reviews driven by version history.

  • Versioned review plans, roles, and checklist forms
  • Needs Review queues computed from what changed
  • Independence checks where the plan requires them
  • Findings, replies, fixing commits, re-review, and closure
  • Evidence packages identifying every reviewed version
Explore revx
A revx HDL code review showing a VHDL file with a Not Accepted comment from the independent hardware reviewer, waiting for re-review.

Program support

Supporting DO-178C and DO-254 programs

reqx and revx support the life-cycle activities programs carry out.

Program needreqxrevx
Bidirectional traceability between requirement levels, design, code, and verificationTrace graph, source repository scanning, checked matrices
Derived requirements identified and justifiedDerived flag and rationale, derived requirements report
Change impact analysisSuspect links, impact shown before commitReviews reopened by upstream changes
Configuration identification and baselinesLabels, project baselines, full Git historyRecords of exactly which versions were reviewed
Problem reporting and change controlChange references checked against your issue trackerCommits tied to review findings
Reviews of requirements, design, and verification dataPlans, forms, independence, findings, closure
Records for certification liaison and auditsReports with provenance, document exportsReview evidence packages

reqx is designed to support tool qualification under DO-330 where a program requires it: deterministic output, a published file format, and an automated verification test suite. Qualification itself is performed for each program.

Deployment

Runs on your infrastructure, with your data

Self-hosted

Run the Docker image with Compose, or on Node.js directly. Requirements stay in your Git repositories, on your network.

Any Git host

Works with GitHub, GitLab, or a self-hosted Git server. Set up connections, documents, and projects from the browser.

Offline licensing

The license is a signed file the server verifies itself. reqx does not contact the vendor or report usage, so it can run on isolated networks.

See reqx and revx with a realistic program

We can walk through the synthetic brake controller example, from system requirements to VHDL and code reviews, and discuss how it fits your process. Pricing is available on request.

Request a demoLearn about revx