Docs Getting started
What is gridtrue?
A self-contained Git platform where the remote, CI, and ledger are one system.
gridtrue is verifiable CI/CD that ships with the repo. Every build, test, and local deploy you run becomes a cryptographically signed attestation on your team's private network — before the push ever leaves the machine.
gridtrue is a standalone Git platform. The remote you push to, the CI that validates, and the ledger that records it are one system owned by your organization. You get four things you could not get before: proof that the code ran, proof that the tests passed, proof of who ran them, and early warning when a teammate is about to collide with your work. Everything is standard Git, so exporting to any other remote is always a single push away.
What gridtrue gives you
- Verifiable CI
- Every build and test is signed by the developer that ran it. 'Works on my machine' becomes a cryptographic receipt.
- Conflict Radar
- The moment a teammate attests overlapping work, a quiet notification fires. A 30-second conversation prevents the 40-minute merge conflict.
- Continuous state
- Every commit has a single lifecycle: DRAFT → VALIDATING → ATTESTED → PROMOTABLE → DEPLOYED. The state is on a ledger your organization owns.
- Instant onboarding
- git clone pulls code, environment, policy and identity in one step. First signed commit in under 10 minutes.
What gridtrue is not
- Not a cryptocurrency, not a token, not a Web3 project.
- Not an accessory to another Git host — gridtrue is the remote, the CI, and the ledger as one system.
- Not a hosted CI vendor — CI runs on your developers' machines, not on rented build minutes.
- Not a supply chain signing tool for external consumers — we export to SLSA, in-toto and Sigstore when you need it, but the primary job is internal team verification.
Read next
- How it works — the four phases every commit walks through.
- Quickstart — the ten-minute install-to-attestation path.
- CLI → Commands — the full verb surface of the gridtrue binary.