ICR · Engagement model
Not a SaaS subscription. A contracted, premium service.
You cannot sign up for ICR with a credit card, and that is deliberate. The capacity is real hardware, the isolation is built per customer, and every tenant is known, onboarded and reachable. ICR is sold the way infrastructure has always been sold to companies that depend on it: under a contract, with a named operator.
What ICR is not
Three things you will not find here.
- No self-service signup, free tier or anonymous tenants.
- No public price list: pricing depends on the concurrency ceiling and the usage profile we agree on.
- No uptime figure we cannot stand behind: the status of the tier you buy is written into the contract.
What ICR is
A service with a contract, an operator and an exit.
A contract, not terms of service
A short service annex fixes the scope, the tier and its status, the sizes and ceiling you get, the fallback rule, the data and access clauses, and how either side exits. It is signed by both companies.
Two ways to pay
A monthly contract with an included volume of normalised minutes for teams with a steady load, or a smaller base with usage-priced minutes for teams with a bursty one. Both are stated on the annex; minutes are counted per job.
Onboarding by the operator
We install nothing on your side but a GitHub App. We create the scale sets, run a canary week with your tech leads, and switch your organisation when they say so.
A statement you can audit
Every month you receive a job-level statement: repository, workflow, size, duration, normalised minutes. Invoices are issued through a certified e-invoicing platform, as French law requires from 2026.
A named operator
You know who runs the service, how to reach them and when. Support is business hours, Paris time, with a named backup for absences.
An exit you control
Switching back to GitHub-hosted runners is one variable, at any time, without asking us. The contract has a monthly notice and no minimum term beyond the pilot.
Status
One status ladder, on the site and in the annex.
Every tier is labelled with where it stands. The label on this site and the label on your annex are the same word, and a commitment appears only at the last step.
- 01Planned
Designed, not running. Register interest; the tier opens on a public threshold.
- 02Early access
Running for a few customers, no availability commitment, priced per customer.
- 03Available
Contracted, with the availability commitment written in the annex.
Fit
Who it is for.
ICR fits engineering teams of five to fifty developers whose builds are CPU-bound and whose wait time costs more than the runners do. It does not fit teams that need a public SLA today, or workloads that must stay on a public cloud for compliance reasons.