Build your stack

For each ALM area, choose the tool you already have, the ALM OS plugin, or nothing. You get a description of how the set-up works: what each plugin does, what you can do across your tools, the gaps, and the licence it needs.

The interactive configurator needs JavaScript. Below are all supported connections, area by area, and eight example set-ups.

Example set-ups

The eight use cases, as starting points.

  • Jira and Google Drive, nothing for requirements

    How the tools connect

    Already in use

    • Jira
    • Google Drive (planned)
    ALM OS core links · Needs review · impact · baselines · evidence report

    Added with ALM OS

    • ReqManTool · free
    • Test results · paid
    • Documents · paid
  • A team that lives in GitLab

    How the tools connect

    Already in use

    • GitLab
    ALM OS core links · Needs review · impact · baselines · evidence report

    Added with ALM OS

    • ReqManTool · free
    • Test results · paid
  • Azure DevOps and SharePoint

    How the tools connect

    Already in use

    • Azure DevOps
    • SharePoint
    • Entra ID
    ALM OS core links · Needs review · impact · baselines · evidence report

    Added with ALM OS

    • ReqManTool · free
    • Microsoft 365 calendar · free
  • An on-premise railway supplier: Redmine, Jenkins and JFrog

    How the tools connect

    Already in use

    • Redmine
    • Jenkins
    • JFrog
    • LDAP / Active Directory
    ALM OS core links · Needs review · impact · baselines · evidence report

    Added with ALM OS

    • ReqManTool · free
    • Gerrit · paid
    • Risk & Safety · paid
    • Documents · paid
  • Requirements stay in DOORS or Polarion

    How the tools connect

    Already in use

    • ReqIF (DOORS, Polarion, Codebeamer)
    • Jira
    • GitLab
    ALM OS core links · Needs review · impact · baselines · evidence report

    Added with ALM OS

    • Test results · paid
  • A small team on the free package

    How the tools connect

    Already in use

    • Redmine
    ALM OS core links · Needs review · impact · baselines · evidence report

    Added with ALM OS

    • ReqManTool · free
    • My work · free
    • ICS calendar · free
    • LDAP / Active Directory · free
  • A safety team adds Risk & Safety

    How the tools connect

    Already in use

    • ReqManTool
    • Test results
    ALM OS core links · Needs review · impact · baselines · evidence report

    Added with ALM OS

    • Risk & Safety · paid
    • Work · paid
  • Specifications in Confluence

    How the tools connect

    Already in use

    • Confluence
    • Jira
    ALM OS core links · Needs review · impact · baselines · evidence report

    Added with ALM OS

    • ReqManTool · free

All supported connections

Every ALM area, what ALM OS connects to there, and what it does with it.

Requirements ReqManTool · ReqIF (DOORS, Polarion, Codebeamer)
  • Use ALM OS: ReqManTool Free up to 5 modules Built into ALM OS

    ReqManTool keeps the requirements and test cases in ALM OS: modules, hierarchy, attributes, links, ReqIF, CSV and Word export, stored as files in git. Requirements are edited from ALM OS, reviewed and approved under the review workflow, and show their links in ReqManTool.

  • DOORS, DOORS Next, Polarion or Codebeamer (ReqIF) Paid plugin Read-only

    ALM OS reads your tool’s ReqIF exports as deliveries; each new delivery is compared with the one before, and what it created, changed or deleted is reported. Read-only: requirements are still written in your tool.

Tasks and work planning Work · Jira · Redmine · Azure DevOps · GitLab · GitHub
  • Use ALM OS: Work Paid plugin Built into ALM OS

    Work keeps the board, backlog, sprints, releases and roadmap in ALM OS, with templates (CENELEC railway, Automotive SPICE and others) whose workflow guards enforce independence by SIL. Its All tools board also shows the tasks of the project’s other task tools.

  • Jira (Cloud or Data Center) Paid plugin Edits items

    ALM OS reads epics, stories, tasks and sub-tasks, creates new issues in Jira, and edits them (summary, assignee, priority, due date, status) as the person, through Jira’s own workflow.

  • Redmine Free (starter licence) Edits items

    ALM OS reads features, stories and tasks, creates tasks, and edits or assigns them (project, version, person) as the person, with Redmine’s own permissions and workflow.

  • Azure DevOps Boards Paid plugin Read-only

    ALM OS reads epics, features, user stories, backlog items and tasks from Azure DevOps Services or Server. Read-only.

  • GitLab issues Paid plugin Creates items

    ALM OS reads issues and epics, and creates new issues in GitLab as the person.

  • GitHub issues Paid plugin Creates items

    ALM OS reads issues and creates new ones as the person, on GitHub.com or GitHub Enterprise Server.

