specgit

• Headings, tables, images, code blocks, callouts, math, and Mermaid diagrams. Obsidian-flavored Markdown works, and any unrecognized formatting syntax is retained exactly as it was.
• Live co-editing with visible cursors, and inline comments that engineers can answer from GitHub without opening specgit.
• Branch protection and required reviews keep working. specgit shows what a change still needs, and reviewers approve inside the editor under their own GitHub identity.
• Optional AI: Agent chat edits with you, Review posts inline comments on a draft, and Triage works through open comments. It runs only when you ask, and a person approves every change it proposes.Why GitHub?

specgit could have stored your documents on its own servers like other solutions do, but we chose not to. GitHub is better for three reasons. The documents sit next to the code, so engineers and AI coding agents read them without being sent a link. Every edit is recorded with its author and full history, which is what makes review and auditing possible. And GitHub can publish: if the repository has a pipeline, merging a document pushes it live to a GitHub Pages site, a help center, a wiki, or a page inside your product. specgit doesn't render or host any of that; your pipeline does.

Why not a wiki or a shared drive?

If your team uses GitHub, your documents belong there too. Not just specs: handbooks, meeting notes, runbooks, decision records. A wiki, a workspace app, or a shared drive is a second system with its own accounts, permissions, and bill, and everything kept in it sits away from the code, invisible to the people and AI agents in the repository. specgit does the same job with one identity, one attributed history, and one review process, and when the repository publishes through GitHub Pages, the handbook ships the same way the spec does. If you pay for a separate document editor or wiki to get this, you can stop.

We respect your content

GitHub remains the source of truth for your content. specgit reads a file when you open it, writes your changes back as commits, and doesn't keep a copy of your documents or comments. The exceptions are narrow and disclosed: live-collaboration state is deleted after up to 7 inactive days, AI requests run under xAI Zero Data Retention for API inputs and outputs and never train models, and feedback is kept only if you choose to send it. Product analytics contain no document content. The privacy policy has the details.

Sign-in is the specgit GitHub App, installed once by an admin on the repositories you choose. Permissions are per-repository, tokens are short-lived, and there is no separate password. specgit runs on Microsoft Azure. Microsoft Entra ID is used once, at purchase, to activate the subscription. Everyone who edits needs a GitHub account, and readers need access to the repository. Try the editor on a sample document at specgit.com/try, no account needed.

Pricing

A seat is an editor; viewing and commenting are free for unlimited people. Microsoft bills the seats. Pro is $8 per seat per month: unlimited repositories and publishing, a one-time $10 AI credit in your first month, and 3 AI Review plus 3 AI Triage runs per person each month. Pro Plus is $16 per seat per month and includes $10 of AI usage per seat each month. Extra AI is not billed through Microsoft. If a month's allowance runs out, AI pauses until the next one, and Pro Plus is the plan with the bigger allowance. Annual billing saves 20%.

Pricing · Security · Support