Everything you need to run gridtrue on your repo.
Install the CLI, connect to a network, validate locally, and plug gridtrue into the tools your team already uses. This is the user manual — not the engineering internals.
→ 28 pages · read in 30 minutes · updated with every release.
Getting started
Install the CLI, connect to a network, ship your first signed commit.
CLI
The gridtrue binary is the daily interface. Everything else is a read model on top of it.
Validation
Runtimes, manifests, and predicates — how the CLI turns a command into evidence.
Local development
The daemon, identity, and the common things that go wrong on a developer's machine.
Collaboration
Attestations, Conflict Radar, and the shared state that makes teams coordinate.
SDKs & integrations
Read attestations, query policy, and plug gridtrue into your app, CI, or IDE.
Overview
Pick the right integration for the job.
REST + SSE API
HTTP on api.gridtrue.io. JSON in, JSON out, SSE for live streams.
Go SDK
Typed access to the ledger from Go services and tools.
TypeScript SDK
Isomorphic client for Node, browsers and Svelte / React apps.
MCP server
Expose your gridtrue ledger to AI coding agents as structured context.
IDE extensions
Inline Conflict Radar and commit-state badges inside your editor.
Webhooks
Forward ledger events into the tools your team already uses.
Security & privacy
The guarantees gridtrue makes, and the ones it refuses to make.
Tiers
What changes between Free, Pro, Enterprise and Self-hosted — and what does not.
Reference
Dictionary and inventory. Things to look up, not read front to back.
Something missing?
The CLI itself is the authoritative reference for flags and exit codes — run gridtrue <verb> --help for the current release. For bugs, feature requests or questions, the community forum is the fastest path to an answer.