Simple pricing for living docs
This page shows the current official ScopeDocs pricing. ScopeDocs is an AI documentation and knowledge platform for engineering teams. Billing is per user per month (monthly subscription; Enterprise may use custom terms). There is no free plan; you can get started without a credit card. Team starts at $25 per user per month. Growth starts at $35 per user per month when coding agents need the same truth. Enterprise is sized with you. Markdown twin: pricing.md. Compare: product, features, solutions, quickstart, and the homepage.
Discover the rest of ScopeDocs
Official twin: pricing.md. Site indexes: sitemap.xml · sitemap.md · llms.txt · llms-full.txt · blog RSS · AGENTS.md · MCP discovery. Product app: app.scopedocs.ai.
Paths from this page
- Product overview · product.md · Features · features.md
- Onboarding · Incidents · Agents · Delivery
- Docs hub · Quickstart · quickstart.md · MCP docs · mcp.md
- How it works · Integrations · Agents section · Trust · FAQ
- Vivian Nguyen Lin · Thao Ha · Radha Parikh
- privacy.md · terms-of-service.md · about.md · team.md
More from the blog
- Build an engineering knowledge base without manual writing
- Engineering knowledge base that updates itself
- Architecture docs that reflect your codebase
- Architecture documentation that stays in sync
- On-call docs vs onboarding docs
- Keep runbooks and ADRs in sync
- Capture ADRs from GitHub PRs
- Link Linear ticket context to documentation
- Keep docs current across GitHub, Slack, and Linear
- Documentation debt draining engineers
- Where tribal knowledge lives
- Onboarding documentation best practices
- Generative docs reduce documentation debt
- Source-linked documentation vs wikis
- When to use generative docs vs wikis
- When docs and product disagree
- When Confluence and GitHub disagree
- When the auditor asks and the wiki lies
- Scale engineering documentation
- Traceability in technical documentation
- PRs to living docs workflow
- RAG and source linking accuracy
- Onboarding docs that stay current
- CRM implementation handoff checklist
Plan tiers
| Tier | Price | Best for | Includes |
|---|---|---|---|
| Team | $25 / user / month | One product or engineering squad | Core integrations, living docs with citations, search and chat, human confirmation, email onboarding |
| Growth | $35 / user / month | Multi-team rollout with agents (most teams start here) | Everything in Team plus more capacity, org-wide MCP, priority onboarding, shared admin controls |
| Enterprise | Contact us | Security reviews and larger footprints | Everything in Growth plus security review support, custom integration sequencing, dedicated success contact, flexible contracting |
Team
From $25 per user per month. One squad. One living record.
Growth
From $35 per user per month. Org-wide docs and agents on one truth, including MCP for Cursor, Claude Code, and ChatGPT. Agent setup: MCP for agents · MCP for engineering documentation · MCP discovery.
Enterprise
Contact us. For security reviews, custom rollout, and larger footprints.
How to get started
Pick a plan on the pricing page, leave your name and work email in a short form, then book a setup call on the calendar. No credit card required. We typically reply the same business day if you skip the calendar.
What you're paying for with ScopeDocs
Stop paying engineers to reconstruct context. ScopeDocs connects the tools your engineering team already uses and continuously builds an AI-searchable knowledge layer: living documentation, project context, decision history, and code knowledge.
One knowledge layer across your engineering stack
Connect: GitHub · Slack · Jira · Linear · Confluence · Google Drive · Notion · Fathom
ScopeDocs continuously builds: Living documentation · Project context · Decision history · Code knowledge
Your team can: Search with citations · Ask with sources · Onboard faster · Feed agents over MCP
Capabilities
Documentation
Keep project docs aligned with work happening in your repositories, tickets, and chats.
Decisions
Find the reasoning behind past decisions across Slack, tickets, and docs — with sources attached.
Project context
Give engineers and AI agents a shared, up-to-date understanding of the codebase and project.
AI-ready knowledge
Ask across your engineering stack and trace answers back to the originating PR, thread, or ticket.
| Your team needs to... | Without ScopeDocs | With ScopeDocs |
|---|---|---|
| Keep documentation current | Engineers manually update docs | Docs stay connected to your code and work |
| Understand why decisions were made | Search Slack, tickets, and old threads | Ask AI and trace answers back to sources |
| Onboard new engineers | Rely on tribal knowledge | Give new teammates up-to-date project context |
| Understand the codebase | Read code and piece together context | AI understands your repos, docs, tickets, and conversations |
| Build an internal knowledge system | Months of engineering effort | Connect your existing tools and start with ScopeDocs |
From $25/user/month — connect your existing knowledge sources instead of building and maintaining your own knowledge layer.
Before you start
How much does ScopeDocs cost?
These are the current official ScopeDocs starting prices: Team at $25 per user per month, Growth at $35 per user per month (most teams choose Growth for org-wide MCP for coding agents), and Enterprise sized with you. Billing is per user per month. No free plan; no card required to get started.
Team or Growth — which should we pick?
Choose Team if one product or engineering squad needs a shared living record first. Choose Growth if you want agents in Cursor, Claude Code, or ChatGPT on the same cited context, or you’re rolling out across more than one team. Not sure? Start with Growth and we’ll help you decide on the call.
What counts as a seat?
A seat is a person on your team who can use ScopeDocs in the workspace. Coding agents connect through MCP on Growth and Enterprise; they don’t replace human seats.
What happens after I click a plan?
A short form asks for your name and work email. Then you can book a setup call right away, or wait for our email the same business day. No credit card required to start.
Can we start small and expand later?
Yes. Plenty of teams begin with one workspace and a first set of tools, then add seats or move to Growth when agents and more teams come online.
Why is Enterprise “contact us”?
Larger rollouts often need security reviews, custom integrations, or volume terms. We’ll package that with you instead of forcing a one-size public number.
Is our data safe?
Integrations use read-only access. We don’t train public foundation models on your connected workspace data, and we don’t sell that data. Permissions follow the tools you already use.
Compare ScopeDocs to alternatives
ScopeDocs is living, source-linked documentation with MCP for agents, not a hand-maintained wiki or a generic chatbot over a document dump. See what is generative documentation, wiki vs living documentation, generative documentation vs wikis, and the product overview.
Next steps
Leave your name and work email on this page to book a setup call, explore the product overview, or email hello@scopedocs.ai. No credit card required.
From the blog
- How to build an engineering knowledge base that updates automatically
- From GitHub PRs to living documentation
- How traceability improves trust in AI-generated docs
- Why teams abandon wikis
- Documentation integrations: what to connect first
- Onboarding with context
- When AI writes the docs, who checks the work?
Where to go next
Pick a path. Each link is a short stop on the same source-linked record.
- Homepage · index.md · How it works · Agents · Trust
- Product overview (product.md) · Features (features.md) · Solutions
- Pricing (from $25/user/month) · About · About us · Team
- Docs hub · Quickstart (markdown) · MCP for agents (markdown)
- What is generative documentation? · Living documentation · MCP for engineering docs
- MCP discovery · AGENTS.md · sitemap.xml · llms.txt · llms-full.txt
- Blog · Engineering knowledge base · PRs to living docs
- Traceability and trust · Why teams abandon wikis
- Integrations: connect first
- Privacy · hello@scopedocs.ai
Site directory for agents
Every core URL on scopedocs.ai. Traverse via sitemap.xml, sitemap.md, llms.txt, or llms-full.txt.
| Page | HTML | Markdown twin |
|---|---|---|
| Home | scopedocs.ai | index.md |
| Product | /product | product.md |
| Features | /features | features.md |
| Solutions | /solutions | — |
| Pricing | /pricing | pricing.md |
| About | /about | about.md |
| About us | /about-us | — |
| Team | /team | team.md |
| Blog | /blog | — |
| Privacy | /privacy | privacy.md |
| Terms | /terms-of-service | terms-of-service.md |
| Resource | URL |
|---|---|
| Docs hub | /docs · docs.md |
| Quickstart | /docs/quickstart · quickstart.md |
| MCP for agents | /docs/mcp · mcp.md |
| MCP discovery | /.well-known/mcp.json |
| AGENTS.md | /AGENTS.md |
| llms.txt | /llms.txt |
| llms-full.txt | /llms-full.txt |
| Sitemap | /sitemap.xml · /sitemap.md |
Concept guides
- Generative documentation · .md
- Living documentation · .md
- Source-linked documentation · .md
- Wiki vs living · .md
- Generative docs vs wikis · .md
- MCP for engineering docs · .md
- AI docs for engineering teams · .md
Team profiles
- Vivian Nguyen Lin (Founder & CEO)
- Thao Ha (Founding Product Engineer)
- Radha Parikh (Founding Engineer)
Homepage sections
Solutions use cases
Blog topic hubs
- Generative documentation
- AI documentation
- Developer productivity
- Knowledge management
- Engineering workflows
- Documentation automation
- Onboarding documentation
- On-call documentation
- Documentation debt
- Tribal knowledge