Your product documentation, written from your code and kept up to date in Notion
DeployIt creates a “📘 DeployIt” space in your Notion, writes your documentation from your repositories, and rewrites it every day as the code changes. Your own edits are kept and taken into account.
Free during early access. Unlimited repositories, no volume limit.
Three steps, about five minutes
Connect GitHub
Read-only, on the repositories you pick. Nothing is ever pushed to your code. Several repositories from the start — a product rarely lives in one.
Point at a Notion page
You choose which page hosts the space. DeployIt creates “📘 DeployIt” inside it and imports your last 30 days straight away, so you are not looking at an empty database.
It keeps itself current
Every night, DeployIt looks at what shipped, rewrites the pages the changes made inaccurate, and appends the day to the changelog.
Two things, deliberately kept apart
Documentation answers “how does this work today”. A changelog answers “what changed and when”. Merging them gives you a document nobody can read.
Living documentation
Pages that describe the product as it is now. When a feature changes, the page is rewritten — not appended to. That is what keeps it readable a year in.
Chronological changelog
A Notion database, one row per delivery, with the date, the type, who shipped it — humans and AI agents — and the estimated effort in dev-days. Append-only: it is the history.
What DeployIt will never do to your workspace
A tool with write access to your Notion has to be explicit about its limits. These are ours.
- It only writes inside the “📘 DeployIt” space it created. Nothing anywhere else in your workspace is ever read from or written to.
- It never silently overwrites your edits. Before rewriting a page it reads back what is actually there, and your version is what it starts from.
- It never deletes. A page that no longer has a subject is archived to your Notion trash, where you can restore it.
- Every page says who maintains it, when it was last updated, and which commits it came from.
- Disconnecting stops the writing and leaves everything in place. What DeployIt wrote is yours.
Questions people actually ask
What happens if I edit a page myself?
It is kept. The next update reads your version from Notion first and edits that, so your wording, your examples and your warnings survive. If a code change made one of your sentences factually wrong, DeployIt corrects the fact and keeps the sentence.
Does it touch my existing Notion documentation?
No. DeployIt only writes inside the space it creates. Your existing pages are never read from or written to — that boundary is what makes it safe to give a tool write access.
How often does it update?
Once a day, overnight. Not in real time: seeing a whole day at once produces one coherent rewrite instead of four partial ones, and it keeps the cost sane.
Is this a documentation website?
No. The documentation lives in your team’s own Notion, where your team already works. DeployIt does not host a public documentation site.
What does it cost?
It is free during early access — unlimited repositories, no volume limit. Paid plans start in January 2027, and anyone who joins before then keeps the founding-member price.
Which providers are supported?
GitHub, GitLab and Bitbucket for the code. Notion for the documentation and the changelog.