Notion documentation maintenance
Keep your Notion help docs aligned with every release.
Amendary checks every GitHub Release against the Notion help pages your customers rely on and drafts the exact corrections, with the release evidence attached to every change. On a paid plan, confident corrections go live automatically and anything uncertain waits for review. Undo is one click.
Free for 7 days, no card. 1 repo, 3 pages, daily checks. Subscribe to keep it running and to let it apply corrections automatically.
Example
Built for a specific team
Amendary does one job well. If your setup does not match, it is probably not the right tool yet.
A good fit
- B2B SaaS teams of roughly 5 to 50 people
- Docs that live in Notion, or as markdown in a GitHub docs folder or wiki
- A product that ships through GitHub Releases with release notes
- Nobody whose job is keeping the help pages current
Not a fit today
- Teams whose reference docs are generated from code (OpenAPI, docstrings): those need a build step, not a maintenance loop
- Enterprises with a docs team and a formal review workflow
- Internal wikis, engineering runbooks or API references as the main use
- Products with no change signal at all, no commits, releases or tags to check against
How it works
Connect and map
Install the GitHub App (read-only by default) and share your help pages with the Amendary Notion integration. Then map each page to the repo it describes. Only mapped pages are ever read or edited.
Every release is checked
When your repo ships a change, a GitHub Release, a tag, or commits on the branch you choose, Amendary reads what changed and checks each mapped page for a sentence it made wrong.
Corrections land with evidence
A confident correction with complete context is applied to the page and logged with the release behind it. Anything uncertain waits in your review queue. Undo is one click for 30 days.
What one correction looks like
ExampleA made-up release and page, laid out the way a correction appears in Amendary. It is not a customer case.
Release note line
v2.14.0: API rate limit raised from 60 to 120 requests per minute.
Why this page is affected
The help page “Rate limits” states the old limit. The release changes the number that sentence documents.
Current text on the page
Requests are limited to 60 per minute per API key.
Proposed correction
Requests are limited to 120 per minute per API key.
Evidence
Release v2.14.0, published 3 days ago. [link to the GitHub Release]
Complete context. Applied automatically and logged. Undo available in the queue for 30 days.
Guardrails and permissions
Read-only on your code by default
The GitHub App reads repository contents and metadata, and nothing else, until you opt a repo into writing docs to GitHub. It never changes your code, only docs, and only where you turn it on.
Explicit page mapping
Nothing is checked or edited until you map it. New pages arrive excluded. Unmapped and excluded pages are never read by the model.
Partial context waits for review
If a page or a release was too large to read in full, the correction is never applied on its own. It waits in the queue with a Partial context label.
Audit trail on every change
Each correction stores the release evidence, the model draft, the applied text and the exact text it replaced, in an append-only log.
Undo in Amendary
Undo restores the original text from the audit trail after checking the block has not been edited since. It is available in the queue for 30 days and does not depend on your Notion plan.
Review mode if you want it
Switch the workspace to review mode in Settings and every correction waits for a person before it touches a page.
The full account of what is stored, sent and deleted is on the Security page.
Coming soon
On the roadmapThe same release-driven loop is being extended to new kinds of documents, generated from your repo and releases and then kept current, not written once and left to rot:
On-call runbooks
How to start, stop, health-check and roll back, with the real commands.
Incident playbooks
Per failure mode: symptom, diagnosis, fix, verification, prevention.
Product updates
A dated changelog that grows as you ship: one page per day, entries appended, following your review mode.
See the full roadmap.
Start free, then pick a plan
Free for 7 days, no card: 1 repo, 3 mapped pages, daily checks, review-only so you approve every change. When the trial ends, scheduled checks pause and your dashboard stays. Subscribe to keep daily checks running and to let Amendary apply corrections automatically. Payments, VAT and invoices are handled by Polar as our merchant of record.
Starter
€49 per month
- Up to 2 repos
- 15 mapped pages
- Daily checks and automatic corrections
Team
€99 per month
- Up to 5 repos
- 50 mapped pages
- Daily checks and automatic corrections
Scale
€249 per month
- Up to 15 repos
- 150 mapped pages
- Daily checks and automatic corrections
Questions we get asked
- What if a correction is wrong?
- Undo it from the queue. Amendary checks the block has not been edited since, then restores the original text. You can also mark an applied correction as wrong with a short reason, which is recorded so you can track accuracy over time. Every change carries its release evidence, so you can see what it was based on.
- What does Amendary read?
- From GitHub: releases and release notes, and for code-change checks the changed files, all read-only. From Notion: only the pages you map. Page text is read for a check and not stored; the audit trail keeps the sentence that was replaced and the new text.
- Can I review everything before it goes live?
- Yes. Switch the workspace to review mode in Settings and every correction waits in the queue until someone applies it. In the default mode, confident corrections with complete context are applied automatically and everything else waits.
- What happens on Notion Free or Plus plans?
- Notion page history is shorter on those plans and is not something an integration can rely on. Amendary does not depend on it: undo uses the original text stored in the audit trail and works the same on every Notion plan.
- Is my code sent anywhere?
- Your code is never written to and raw diffs are never stored. To judge a change, Amendary sends the model the release notes or a change summary (for code-change checks, the diff itself) together with the mapped page text, through Anthropic's API. Anthropic does not train on data sent through its API. The Security page lists every subprocessor.
More in the Help Center.