From a code change to docs you approve.
Sabí reads what changed and writes it up. You check it and hit publish.
- 01
Your team merges a change.
Nothing new to learn. Sabí picks it up from GitHub.
- 02
Sabí writes it up.
For customers, your team and developers. Cleanups are skipped.
- 03
You check and publish.
It lands in your Notion.
What it works with.
It reads from GitHub and publishes to Notion today. Here's what's next, and when.
Four labels.
Only two need you.
Every page says whether it was checked, backed by the code, or needs a person.
Short answers.
What do the four labels mean?
Your team only looks at the last two.
Does this replace our wiki?
No. Sabí documents your product. Your wiki keeps team processes and meeting notes.
Do engineers have to do anything?
No extra work. Sabí reads the changes they already ship.
What does Sabí need from us?
Access to your GitHub and someone to review. For the beta product check, a test version of your product and a test login.
Will every small change become a page?
No. Sabí skips cleanups, renames and internal changes that change nothing for readers, and tells you why.
What happens when a page is wrong?
You catch it in review. Every update shows the old words, the new words and the code change behind them. Fix it, and your edit goes to review as a new version.
Who can see our code?
Each run analyses your code in a secured sandbox that's deleted when the run ends. See Security and trust.
How long until we see value?
In a demo call, you see pages for one area of your own product in thirty minutes.
What changes for my team?
Engineers: nothing. Product and support: a short review each week. Everyone else: docs they can trust.
