Your product changed.
Did your docs, website, and help center?
Track connects the repositories that change your product to the docs, website, and support content that explain it. When a pull request merges, Thally works out what changed for customers, finds every place that still says otherwise, and drafts evidence-backed updates for review.
No Thally account needed. Connect GitHub, and Track reads your last five merged pull requests in plain language.
Trusted by the AI tools your readers already use
feat: per-project webhook secrets
12 files changed · public surface: 2 endpoints, 1 config schema
docs: per-project webhook secrets
Opened by thally-bot · needs 1 review
guides/webhooks.mdx updated
api/projects.mdx updated
Changelog entry drafted
Impact analysis
Track maps the bounded change to affected knowledge.
Approve and merge
Human review before anything ships.
guides/webhooks.mdx
Confidence 0.94, backed by specific diffs.
guides/quickstart.mdx
Evidence says nothing to update here.
api/projects.mdx
Confidence 0.87, endpoint params changed.
Understand the change. Then trace it everywhere.
Connect your customer-facing surfaces
Docs, website, help center, and content repositories.
Start with your docs site, including pages, code samples, OpenAPI descriptions, and llms.txt. Then connect the other repositories where customers learn about your product.
Connect product repositories
Point Track at the code that defines your public surfaces.
Point Track at the code that defines your public surfaces: SDK exports, configuration schemas, CLI commands, and API operations.
You choose exactly which repos Thally can read
Analyze a merged change
Candidates across connected surfaces, with evidence, confidence, and a drafted diff.
For each merged pull request, Track works out what changed for users, searches every connected surface for pages that now contradict it, and presents candidates with evidence, confidence, and a drafted diff. A no-change result is valid.
Proof before prose.
Track inside Thally Cloud
How Track behaves, by design
A no-change result is valid. Thally never publishes to any surface without a human.
A repository is evidence about implementation, and documentation is evidence about communicated behaviour. Track surfaces candidates backed by specific diffs, and every draft is reviewed by a human before it ships.
Run Track on your repos right now.
Connect the repositories where your product changes, then connect the docs, website, and help center your customers read. Track reads your last five merged pull requests and explains what each one changed that your public content has not caught up with. Then it offers to draft the pull requests.
Connect GitHub
Connect your GitHub repositories
Install the Thally Labs GitHub App on the repositories you want to test: where your product changes, and where customers read about it. Thally reads only the repository contents, metadata, and pull requests you grant.
Already installed the Thally Labs app?