Features
ALM OS adds what no single tool can do: one identity for every item across tools, one trace registry, cross-tool baselines and the evidence built on them. Each part below is in the product today; the page describes ALM OS 0.12.0, now in pre-release (beta).
Traceability and coverage
Link any two items across tools with a named relationship — implements, verifies, satisfies, refines, mitigates and more. The trace matrix shows coverage with ready-made views (requirements to tests, to code, to design documents) and your own.
- Coverage in numbers: “3 of 5 requirements have tests (60 %)”, with the gaps highlighted
- “Only gaps” filter and CSV export, one line per link, for the assessor
- V-model view and a Missing evidence list: work done without its required output
- Links are written back into the tools that can show them, e.g. a note on the merge request
- Traceability between modules: a matrix of modules, links made by drag and drop, and chains followed level by level
- Code traced from git: commit trailers (Implements:, Verifies:) and annotations in the code link it to requirements, pinned to the commit read
- Variants and product lines: an item valid for some variants only, with the trace, coverage and baselines per variant
Impact analysis and Needs review
Before you change a requirement, see what it affects: every item reachable over links, scored by relationship and distance. After a change, every link to the changed item turns to Needs review until its owner confirms it.
- “What changed”: the words added and removed, the version before and after, who and when
- “Still valid…” asks for a reason and records the person; “Can't check” never counts as OK
- One inbox for links to review, sign-off requests and tools that are not answering
- Live updates in the browser; e-mail notifications by rules per project
- A tool’s own suspect links listed in Needs review too, with what changed
Releases, baselines and sign-off
Freeze a baseline in three steps: name it, check what it includes, and let ALM OS confirm that every tool answers. Snapshots from every tool are stored together in git as one immutable, tagged baseline.
- Compare two baselines: what was added, changed and removed, in every tool
- Sign-off in four steps — frozen, reviewed, verified, approved — with Ed25519 signatures
- Independence rules: whoever froze it cannot sign it; one person, one role
- Who may sign each role is set per group or person by the administrator
- Module baselines tied to a product version, and a baseline difference report as DOCX, PDF or XLSX
- Phase gates: the gate’s checks, its board’s decision and an e-signed pass move the project to the next phase
Evidence and audit trail
Everything ALM OS records is a git commit with the person's name: links, reviews, edits, baselines, signatures, settings. Evidence is never rewritten; failures are recorded in the baseline, not hidden.
- Evidence report per baseline: tools, items with content hashes, links and their state, coverage, checksums
- Audit trail of every operation with who and when
- History of each item: its links, reviews and edits
- Dashboards and KPIs: work without evidence, items without verification, open problems
- Every view, search, plan, roadmap and dashboard exported to Excel or CSV; the whole project at once, current or as a baseline froze it
- Each plugin’s exact build, named by its commit, recorded in every baseline
AI agents, reviewed by people
Connect the AI agent you already use — Claude Code, Claude Desktop, Copilot in VS Code, Gemini CLI, ChatGPT or Cursor — over MCP (the Model Context Protocol). It reads your projects as you and proposes; it never writes. Nothing changes until a person accepts the proposal, and what is accepted is recorded as AI-assisted. ALM OS runs no AI model of its own.
- Connect an agent: a four-step guide that ends with one set-up script for Windows, macOS or Linux; Claude Desktop and ChatGPT connect through OAuth, without a token
- Proposals shown before anything is written — new items with their links, edits, links, requirement imports — and accepted in whole or in part
- Independent review of AI proposals when the project asks for it; an agent never applies a proposal, signs, freezes a baseline or clears a link that needs review
- Requirement quality findings (vague words, several obligations, missing acceptance criteria) and test cases drafted from a requirement, as proposals
- Tokens limited to reading or to reading and proposing, to chosen projects and a lifetime, rotated or revoked at any time; with the ALM-AI licence
Requirements management with ReqManTool
ReqManTool, a DOORS-style requirements tool, is included free for up to 5 modules; ReqManTool Pro removes the limit. Modules, hierarchical requirements, custom attributes, directional links and ReqIF/CSV export, with requirements stored as plain files in git. A module or a requirement is opened for editing and saved as one commit, so nobody reads half-made changes.
- Opens inside ALM OS as an app, with the same menus and search
- Edit requirements from ALM OS; every edit is audited
- Requirements kept in DOORS, DOORS Next, Polarion or Codebeamer come in through ReqIF
- Comments and discussions, earlier versions restored from the history, and a glossary of references, definitions and abbreviations
- Word, PDF, Excel and CSV specifications imported into modules, tables kept as tables; the next version of a document updates instead of duplicating
Document control with Office editing
The Documents plugin keeps controlled documents in ALM OS itself: every version identified by its SHA-256, the previous one archived, never deleted. Check a document out and edit it directly in Word, Excel, PowerPoint or LibreOffice.
- Folders, versions, check-out and check-in, who changed what and why
- Confluence pages and SharePoint documents as controlled copies in baselines
- A document register imported from CSV
- AsciiDoc documents kept in git, with a live preview, PlantUML diagrams and HTML or PDF export
- Documents folders synced with a folder on your computer through ALM OS Desktop: edit with any program, then Check in… with a comment
- A free wiki per project and product: Markdown or AsciiDoc pages in git, linked to items and kept in baselines
Tests and verification
Test results from CI and tests run by hand, in one place and in the trace matrix. The Test results plugin reads JUnit XML and Robot Framework files from any CI and keeps manual tests executed step by step.
- Manual test cases, plans, runs and campaigns, executed step by step
- Each automated test keeps one identity across runs, so its links stay valid
- Tests, traceability and test results exported as CSV, XLSX, PDF or DOCX, current or pinned to a baseline
Artifacts and builds
The Artifacts plugin keeps build outputs, packages, firmware and installers in repositories per project, each version by its SHA-256, so a signed baseline and its release name the exact file delivered.
- Uploads in parts that resume after a broken connection; every download checked against its SHA-256 first
- SBOMs (CycloneDX, SPDX) per product version, matched against a local vulnerability feed (OSV or NVD), with findings to triage
- Retention rules per repository; released and baselined files are never removed
- Jenkins builds and JFrog Artifactory binaries in the same baselines
Risk and safety
The Risk & Safety plugin keeps the safety records of a railway project next to the rest of the evidence, each register linked to requirements, mitigations and tests.
- Hazard log (EN 50126-1) with a configurable risk matrix, initial and residual risk
- Mitigations and safety requirements with their safety integrity (basic, SIL 1–4)
- FMEA / FMECA worksheets with computed RPN and criticality, and fault trees (FTA)
- SRAC register (EN 50129) and cybersecurity threats with SL-T and SL-A and their TARA (CLC/TS 50701, IEC 62443)
Work and lifecycle
Use the tracker you have, or the Work plugin: Project Management and Product Management with boards, backlog, sprints, releases and a roadmap, templates for the EN 50126 lifecycle phases, verification and validation with independence by SIL, and Automotive SPICE processes.
- Products, systems and their released versions (product and work breakdown)
- A Gantt over every tool’s work: dependencies, the critical path with float, each person’s load, and master projects above several projects
- Scrum, Kanban, Waterfall or V-model, custom fields, and many items selected and set together
- A change control board (ALM-CCB): change requests and board meetings with e-signed decisions
- Gerrit code review in the image, with review rules by SIL
Workflows, gates and scripts
Each project follows a process template — the CENELEC railway template, Automotive SPICE, and previews for industry, energy, medical devices, aerospace, banking and defence — whose workflows ALM OS enforces in every tool, with roles and independence checked as people are named. The workflow editor, new electronic signatures and scripts come with a paid licence.
- The workflow editor: change, compare, simulate and publish a project’s workflows
- Electronic signatures on workflow steps, with re-authentication at your sign-in service
- Functional roles that every tool reads, and a preview of the project as a role
- Scripts and triggers in Starlark: a pre-save trigger refuses a change with a reason; each version runs only once someone else approved it, with dry runs and a kill switch
ALM OS Desktop
The ALM OS Desktop app keeps a copy of your projects to read and edit requirements, Work items, links and comments offline, and sends your changes with Sync; the server checks them with your rights and workflows.
- Sign in through the browser: no token to copy, and each computer can be disconnected
- Documents folders on your computer: approved, released and in-review documents read-only, and nothing sent until you check it in
- An approved item edited offline becomes a change request where the project has change control
- No offline copy on a computer without full-disk encryption where ALM OS requires it (the default)
- Included in every named-user licence at no extra cost
Import and export
Bring an existing project in from CSV or JSON: the product breakdown, work breakdown, document register and any tool's items. Every import is checked first and matched by a key, so importing the same file again changes nothing.
- Dry run by default: create, update, unchanged or error, per row
- Export the same columns, edit them in a spreadsheet and import again
- Trace matrix and evidence in CSV and HTML for the assessor
Sign-in, roles and languages
People sign in with the accounts they have: Microsoft Entra ID, any OpenID Connect provider (Okta, Keycloak, Google…), LDAP or Active Directory, or GitLab, GitHub and Atlassian accounts. Sign-in never needs a licence.
- Projects with managers, members and viewers; assessors usually as viewers
- Each person's own accounts in the tools, so changes are made in their name
- HTTPS everywhere, with mutual TLS between ALM OS and its plugins
- Password sign-ins held back after repeated failures; signing out ends every plugin session at once
- Every screen, the help and the e-mails in English and Polish, chosen by each person
Want to see it with your tools?
Tell us which tools your project uses and we will show you ALM OS on a similar set-up.