About
We are building the record, not another way to run a script
Everyone already has something that runs the build. Almost nobody has something that can prove, six weeks later, exactly what went in and who let it out.
- 2024
- Founded
- 31
- People
- 4
- Countries
- Series A
- Stage
Our story
Why this exists
Girder came out of eighteen months spent answering the same question at two different companies: what exactly is running in production, and which commit produced it. Both had a CI system. Neither could answer without a person reading logs. The build worked; the record of the build did not exist. We wrote the record first — the signature, the inputs, the closure — and the builder second, because a builder without a record is the thing everybody already has.
Every team we knew was rebuilding that layer badly, in a hurry, under a deadline set by a demo that had gone well. It is not a differentiator for any of them and it is genuinely hard to get right, which is a fairly precise description of something that should be bought rather than built.
How we work
We ship small and we ship often, and we write down what we learn. The engineering notes on this site are not marketing; they are the internal write-ups, edited lightly.
We keep the output verifiable without us. Attestations use open formats and, on Enterprise, your own signing keys — so a customer who leaves keeps a provenance history that still verifies. Building a lock-in we would have to defend is not a business we want.
How we decide
Four things we argue from
Not values in the poster sense. These are the sentences that actually end disagreements here.
01
Legible over clever
If explaining what the system did requires an engineer, the system has not finished the job.
02
Default to the safe path
The guarded route has to be the quick one, or people will route around it and be right to.
03
Measure before building
We have optimised the wrong end of a funnel because it was the end we had instrumented. Once was enough.
04
Say the number
Claims on this site come with the measurement behind them, or they do not go on the site.
Team
The people behind it
Thirty-one of us across four countries. These are the ones you are most likely to end up on a call with.
Maya Okonkwo
Co-founder & CTO
Tomas Halvorsen
Co-founder & CEO
Inès Lefebvre
Head of Security
Daniel Reyes
Principal Engineer
Priya Raghunathan
Head of Design
Kwame Mensah
Head of Customer Engineering
Seal one service and see.
Run Girder beside your pipeline for a week and compare the artifact hashes. If they don't match, you have learned something worth knowing either way.
Free for 14 days · No card required