Security and compliance

ALM OS is built for projects whose evidence will be audited — and whose networks often have no internet at all.

  • On your premises

    ALM OS runs on your server or virtual machine. There is no ALM OS cloud: nothing about your project is sent to us.

  • Air-gapped installation

    The installation package contains everything; installing it downloads nothing but Docker. Paid plugins arrive as signed packages on a medium of your choice.

  • Offline licences

    Licence files are signed with Ed25519 and checked on your server. No licence server, no activation call, no expiry surprises: notices start 30 days ahead.

  • No telemetry

    ALM OS does not phone home. No usage statistics, no crash reports, no update checks unless you run them.

  • Signed packages

    Every plugin package is signed and every file in it hashed; ALM OS refuses unsigned or altered packages and checks the files again at every start. Installation bundles come with a SHA-256.

  • Your data stays yours

    Items stay in the tools they live in. What ALM OS adds — links, reviews, baselines, signatures — is a git repository on your server, readable without ALM OS. Credentials to the tools stay in their plugins.

  • Evidence never locked

    A lapsed licence makes plugins read-only, never unreadable. Baselines are immutable git tags; evidence is never rewritten, and failures are recorded, not hidden.

  • Encrypted and authenticated

    HTTPS everywhere, mutual TLS between ALM OS and each plugin, single sign-on through your identity provider, roles per project and an audit trail of every operation.

  • Plugins kept apart

    Each plugin gets only its own environment and, in the server image, runs under a user of its own. Stored secrets are bound to their plugin, and ALM OS’s own certificate authority keeps its key outside the data volume and signs only ALM OS’s names.

  • Hardened sign-in and sessions

    Password sign-ins are held back after many failures from one address, and signing out ends every plugin session at once. The interface cannot be framed by another site, and only administrators widen what a project may reach.

  • AI agents only propose

    An agent acts as its person, within their projects and roles, and only proposes: a person accepts. Tokens are scoped and kept only as a SHA-256; every AI call is audited by its metadata, never its content.

  • Offline copies on encrypted disks

    ALM OS Desktop keeps no offline copy on a computer without full-disk encryption (FileVault, BitLocker, LUKS) where ALM OS requires it, which is the default.

Tool qualification (T2)

Under EN 50716 (and EN 50128) a tool whose output supports verification is a class T2 tool, and the project has to justify relying on it. ALM OS is built to make that justification straightforward:

  • A tool manual for assessors: what ALM OS computes, how, and the constraints of use
  • A T2 qualification report against EN 50716 §6.7: selection, specification, evidence of conformance, version identification
  • A requirements-to-tests trace generated from the automated test run of every release
  • Version identification of every component in the installation and in each evidence report

Qualification is always done by the project for its own use of the tool; we give you the evidence to do it.

See it on your own project

We are looking for teams who want to try ALM OS on a real railway project. Every plugin can be tried free for 30 days.