Skip to Content

FinOps & managementPlatform & DevOps

Cut CI Costs

The problem

Runners billed by the minute, machines left idle between jobs, a large instance to run a linter: the CI bill grows faster than the team.

With Cadence.CI

  • Steps run on machines Cadence.CI starts in your own cloud account, billed by your provider at its rates, with no per-minute charge on top.
  • Each step gets the smallest instance that fits what it declares, ARM or x86, and its machine stops when the step ends.
  • Every run lists what each of its parts requested, and each cloud account lists the instances started and the run each one served.
1

The step declares

2 CPU4 GiB memory10 GiB storageARM64
2

Cadence.CI picks

  • Account ⁨1⁩2 vCPU · 2 GiB · arm64
  • Account ⁨1⁩2 vCPU · 4 GiB · arm64
  • Account ⁨2⁩2 vCPU · 4 GiB · x86_64
  • Account ⁨2⁩4 vCPU · 8 GiB · arm64

The smallest instance type that fits, among all your connected cloud accounts

3

In your account

starts
build
stops

The instance starts, runs the step, and stops when it ends. Your provider bills it, at its rates.

DevelopersPlatform & DevOps

Get Feedback in Seconds

The problem

Push, wait ten minutes, read a red X, guess, push again. Reproducing a failure means running everything once more.

With Cadence.CI

  • The whole pipeline, types, connections and parameters, is checked in about a second, before a single machine starts.
  • Each run keeps its logs, its debug events, and the exact program and parameters it ran with; the run page replays them on the pipeline graph.
  • The same pipeline runs on your own machine first, its steps as local containers, before you push anything.
melodium check1 error

Connection from startup to test is not possible

trigger sends a Block<void>, while the data input of test expects a Stream<byte>.

Found in about a secondNo machine started
Open the CI/CD template in the playground

Platform & DevOpsDevelopers

Adopt It Without Migrating Everything

The problem

Changing CI usually means rewriting every pipeline at once, and nobody has time for a big-bang migration.

With Cadence.CI

  • Launch pipelines from your GitHub Actions or GitLab CI jobs, on the runners you already have, for one job or for all of them.
  • An AI assistant converts your workflows into checked pipelines, with the Mélodium MCP server and skills.
  • Move steps to your own cloud account when it pays off, without rewriting the pipeline.

Your CI today

A GitHub Actions or GitLab CI job

Cadence.CI

Checks and launches the pipeline

Steps on the runners you already have

Or steps in your own cloud account

Moving steps from one to the other changes where they run, not the pipeline.

Security & compliancePlatform & DevOps

Comply With the CRA and NIS2

The problem

Since 11 September 2026, an actively exploited vulnerability must be reported within 24 hours. From 11 December 2027, every CRA obligation applies to each release.

With Cadence.CI

  • The SBOM and the vulnerability scan are steps of the release, which is pushed only once they succeed.
  • Their outputs are artifacts with their SHA-256, a change history and a lock, kept up to ten years on Pro in buckets of your own.
  • For NIS2: machines in your own account, run identities valid ten minutes, and a record of every use of a secret.
The CRA and NIS2 in your pipeline

Release run

build
sbom
scan
push

The artifacts are pushed only once the scan succeeds.

sbom-v2027.1Locked
SHA-256
9f2c…e41a
Expires
2037, ten years on Pro
Copies
Your primary bucket, and a replica with another provider
History
Pushed by its run, locked by an administrator

AI & dataSecurity & complianceDevelopers

Run AI Agents Safely

The problem

An agent in CI reads text anyone can write, issues, pull requests, logs, and acts with whatever its step can reach.

With Cadence.CI

  • Which element receives which secret is written in the program; the value is revealed only there, masked in logs and refused in artifacts.
  • Agents check the whole pipeline in about a second with the Mélodium MCP server, instead of pushing commit after commit.
  • Every step is recorded, with the audit of which element used which secret.
Agents and AI pipelines

Agent step

Reads the issue, the diff, the logs
Proposes a change

No secret wired to it: none to leak.

Release step, its own machine

Checked pipeline, reviewed change
Secret revealed to the push only

Cloud access through a token valid ten minutes.

Both steps are recorded: program, parameters, logs, debug events, and which element used which secret.

Security & compliancePlatform & DevOps

Keep Control of Where It Runs

The problem

Pipelines tied to one vendor's runners and cloud, and no clear answer to where your code is built or who can reach it.

With Cadence.CI

  • Data between steps goes straight from machine to machine, and secrets kept on your side never reach Cadence.CI.
  • Use any supported provider, several in one pipeline, or your own machines. Cadence.CI runs on libre and open-source technology, with infrastructure partners incorporated and located in the EU.
  • On Enterprise, the same pipeline runs fully offline, in an air gap. Released binaries cover Linux, macOS and Windows, on x86-64, ARM64 and i686.

Cadence.CI

Coordinates the machines and keeps the records of each run

status, logs, debug events

start and stop machines

Your side

Cloud account ⁨1⁩
Cloud account ⁨2⁩
Your machines
  • Data between steps goes from machine to machine
  • Secrets kept on your side are resolved where they are used
Air gap: the same pipeline, with no link to Cadence.CI (Enterprise).

AI & dataDevelopers

Build Data and AI Pipelines

The problem

Data pipelines fail halfway without saying why, and every AI request goes to the largest, most expensive model.

With Cadence.CI

  • Pipelines are programs where data streams between steps, checked as a whole before they run.
  • Route each request to the model that needs to answer it, and keep the boundary between local and remote models visible in the pipeline itself.
  • Data and AI pipelines get the same logs, debug events and resources as CI.

Where you launch the program

Prompt received over HTTP
JavaScript function rates how complex it is
Reply sent back
promptanswer

Remote model APIs

Economy model, 200 tokens max
Standard model, 600 tokens max
Premium model, 1,500 tokens max
See the full program in the playground

Developers

Run Open-Source Projects for Free

The problem

Open-source projects need CI their contributors can read and follow, at no cost for the maintainers.

With Cadence.CI

  • The open-source plan gives unlimited members, unlimited concurrent jobs, and the run history and storage of Basic, at no cost.
  • Runs, their logs and their program are public, ready to link from merge requests and READMEs; debug events stay visible to members only.
  • Contributors check their changes to the pipeline in about a second, before they push.

Merge request #128: fix the parser

Pipeline passed

View run

Public run page

  • Status and resultPublic
  • LogsPublic
  • ProgramPublic
  • Debug eventsMembers only
Unlimited membersUnlimited concurrent jobs€0

Want to know more?

Every project is unique, and Cadence.CI will not have the same impact on each of them. If you need some guidance or information, feel free to reach us.