457 pushes a second. Every one with a receipt.
Built for the volume agents produce. Your code lives in object storage, CI starts warm, and every merge leaves proof.
Sigbound, Cursor, GitHub
| Sigbound | Cursor | GitHub | |
|---|---|---|---|
| Pushes a secondHow many pushes can land at once, each one fully persisted before git is told it succeeded. | 457each one with a receipt | 120 | Not published. The rate limits are. |
| Push to greenFrom a push to a green three-job CI workflow, sandboxes already warm. | 9 sSigbound CI | Bring your own CI. | 15 ssame workflow, hosted runners |
| An AI reviewA read of the exact head against what done means, every claim cited to a line of code. | 12¢per review, not per seat | Comments on the diff. Per seat. | Comments on the diff. Per seat. |
| Where your code livesObject storage is durable and scales with replicas; disks are fast. Sigbound uses disks only as a cache. | Object storagedisks are a cache | Object storage | Disks. Three of them. |
| Proof of every mergeA signed statement of what landed, on what evidence, approved by whom. Verifiable offline, without Sigbound. | A receiptsigned, verifiable offline | A merge commit. | A green check, and your memory. |
Sigbound figures are measured on a published benchmark. Cursor figures are from Cursor's published engineering notes. GitHub push to green is the same workflow timed on GitHub Actions. Where a column has no number, nobody has published one.
Your code lives in object storage
Most forges keep repositories on disks and replicate the disks. Sigbound writes every push to object storage first, as an append-only log, and treats every disk as a cache. That is where both the throughput and the durability come from.
- 1Push
The pack is written straight to object storage, as an entry in an append-only log.
- 2Persisted
A push is never acknowledged until it is fully persisted. Only then does git say done.
- 3Receipted
The landing is signed and sealed to the ledger in the same write.
- 4Compacted
Small packs fold into large ones behind the acknowledgement. Replicas read the compacted log.
- 5Cached
Repositories on disk are a cache. Any node can be lost and rebuilt from the log; nothing is lost with it.
A push is one append, one signature, one ledger sequence. Busy repositories group-commit; quiet ones wait for nobody. Read throughput grows with every replica added.
A node can fail mid-push and the push is either fully landed or never acknowledged. Repositories move between nodes freely. Backups are the storage's own versioning, to any point in time.
Clone, fetch, push, with any client. The log is Sigbound's; the format on your machine is git's.
Push to green in nine seconds
CI runs in isolated sandboxes that start warm. When a tree has already been verified, its evidence is reused and the run takes no time at all.
From push to a green three-job workflow. Sandboxes boot in under a second with the runtime and actions already in place, and the verdict is written to the attempt's evidence.
The same workflow file, the same jobs, on hosted runners.
How the numbers are measured
Measured on a benchmark Sigbound publishes with its source: small packs, the shape of an agent's commit, with compaction, replication and a receipt on every push.
One three-job workflow file, run on Sigbound CI and on GitHub Actions on the same repository, the same day.
The average cost across every review on the hosted alpha. Each receipt records what its own review cost.