Bugs and defects Work · Jira · Redmine · Azure DevOps · GitLab · GitHub
  • Use ALM OS: Work Paid plugin Built into ALM OS

    Work tracks problems and changes with the CENELEC flows: problem reports, a change control board, and release checks that no critical or major problem is open.

  • Jira Paid plugin Edits items

    Bugs and change requests in Jira: read, created from ALM OS, and linked to the requirements and tests they concern.

  • Redmine Free (starter licence) Edits items

    Bugs and change requests in Redmine: read, created, edited and assigned from ALM OS.

  • Azure DevOps Paid plugin Read-only

    Bugs and change requests in Azure DevOps Boards, read-only, with their Found In and Integrated in Build fields.

  • GitLab issues Paid plugin Creates items

    Bugs kept as GitLab issues; a project maps the issues to problems in its model settings.

  • GitHub issues Paid plugin Creates items

    Bugs kept as GitHub issues; a project maps the issues to problems in its model settings.

Code and reviews Gerrit · GitLab · GitHub · Azure DevOps
  • Gerrit, run by ALM OS Paid plugin Built into ALM OS

    ALM OS runs Gerrit inside its own image: git hosting and code review, signed in through ALM OS, with review rules by SIL (independent reviewers, a Verified vote from CI, no unresolved comments). Changes and their votes go into baselines; links are written as change messages.

  • GitLab Paid plugin Creates items

    Merge requests, commits and issues; each ALM OS link is written as a note on the merge request or issue. A baseline pins the repository at a commit.

  • GitHub Paid plugin Creates items

    Pull requests, commits and issues on GitHub.com or GitHub Enterprise Server; each ALM OS link is written as a comment. A baseline pins the repository at a commit.

  • Azure DevOps Repos Paid plugin Read-only

    Pull requests and commits, read-only.

CI and builds Jenkins · Test results
  • Jenkins or CloudBees CI Paid plugin Read-only

    ALM OS reads jobs and pipelines, builds with their result, revision and stages, archived artifacts with their fingerprints, and JUnit test reports. Read-only; each finished build is reported as an event.

  • Any CI that writes JUnit XML or Robot Framework files Paid plugin Built into ALM OS

    Your pipelines (GitLab CI, GitHub Actions, Azure Pipelines…) copy their result files to a folder the Test results plugin reads. ALM OS reads the test results, not the builds themselves.

Binaries and artifacts Artifacts · JFrog · Jenkins
  • Use ALM OS: Artifacts Paid plugin Built into ALM OS

    Artifacts keeps build outputs, packages, firmware and any other file in repositories per project, each version by its SHA-256; uploads resume after a broken connection and downloads are checked against the SHA-256 first. A product version’s SBOMs (CycloneDX, SPDX) are matched against a local vulnerability feed (OSV or NVD), imported as a file, never fetched.

  • JFrog Artifactory and Xray Paid plugin Read-only

    ALM OS reads build-info, artifacts with their SHA-256, Release Bundles v2 with their promotions, and the Xray security issues of builds and bundles, from JFrog Cloud or a self-hosted platform. Read-only.

  • Jenkins archived artifacts Paid plugin Read-only

    The artifacts Jenkins archived, with their MD5 fingerprints; a SHA-256 only where the build archived a checksum file next to them.

