Admin
Configures and governs the workspace.
- Manages members and roles
- Installs and manages the GitHub App
- Connects and disconnects repositories
- Reprocesses PRs when needed
AI-powered code documentation
You merge the PR. The docs are already done.
ClayDocs turns every merged Pull Request into plain-language documentation for PMs, QA, stakeholders and sales — plus a structured record the team can query in chat.
- Documents itself on every merge
- Clear language, no jargon
- Chat over your project history
Why ClayDocs
Code changes every week. Documentation almost never keeps up.
PRs with no context
Messy commits, empty descriptions, and the team only learns what changed by asking on Slack.
Docs only the author understands
PMs, QA, stakeholders and sales need plain language — what changed, why, user impact and how to test.
History that disappears
Decisions live in old PRs. New teammates and sellers cannot find answers without digging through GitHub.
Features
From merge to answer, with no manual work
An automatic documentation layer on top of your GitHub flow — without becoming a code-quality scanner.
Automatic docs on merge
On every merged PR, ClayDocs collects title, description, commits, reviews and the diff, then generates the doc in a single LLM call.
Docs for people
Four sections in Brazilian Portuguese: what was done, why it was done, user impact and how to test — step by step.
Product timeline
Browse documented PRs with type, modules, author and date — the product evolution thread in one place.
Chat over history
Ask in natural language. Counts and filters go through SQL; semantic questions use vector search. Every answer cites the source PRs.
Answers for the sales team
Sellers ask what the product already does, what shipped recently and what is still missing — with PR citations they can use in the sales conversation.
Modules from the code
Modules come from the folders of changed files. The LLM may refine them — it must not invent them.
Retroactive import
Pull the latest merged PRs from a repository so the team starts with context already in place.
How it works
From repository to question in four steps
- 1
Connect GitHub
Create the workspace, install the GitHub App and pick repositories. The creator becomes admin and invites the team.
- 2
Merge as usual
When a PR is merged, the webhook enqueues a job. The worker collects the data, calls the LLM once and stores the doc.
- 3
Read the timeline
PMs, QA, stakeholders and sales open the timeline or the PR page and understand the change without decoding the diff.
- 4
Ask in chat
“What changed in checkout this week?”, “Do we already support SSO?” or “How many bugfixes did Ana ship in March?” — with PR citations.
Pricing
From indie to enterprise, at your pace
Start on Dev with self-serve. When the company needs a contract, SSO and a partner, move up to Enterprise.
Dev
For small teams that want frictionless PR documentation.
$15/month per workspaceor $140 per year (22% off)14 days free to start
- Connected GitHub repositories
- Unlimited readers, no per-seat cost
- Automatic docs on every merged PR
- Chat over your project history
- Retroactive PR import
- Email support
Enterprise
For companies that need a contract, governance and a partner.
Let's talkAssisted billing and onboarding
- Everything in Dev, with agreed limits
- SSO and provisioning (as agreed)
- SLA and priority channels
- Contract, invoicing and procurement
- Dedicated customer success
The 14-day trial starts when you connect your first repository. Billed per workspace, with unlimited readers.
Roles
Two roles, clear permissions
No complicated hierarchies: admins configure the workspace; members read the docs and use chat.
Member
Follows the product and asks questions.
- Sees the timeline of documented PRs
- Opens each PR page
- Uses the workspace chat
- Reads generated docs in Portuguese
Integrations
Wired to GitHub, built for the whole team
Install the GitHub App on the workspace, pick repositories and let every merge produce documentation. Built for people who write code — and for PMs, QA, stakeholders and sales who need to understand it.
- Dev
- PM
- QA
- Stakeholder
- Sales
GitHub App
Per-workspace installation with a repository scope you control. Only merged PRs are processed.
One LLM call per PR
Generates the human doc and the structured record together, with validated output. No code-quality analysis.
Chat with tools
Quantitative questions via SQL; semantic search with embeddings. Always scoped to your workspace.
FAQ
What teams ask before getting started
Does ClayDocs analyze or review my code?
No. It documents merged PRs. There is no quality scanner, compliance engine or automated review — just useful documentation and chat over history.
Does it work with GitLab or Bitbucket?
In the MVP, only GitHub — via the GitHub App and pull request webhook. Other providers are out of scope for now.
Can I edit the generated documentation?
Not right now. Docs are generated automatically from the PR. Manual editing is out of the MVP.
Which roles exist in a workspace?
Only two: admin and member. Whoever creates the workspace becomes admin. Admins manage members, GitHub and repositories; members see the timeline, PR pages and chat. Job function (dev, PM, QA, stakeholder) is informative only.
Which languages is the interface available in?
Portuguese (Brazil) and English in the UI. LLM-generated content (human doc, technical summary, how to test) is always in Brazilian Portuguese.
How do the Dev and Enterprise plans work?
Dev is self-serve: the admin starts a 14-day trial in Stripe Checkout when connecting the first repository, and billing (monthly or annual, in BRL or USD) starts when the trial ends. Readers are unlimited — PMs, QA and sales don’t pay per seat. Enterprise is closed with our sales team, with contract, limits and invoicing agreed upon.
Let's talk
See ClayDocs with your own repository
Tell us how the team tracks what shipped today. We'll show how every merge becomes clear documentation and a chat that answers from your history.