How it works
Every build starts clean and ends with proof.
Here is what happens each time you start a build.
The four steps
You pick what to build
A project, a target and a revision: a branch, a tag or a commit.
We fetch the exact commit
The revision is turned into one commit SHA. That SHA is what gets built and recorded.
It builds in a sandbox
A fresh workspace with limits on memory, processes, disk and time. Nothing else on the machine is reachable.
You get the files and the proof
Each file gets a size and a SHA-256. The full log is kept. The workspace is deleted.
One build, start to finish
This website keeps your settings and the results. Only the build runner fetches code and runs build steps.
Cancel any time
Cancel stops the build and every process it started. The workspace is still deleted.
Run it again
A failed, cancelled or interrupted build can be run again with one button, on the same revision.
Nothing is faked
A build appears in your list only after the runner accepted it. If building is not on for you yet, the dashboard says so.
Start with one project
Building is inactive until it is priced. Ask about access.