Skip to content
Thally
Log inGet started

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.

Run it on your reposSee how it works

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

ClaudeCursorCopilotPerplexityGeminiv0Windsurf
Mergedacme/api#517

feat: per-project webhook secrets

12 files changed · public surface: 2 endpoints, 1 config schema

HighDocs PR#292

docs: per-project webhook secrets

Opened by thally-bot · needs 1 review

guides/webhooks.mdx updated

api/projects.mdx updated

Changelog entry drafted

HighAnalysisT-101

Impact analysis

Track maps the bounded change to affected knowledge.

ReviewHumanT-204

Approve and merge

Human review before anything ships.

AffectedGuides

guides/webhooks.mdx

Confidence 0.94, backed by specific diffs.

No changeGuides

guides/quickstart.mdx

Evidence says nothing to update here.

MediumAPI

api/projects.mdx

Confidence 0.87, endpoint params changed.

Understand the change. Then trace it everywhere.

01Connect02Point03Analyze

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.

acme/docsindexing
guides/42 pages
api/openapi.yaml118 ops
llms.txt1 file
snippets/36 samples
Index progress78%

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.

acme/apiread-only
SDK exports24 symbols
Config schemas6 schemas
CLI commands11 commands
API operations118 routes

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.

guides/webhooks.mdx0.94
-Webhook secrets are shared.
+Each project has its own secret.
+Rotate secrets from Project Settings.
evidence: acme/api#517Awaiting review

Proof before prose.

The Track page in Thally Cloud showing setup progress and watched product repositories

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.

Track reads your last five merged pull requests and shows what your docs, website and help center have not caught up with.

No account needed. Read-only access. Nothing is written until you say so.

Run Track
  1. Connect
  2. Product repositories
  3. Surfaces
  4. Run
  5. Results

Connect GitHub

Connect the GitHub account that holds the repositories you want to test. Thally only reads them.

Thally Labs · GitHub App

  • Repository contentsread
  • Pull requests and merge eventsread
  • Repository metadataread

Pick the account that holds your product code and the docs, website or help center your customers read. You can connect more accounts after the run.

Already installed the app? Connect anyway. Thally finds the installation.

Read-only access. Nothing is written until you say so.

Works with the stack you already ship

GitHub
Vercel
Netlify
Cloudflare
Docker
Markdown