Tests and results ReqManTool · Test results · Jira · Azure DevOps · Jenkins · ReqIF (DOORS, Polarion, Codebeamer)
  • Use ALM OS: ReqManTool test cases Free up to 5 modules Built into ALM OS

    Test cases and test executions kept in ReqManTool next to the requirements and linked to them for coverage.

  • CI result files (JUnit XML, Robot Framework) Paid plugin Built into ALM OS

    The Test results plugin reads each result file as a test run; each test keeps one identity across runs, so its links stay valid when it runs again. It also keeps manual tests: test cases, plans, runs and campaigns, executed step by step.

  • Jira with Xray or Zephyr Scale Paid plugin Edits items

    Tests, test sets, plans, executions and their results from Xray or Zephyr Scale, read-only.

  • Azure DevOps Test Plans Paid plugin Read-only

    Test cases, test runs and test results, read-only.

  • Jenkins JUnit reports Paid plugin Read-only

    Each build’s JUnit report as a test run, with a result per test.

  • Polarion or Codebeamer test cases (ReqIF) Paid plugin Read-only

    The test cases that come with the ReqIF exports, read-only.

Documents Documents · Wiki · Confluence · SharePoint · Google Drive (planned)
  • Use ALM OS: Documents Paid plugin Built into ALM OS

    Controlled documents kept by ALM OS: every version identified by its SHA-256, older versions archived and never deleted, check-out and check-in, editing in Word, Excel, PowerPoint or LibreOffice, AsciiDoc documents kept in git, a document register and the review workflow. ALM OS Desktop syncs a Documents folder with a folder on your computer.

  • Use ALM OS: Wiki Free Built into ALM OS

    The project’s and its products’ wiki: pages in Markdown or AsciiDoc in a git repository ALM OS hosts, each save a commit, linked to items by key and taken into baselines.

  • Confluence (Cloud or Data Center) Paid plugin Read-only

    Pages, blog posts and attachments, read-only; baselines keep controlled copies: the exact version and the SHA-256 of what Confluence stores.

  • SharePoint Paid plugin Read-only

    The documents of a SharePoint site’s libraries, through Microsoft Graph or a library synced by OneDrive; read-only, each document identified by its content hash.

  • Google Drive (planned) Planned

    A Google Drive plugin is planned, not built. Today the files that need control are uploaded to Documents.

Risk and safety Risk & Safety
  • Use ALM OS: Risk & Safety Paid plugin Built into ALM OS

    Hazard log with an EN 50126 risk matrix, mitigations and safety requirements, FMEA worksheets, fault trees (FTA), the SRAC register (EN 50129) and cybersecurity threats with their TARA (CLC/TS 50701), kept in git, every change a commit.

Sign-in Entra ID · OpenID Connect · LDAP / Active Directory · GitLab · GitHub · Jira
  • Microsoft Entra ID Free Sign-in

    Single sign-on with Microsoft 365 accounts, with their users and groups for the people pickers.

  • OpenID Connect (Keycloak, Okta, Auth0, Google Workspace…) Free Sign-in

    Single sign-on through any OpenID Connect provider.

  • LDAP or Active Directory Free Sign-in

    Sign-in with the directory password on ALM OS’s own form, with the directory’s users and groups.

  • GitLab accounts Paid plugin Creates items

    Sign-in through GitLab; it works without the GitLab plugin’s licence.

  • GitHub accounts Paid plugin Creates items

    Sign-in through GitHub, for the members of your organisation; it works without the GitHub plugin’s licence.

  • Atlassian accounts (Jira Cloud) Paid plugin Edits items

    Sign-in through Atlassian, for Jira Cloud only: people with access to the Jira site get in. It works without the Jira plugin’s licence.

Calendar and My work Microsoft 365 calendar · ICS calendar · Google Calendar sign-in (planned) · My work
  • Microsoft 365 / Teams Free Calendar

    Each person connects their Microsoft 365 calendar; My work shows their meetings with the online join link.

  • Any calendar with an ICS address Free Calendar

    Outlook’s published calendar, on-premises Exchange, Google Calendar’s secret iCal address: each person pastes theirs. ALM OS keeps it encrypted and reads only times, titles and join links.

  • Google Calendar sign-in (planned) Planned

    Connecting Google Calendar with a Google sign-in is planned, not built. Today its secret iCal address works.

  • Use ALM OS: My work without a calendar Free Built into ALM OS

    Each person’s to-dos, what the tools assign to them, the plan for today and the week, and the work report, without meetings.

ALM OS is built for tool qualification under EN 50128 / EN 50716 and ISO 26262-8, and each release comes with its qualification kit. It is not certified: each project qualifies the tool for its own use, and a pre-release (beta) is not for qualified use.