Four tiers — from a single free repo to enterprise-scale. Each additional repo is a separate line item at the same rate.
Try it on one repo. Documentation builds as PRs merge.
The full product for teams that have validated the value.
Full platform depth for growing engineering organisations.
@syscribe/mcp, on roadmap)For organisations with compliance requirements or large repo footprints.
Extra commit packs are $45 for 25 PRs. At around 110 PRs a month, Pro pays for itself — and adds edit learning, gap analysis, and a bootstrap pass.
At 150 PRs a month you have hit the limit and commits queue. Business gives you 500 — plus unlimited seats, targets, and bootstrap passes.
Both modes are available on all pricing tiers.
Syscribe writes to your existing documentation platforms. You keep Notion, Mintlify, or Confluence exactly as it is. Low friction. No infrastructure migration. Best for teams with an existing documentation setup they like.
DefaultSyscribe hosts the documentation portal — custom domain, theming, built-in semantic search, auto-generated llms.txt. Same PR trigger, same approval workflow. Best for teams consolidating or starting fresh.
Included on all tiersSyscribe connects via a GitHub App you install on your organization or specific repositories. You configure a webhook that fires on pull_request.closed events. No SSH keys, no PATs, and no access to code outside the specific repositories you authorize.
Setup takes under 30 minutes. We walk through it in the onboarding call.
No. Syscribe only processes the diff from each merged PR — the specific lines added or removed. It does not clone your repository, does not store your full codebase, and does not read files outside the diff context needed to generate accurate documentation.
Diff content is processed in memory and not persisted beyond the documentation event. We are actively working toward SOC 2 Type II.
When a PR merges and drafts are ready, the configured reviewer receives an email with a direct link. The review screen shows all doc types for that PR in a tabbed view — one tab per documentation target.
Each tab shows the proposed update in context, a diff against the previous deployed version, and an approve/reject action. You can edit inline, instruct the AI to revise, or approve as-is. Nothing deploys until explicitly approved.
Yes. You define which sections Syscribe owns using comment markers (for Markdown) or explicit page assignments (for Notion and Confluence). Everything outside those boundaries is never touched — no risk of Syscribe overwriting content your team wrote by hand.
Rejected drafts stay in the queue with a "Needs revision" status. You can add a note explaining what was wrong, then either regenerate or edit manually. The rejection and any instructions you add become training signal — Syscribe learns from rejections just as it learns from approvals.
Most teams are fully set up within one business day. The steps are: install the GitHub App, connect your documentation targets (Notion, Mintlify, etc.), and do a 30-minute onboarding call where we configure the knowledge graph from your existing docs.
The first PR after setup triggers the first draft. From there, the system runs on its own.
Yes. The value Syscribe delivers scales with your PR volume and documentation surface area — not with how many people can log in. Add as many reviewers, contributors, and viewers as your team needs. You pay for connected repositories, not for headcount.
Pro is $149/repo/month ($119 annually). Business is $299/repo/month ($239 annually). Each additional repo at the same tier is a separate line item at the same rate.
We are onboarding a small number of engineering teams to help shape the product before general availability. Design partners get free access through the beta period, direct input on the roadmap, and a discounted rate when billing goes live.
In exchange: honest feedback, permission to reference your company name, and willingness to become a public reference if the product works for you. Email hello@syscribe.com to apply.
We're onboarding a small number of engineering teams to shape the product. Free access through beta. Direct influence on the roadmap. Discounted rate when billing goes live.
In exchange: honest feedback, permission to reference your company name, and a willingness to become a public reference if the product works.
Apply as a design partner