NexusRM brings the DOORS and JAMA way of working (modules, attributes, typed links, baselines) to a modern web app your whole programme can edit at once. No desktop client, no module locks, and nothing leaves your network.
Write the specification, trace it down to software and verification, freeze it at each design review, and see exactly what a change will touch before you make it.
Read a module as a numbered specification with tables and diagrams, or switch to the grid and edit status, priority and custom attributes in place. Several engineers can work in the same module at the same time; conflicting saves are caught, never silently overwritten.
Typed links such as Decomposes, Verifies and Impacts connect system requirements to software requirements and test cases. The object graph shows parents to the left and children to the right; the coverage matrix highlights every row and column with nothing linked.
Capture an immutable baseline at PDR, CDR or any milestone. Compare any two baselines, or a baseline against today, and see what was added, deleted and modified, down to the individual field and attribute.
Walk the link graph from any object, layer by layer, to a depth you choose. Each affected item shows the path that reached it, so a reviewer can see why an interface change lands on a particular test case. Cycles are detected, not followed forever.
Role-tailored dashboards track volatility, churn by module, maturity against your design-review milestones and stale change branches. Every chart has a table behind it, and every table exports to CSV.
Every change is written to an append-only audit log in which each entry carries the SHA-256 hash of the one before it; one click verifies the whole chain. NexusRM runs as a single Docker Compose stack with no runtime network egress, so it fits networks that are air-gapped by policy.
Projects, modules and objects with per-module numbering, custom attributes and typed links. Teams coming from either tool recognise it on day one.
Export a whole project to a documented CSV or XML format; re-importing the export reproduces the project.
Import and export →User-bound tokens drive the REST API and an MCP server, so scripts and self-hosted AI agents work under the same roles and audit trail as people.
API and MCP →Shared column sets per project, such as a safety review or a software build view, picked from the grid toolbar.
Define terms once; wherever they appear in a requirement body, the definition is a hover away. Stored text is never altered.
Pair it with Lucent: reviews register back into NexusRM, requirements in scope get a Reviewed Status, and each object lists its reviews.
A narrated walkthrough of a flight management system project: authoring, traceability, coverage gaps, baseline comparison, impact analysis and the audit trail.
Own a perpetual licence or subscribe for continuous updates. Every tier includes the full source code.
A perpetual licence for the current version.
Redistribution not permitted.
Purchase licenceA perpetual licence with feature updates and support for a year.
Always-current source code, plus support for custom features and integrations.
No. NexusRM is a single Docker Compose stack (the application and PostgreSQL 16) that runs on your own servers with no runtime network egress. For an air-gapped network, the images are built on a connected machine and carried across with docker save and docker load.
NexusRM includes importers for DOORS XML and JAMA CSV/XML exports. An import is validated first, with a report of any issues, and only committed once you confirm it; re-importing a file matches items by their source ID. Every legacy database is different, so send us a sample export and we'll talk through your migration before you plan a cut-over.
LDAP and Active Directory are built in, with directory groups mapped to global or project roles. Local accounts are also available, with passwords hashed using Argon2id. If you need a different identity provider, talk to us.
On your hardware, in your PostgreSQL volume. Nothing is sent to us or anyone else. You can export a whole project to a documented CSV or XML format at any time, so your requirements are never locked in.
Every change is appended to an audit log in which each entry includes the SHA-256 hash of the previous one. Verifying the chain detects any entry that was altered or removed, and the log can be filtered by project, user, action and date and exported to CSV as evidence.
Yes. You keep the source code as of the last day of your subscription, to use in perpetuity.