gridtrue attestation
block #84,329integration-tests passed · signed
- repo
- acme/payments
- commit
- a3f1c22
- runtime
- podman 5.2
- host
- macOS arm64
- duration
- 12.8s
- signer
- [email protected]
- signed-at
- 2026-04-21T14:22:05Z
v0 · early access
Your onboarding at light speed. Your code with collective awareness.
Stop spending two days reading readmes before you see your landing page. With gridtrue, git clone gives you the code, the environment, the policy, and a living record of what your team is doing — right now.
No credit cardNo team size limitForever free
- No build-minute bills.
- Your keys stay on your machine.
- Export the full network and leave any time.
- We do not train models on your repos.
- Your peers see your overlaps. Your managers never do.
~/acme/backend
$ git clone https://gridtrue.io/acme/backend $ cd backend gridtrue: installing toolchain (go 1.23)… gridtrue: starting local services… gridtrue: ready. 9 minutes, 12 seconds. $ git commit -m "fix: handle null charges" gridtrue: running validations… ✓ build (container, 4.1s) ✓ unit-tests (container, 12.8s) ✓ attestation signed by [email protected] gridtrue radar: [email protected] attested on services/charges.ts 3 min ago
Every developer has said it. None could prove it. Until now.
01 · Before
A Slack message, and a prayer.
"it works on my machine 🤷". Someone merges. Production breaks on Friday. The post-mortem concludes "we should test more thoroughly." Nothing changes.
02 · The fix nobody asked for
Rebuild what you just built. Twice. For $12k/month.
Remote CI solved trust by centralizing compute. Then billed per minute for the privilege of recompiling the exact code the developer just compiled, on hardware they already own.
03 · With gridtrue
A receipt, not an excuse.
Every passing validation is signed by the developer, recorded on the org’s permissioned ledger, and visible to the network in real time. Immutable, peer-endorsed, permanently filed.
Onboarding, CI cost, the excuse heard round the world, and the conflict that shipped as a bug.
problem 01
Clone is onboarding.
Today
New hire clones the repo. Spends 3–5 days on “why won’t this run locally?” — wrong Node version, missing env vars, a Postgres dump someone has on Slack from 2019, a make setup that last worked two refactors ago.
The repo contains code, not environment. Onboarding docs rot faster than they’re written. “Ask Pedro” is not a scalable system.
With gridtrue
git clone brings down policy, pinned container images, the local stack definition, and the developer’s identity in the org’s network. First gridtrue validate spins up the full local environment.
problem 02
Your developer fleet is your CI fleet.
Today
8–12 minutes waiting for GitHub Actions or Jenkins to recompile the exact code the developer just compiled. Bills at month-end in the thousands. If the build fails because of a typo, the developer has already context-switched to Slack.
CI moved to remote servers because “works on my machine” was unprovable. The fix centralized trust — and with it, cost.
With gridtrue
Validation runs on the machine where the code already is, in the environment the developer already has. Feedback in 30–90 seconds. No build-minute bill at month-end.
problem 03
“Works on my machine” becomes a receipt, not an excuse.
Today
Developer A says it passed locally. Developer B pulls, it breaks. Developer C merges anyway. Production is down. The post-mortem is: “we should have tested more thoroughly.”
There is no artifact that says what was tested, with what environment, by whom. The phrase is a social contract, not a technical one.
With gridtrue
Every passing validation produces a signed attestation — runtime, image digest, OS, architecture, duration, cryptographic identity — written to the org’s ledger. The question “what did you actually test?” has a receipt.
problem 04
Conflicts surface when they’re still conversations, not commits.
Today
María and José start editing the same file at the same time. Neither knows. Four hours later María pushes, José gets a merge conflict, 40 minutes vanish. Worst case, the textual merge succeeds but their semantic assumptions diverge and a subtle bug ships to production.
Git was designed for asynchronous collaboration. Pull requests surface conflicts only after they’re already structural. There is no primitive in Git for pre-commit awareness of parallel work.
With gridtrue
The same attestation stream that gives us verifiable CI also tells every local runner what teammates are working on. The moment someone attests work on a file you’re also modifying, a quiet notification surfaces. The 30-second conversation that prevents the 40-minute merge conflict. We call it Conflict Radar.
Four steps. No server to rent.
- 01 · Clone
Clone
git clone brings down code, environment, policy, and your cryptographic identity for this network.
$ git clone gridtrue.io/acme/payments - 02 · Validate
Validate
The local runner executes tests in your preferred runtime — Docker, Podman, native, VM. Your choice, your hardware.
$ gridtrue validate - 03 · Attest
Attest
Pass or fail is signed with your organization identity and written to the ledger. Peers endorse. The network sees it.
$ gridtrue push # attestations flush automatically - 04 · Promote
Promote
Deployment tools query the ledger before applying a manifest. Unverified commits never reach staging or production.
$ argocd sync --only-if-promotable
Conflict Radar · A primitive Git never had
Conflicts surface when they’re still conversations, not commits.
The same signed attestation stream that makes CI verifiable also tells every local runner what teammates are working on — file by file, in real time. When overlap is high enough to matter, a quiet notification appears. Everything else stays silent.
A peer tool, not a supervisory one
Managers never get a radar view. There is no "who’s working on what" dashboard and there never will be.
Metadata only — never your code
File paths, attestation results, provenance. Bytes stay on your machine. No keystrokes. No cursor positions. No edit history.
Warnings, not blockers
The radar never prevents a push. It informs — and the decision to push anyway is itself recorded on the ledger.
Symmetric opt-out
Mute the radar for a repo, an org, or globally. If you opt out, you don’t see others and others don’t see you. No power asymmetry.
pre-push radar scan
$ git push
⚠ Potential conflict detected before push
Your push will include commits touching:
billing/validator.ts
billing/types.ts
In the past 90 minutes, a teammate attested work on
overlapping files on the same branch:
- José Ramírez <[email protected]>
branch: feature/refund-flow
files: billing/validator.ts
last: 12 minutes ago (passed · unit-tests)
Continue push? [y/N]
For solo developers and tiny teams
A senior engineer on every commit.
You don't have a team to review you. You don't have budget for a senior SRE. gridtrue runs the same pipeline they would — build, tests, vulnerability scan, obsolescence check, policy — on your laptop, before every push. Signed evidence stays in your ledger, so when you hire your first engineer in eight months, they can see exactly how the code got to where it is.
~/side-project
$ gridtrue init
gridtrue: detecting project…
language node 20.11 (pinned via .tool-versions)
runtime podman 5.2 (detected)
tests vitest 1.6 (detected)
deps 127 packages — scanning for CVEs…
policy starter (default for solo tier)
gridtrue: ready. one pipeline on every commit, free forever.
pre-push pipeline
$ git commit -m "feat: add retry on transient failures"
gridtrue: running validations…
✓ build (container · podman 5.2 · 3.9s)
✓ unit-tests (container · podman 5.2 · 8.1s)
✓ vuln-scan (0 critical, 0 high)
✓ deps-obsolete (3 minor updates available — non-blocking)
✓ policy (starter rules: tests present, no skip)
✓ attestation signed by [email protected] · block #1,204
Try it on one repo. Leave at any time.
$ git push gridtrue main Point one repository at gridtrue and see what happens. Validation runs on the developers' machines that already have the code; every pass is signed and written to your team's ledger. If the team doesn't want to stay, `git push` the full history to any other Git remote and you're out — no platform lock-in, no format conversion, no recovery plan required.
-
Start with one repo
You don't have to move every repository on day one. One project is enough to feel the difference.
-
No forced rollout
Individual developers opt in per repo. The team adopts at the pace the team wants.
-
Standard Git, all the way out
Everything in gridtrue is a regular Git repository. Export pushes the full history plus a portable attestation bundle — no vendor format, no export fee.
Supply chain
Built for the post-SolarWinds world.
Supply chain attacks cost enterprises billions. The common thread: an unverifiable gap between what the developer built and what shipped to production. gridtrue closes that gap by construction — every build signed by the developer’s cryptographic identity, every validation recorded on a ledger your organization controls, every deployment gated on a query to that ledger.
For teams that need supply chain compliance, we export to industry standards: SLSA provenance, in-toto attestation format, Sigstore-compatible signatures. Your auditor gets the receipts; your developers don’t need to think about it.
- SLSA provenance
- in-toto attestations
- Sigstore-compatible
- SOC 2 Type II (Enterprise)
A new category, not a faster runner.
gridtrue is the developer platform built around verifiable truth instead of centralized trust. The remote, the CI, and the ledger are one system — designed together, owned by your organization, exportable on demand. What we replace is the business relationship with your CI vendor and the trust gap underneath it.
| GitHub Actions | Jenkins / Hosted CI | gridtrue | |
|---|---|---|---|
| Where builds run | Hosted runners you rent | Servers you own and maintain | Developer machines you already own |
| Cost model | Per minute, per concurrency | Infra + pager duty + upkeep | Per seat, fixed |
| Proof of what was tested | Server log in the vendor UI | Server log in your UI | Signed attestation on your ledger |
| Onboarding a new hire | Setup scripts, secrets, 3–5 days | Setup scripts, VPN, tribal knowledge | git clone + gridtrue validate |
| Data ownership | Logs owned by the vendor | Yours, if you built the storage | Permissioned ledger you can export |
| Supply chain provenance | Add-on (OIDC + third-party) | Bolt-on plugins | Built-in (SLSA, in-toto, Sigstore) |
| Parallel work coordination | None — surfaces at merge time | None — surfaces at merge time | Conflict Radar — surfaces at the moment of overlap |
Free forever. Pay per seat when your team is ready.
The Free tier has unlimited seats — bring your whole team at zero cost. Pro charges per seat when you need HA, SSO, and guaranteed uptime. We never charge per build-minute, per commit, or per attestation: CI runs on the machines you already own.
Free
Real Git, cryptographic proof, zero setup. No credit card.
$0 / forever
No credit card · No team size limit · Forever free.
- Unlimited seats
- 5 private repos
- 5 GB storage
- Unlimited attestations
- Conflict Radar (full)
Pro
For teams running real production work.
$29 / seat / month
billed annually, or $35 monthly
- Everything in Free, plus:
- Unlimited seats & repos
- 100 GB storage included
- Unlimited attestations
- SSO (OIDC)
Enterprise
For regulated workloads and large organizations.
From $999 / org / month + seats
- Everything in Pro, plus:
- Region pinning & data locality
- CMEK & VPC peering
- SOC 2 Type II, HIPAA BAA
- Dedicated cluster option
Your onboarding is a readme festival.
Your onboarding is an incomprehensible IDP: more credentials for git, cloud, and the rest, only to then read the readme festival — which environment variables you need, which Docker images you need, how to compile them — so that, one or two days later, you finally see the landing page you're supposed to be working on.
gridtrue is `git clone`. In 10 minutes you know everything that was done, where it was done, with local deploy without manual configuration, without reading readmes. You code a change, you commit, and in seconds you know whether what you did broke the system.
Your onboarding at light speed. Your code with collective awareness.
Regulated workloads, dedicated peers, your keys.
Region pinning. Customer-managed encryption keys. VPC peering. Audit log export to your SIEM. Named support engineer and 40 hours of implementation. If your auditor asks “who built this binary, on what machine, with what dependencies?” — the answer is one ledger query away.
Start free. Ten minutes to your first signed commit.
No credit card. No team size limit. Forever free to try. Upgrade when your team does.