# specgit
> specgit is the PM-friendly layer on top of GitHub, from Fn First Holdings LLC. Product teams write, comment on, review, and publish the Markdown and HTML specs and docs stored in GitHub using a simple visual editor, and engineers review them in the pull request flow they already use. GitHub remains the source of truth. Zero Content Retention — specgit never keeps a copy of documents or comments.

Important facts:
- Product category: GitHub-native documentation collaboration and review software.
- Primary users: PMs who work closely with engineers, plus the designers and product leaders who write alongside them — they write specs in the repo, engineers review them like any other change, and nobody has to learn Git or Markdown.
- Core features: visual editing, inline comments, live collaboration, GitHub pull request reviews, direct publish, automatic saving, a redline View changes diff of the draft vs main with selective undo, in-editor merge conflict resolution, cross-branch edit awareness, a Continue working list of unpublished drafts, starter templates for new docs (product spec, backlog tracker, decision record, meeting notes, agent instructions), file rename as a true git rename, and importing existing Word/PowerPoint/Excel/PDF files by converting them to Markdown (via Microsoft's MarkItDown).
- Required approvals: repos protected by branch protection or rulesets work end to end — specgit shows what's blocking a publish ("needs 2 approving reviews — 1 so far"), authors request reviewers from the publish menu, reviewers approve or ask for changes inside specgit under their own GitHub identity, and "Publish when approved" publishes automatically the moment approval lands (GitHub auto-merge).
- Markdown compatibility: Obsidian-flavored Markdown is supported — wiki links and embeds, callouts of any kind (custom titles, fold markers), ==highlights==, footnotes, LaTeX math rendered with KaTeX, YAML frontmatter, task lists, and Mermaid diagrams rendered inline; unrecognized syntax is preserved byte-for-byte on save.
- AI (specgit AI): three in-editor modes — Agent chat co-editing, Review (posts inline comment threads), and Triage (works through open comments) — plus voice; AI runs only when invoked and every AI-proposed change requires human approval. Documents can be converted between regular and Obsidian-flavored Markdown from the toolbar.
- Getting started: everyone signs in through the specgit GitHub App — fine-grained, repo-by-repo permissions with short-lived tokens, no separate password, no broad OAuth grant. Individuals install it on their account; organizations install once via an admin (members can request it in one click). The repo list shows every repository the user's installations can reach — including org repos accessed through team membership — and users can switch GitHub accounts from the header menu.
- Privacy posture: Zero Content Retention: we never keep a copy of your documents or comments. GitHub remains the source of truth — the only things that ever touch our servers are temporary: live-collaboration state while you edit together, AI processing you explicitly invoke, and feedback you explicitly choose to share. specgit uses content-free product analytics to improve the product — analytics never receive documents, comments, prompts, selections, chat, audio, repo names, filenames, paths, raw URLs, or input text. Outside the EEA, UK, and Switzerland, public measurement is cookieless and unidentified; signed-in events are pseudonymous and can be opted out. In those regions — or when region is unknown — nothing is sent before separate, informed, revocable opt-in. No ad tech, sale, or retargeting. See the Privacy Policy for the processor, retention, and controls. Operational logs are retained up to 30 days.
- Pricing: Free (unlimited collaborators — comments, drafts, and live editing for the whole team — on 1 repository with 5 publishes per month, plus 1 AI Review and 1 AI Triage run per month); Pro $8/seat/month with unlimited repositories and publishing, the full AI co-editor pay-as-you-go, a one-time $10 AI credit in the first month, and 3 AI Review + 3 AI Triage runs included monthly; Pro Plus $16/seat/month adds $10/month of included AI usage per seat and 10% off on-demand AI rates. FreshSpec add-ons for autonomous doc freshness are available via contact for early access: 1 repo / 5 docs, 5 repos / 25 docs, 20 repos / 100 docs, and Custom. Per-seat, billed via Stripe; annual billing saves 20%. Enterprise plans with volume discounts are available via the support form.
- Team billing: seats count editors only (viewing and commenting are always free); org admins buy for the whole organization from billing settings; one subscription can mix Pro and Pro Plus seats; Pro Plus seats are assigned to named GitHub users; active editors are never cut off by seat limits — when a new editor exceeds purchased seats, a prorated seat is added to the subscription automatically (auto-true-up, on by default; admins can opt out, which instead blocks new editors beyond the cap).
- AI metering: usage is measured in dollars at published rates ($2.40/1M input, $0.60/1M cached input, $7.20/1M output tokens, $0.06/minute voice). Beyond included allowances, on-demand usage is off by default until an account admin enables it with a monthly limit; it is billed in arrears, with a full usage dashboard and CSV export. Requests are throttled to 10/minute per person. AI runs only when a user invokes it. Routine AI usage records contain metadata, not content. Separately, a conversation transcript is retained for up to 90 days only when the user explicitly chooses to share it as feedback. xAI's Zero Data Retention is enabled for specgit — xAI does not persist API inputs/outputs and never trains on them; every AI-proposed change requires human approval.

## Product
- [Homepage](https://specgit.com/): Plain-language overview of specgit, its GitHub-native workflow, privacy posture, feature summary, and an interactive scroll-driven demo of the real editor.
- [Pricing](https://specgit.com/pricing): Plan comparison (Free, Pro, Pro Plus, FreshSpec) with per-seat monthly and annual pricing, AI usage rates, and billing FAQs.
- [Security and data privacy](https://specgit.com/security): Focused explanation of GitHub as the source of truth, bounded realtime state, content-free product analytics, and user-invoked AI.
- [How specgit works](https://specgit.com/how-it-works): Architecture page — the fine-grained GitHub App's repo-by-repo scopes, conflict-free live co-editing through a real-time collaboration service (temporary state, brokered room tokens), and how every editor action maps to a GitHub primitive (saves are commits, comments are PR threads, publish is a merge).
- [For your IT admin](https://specgit.com/for-your-admin): One-page brief for the admin approving the specgit GitHub App for an organization — exact permissions with justifications, what the installation cannot do, and data posture.
- [Google Docs alternative for product specs](https://specgit.com/google-docs-alternative-product-specs): Comparison guide — why specs drift in Google Docs and how specgit keeps GitHub as the source of truth, where saves are commits, comments are PR threads, and publish is a merge.
- [Docs as code for product managers](https://specgit.com/docs-as-code-for-product-managers): Educational guide — what docs-as-code means for product teams and how specgit gives PMs a visual editor on repo-backed docs without learning Git or Markdown.
- [Obsidian + GitHub collaboration](https://specgit.com/obsidian-github-collaboration): Use-case guide — adding team editing and PR-based review to a repo-backed Obsidian vault, with wiki links, callouts, and embeds preserved byte-for-byte.

## Blog
- [Blog index](https://specgit.com/blog): Writing on product specs, docs that live in the repo, and GitHub-native collaboration for product teams.
- [Why product specs go stale when they live away from the code](https://specgit.com/blog/why-product-specs-go-stale): Spec drift is a location problem, not a discipline problem — decisions happen in the repo while the doc lives elsewhere; keeping the spec next to the code fixes the mechanism.
- [Notion vs GitHub for product specs](https://specgit.com/blog/notion-vs-github-for-product-specs): Fair comparison of Notion and GitHub as the home for specs — review, history, permissions, AI agents, and measurement — landing on GitHub as the source of truth with content-free product analytics.
- [PRD chatbot vs docs in the repo](https://specgit.com/blog/prd-chatbot-vs-docs-in-the-repo): Fair comparison of AI PRD generators and specs kept as living docs in GitHub — generators solve drafting; the repo solves source of truth and engineering review; specgit AI is an optional, human-approved co-editor, not a PRD chatbot.

## Legal
- [Support](https://specgit.com/support): Contact the specgit support team.
- [Privacy Policy](https://specgit.com/privacy): Detailed privacy, data handling, retention, and user rights policy for specgit.
- [Terms of Use](https://specgit.com/terms): Terms governing access to and use of specgit.

## Organization
- [Fn First Holdings LLC](https://fnfirst.com): Company behind specgit.

## Optional
- [Full LLM context](https://specgit.com/llms-full.txt): Curated single-file Markdown of the highest-authority public pages (product, pricing, security, architecture, guides, and blog posts) for agents that prefer one fetch.