Skip to Content

Web Summit · CI/CD · DevSecOps · CRA

Your pipeline has a legal deadline.

Selling software or connected devices in the EU? Under the Cyber Resilience Act, every release carries legal obligations, wherever you are based. Cadence.CI turns each of them into a pipeline step, on the infrastructure you choose.

WS26STAND

Extended Pro trial, valid until 30 November 2026.

Create your account, then enter the code under “Have a code?” on your organization's page.

What other CIs leave to you

Errors
GitHub Actions, GitLab CIFound after the push, on a billed run
Cadence.CICaught in about a second, before any machine starts
Debugging
GitHub Actions, GitLab CIText logs; rerun in debug mode to learn more
Cadence.CIDebug events of every run, replayed on the pipeline graph
Replay
GitHub Actions, GitLab CIAn old release means rebuilding its workflow and runner image of the time
Cadence.CIEvery run keeps the exact program and parameter values it ran with
Runners
GitHub Actions, GitLab CIHosted runners billed per minute, setup repeated each job
Cadence.CIOne machine per step, in your own cloud account, stopped when the step ends
Providers
GitHub Actions, GitLab CIThe vendor's runners, prices and quotas
Cadence.CIAny supported provider, your own machines or air gap, several in one pipeline
Secrets
GitHub Actions, GitLab CIEnvironment variables, masked in logs afterwards
Cadence.CIRevealed only to the element that uses them, every use recorded
AI agents
GitHub Actions, GitLab CIAnother job step, with the job's token and secrets in reach
Cadence.CIChecks its pipeline in a second through the MCP server, and gets only the secrets wired to it

Is your release pipeline CRA-ready?

Tick each yes. Eight questions, two minutes. Under each no, what Cadence.CI does about it.

⁨0⁩ / ⁨8⁩ · Start now

Each missing yes is a gap the CRA expects you to close by 11 December 2027. Reporting already applies, since 11 September 2026.

The CRA in three dates

  1. 10 Dec. 2024

    The Cyber Resilience Act enters into force.

  2. 11 Sept. 2026Live

    Actively exploited vulnerabilities and severe incidents must be reported within 24 hours, for products already on the market too.

  3. 11 Dec. 2027

    Every obligation applies, from secure development to the declaration of conformity.

Who it concerns

The CRA applies to anyone placing software or connected devices on the EU market, wherever they are based. NIS2 applies to the essential and important entities of the sectors it lists, digital providers among them, as each member state transposes it.

What is at stake

CRA: up to €15 million or 2.5% of worldwide annual turnover, whichever is higher, and the product can be withdrawn from the EU market.

What the law asks, what the pipeline does

Four obligations of the CRA, each answered by a step or a record of your pipeline.

The law · report in 24 h

Know at once which shipped versions carry the exploited component.

Each release pushes its software bill of materials (SBOM) as an artifact of its run, in your own storage, at a stable address. A script reads them all and lists the versions that ship the component.

CRA Art. 14 · Annex I, Part II (1)

The law · no known flaw

Nothing ships with a known exploitable vulnerability.

A scanning step runs before the push, and the release is pushed only when it succeeds. The pipeline itself is checked in about a second, before any machine starts.

CRA Annex I, Part I (2)(a)

The law · support 5 years or more

A 2027 version must still be rebuilt and patched in 2032.

Each run keeps the exact program, parameter values and container image names it ran with. With pinned dependencies, patching an old version starts from what its release actually ran.

CRA Art. 13 (8)

The law · keep 10 years

Evidence for every release, ready on request.

Artifacts are kept up to ten years on Pro, with their SHA-256, the history of every change, and a lock nobody can lift. Each one is copied to every bucket you add, with the providers and in the jurisdictions you choose.

CRA Art. 13 (13)

Also under NIS2?

Essential and important entities must secure their supply chain and the development of their systems, and send an early warning within 24 hours of a significant incident. The same records answer both laws: machines in your own account, short-lived run identities, the secret audit, and every run kept.

NIS2 in your pipeline

Plans

Access

Free

Your GitHub or GitLab runners, up to 10 users

Basic

€⁨29⁩

Your cloud accounts, artifacts kept five years

Pro

€⁨55⁩

Artifacts kept ten years, machine policies, custom roles

Enterprise

On Quote

Air gap, on-premise, dedicated SLA

Per user and month, excl. VAT, billed annually. Machines and storage are billed by your provider at the rates you already have: no markup, no per-minute charge.

Compare plans

WS26STAND

Extended Pro trial, valid until 30 November 2026.

Create your account, then enter the code under “Have a code?” on your organization's page.

Send us one workflow

Send one GitHub Actions, GitLab CI or Jenkins workflow: you get it back as a Cadence.CI pipeline within 48 hours.