Guide
Published · 5 min read
Keep help center articles up to date
Find help-center articles affected by a product change, draft checkable corrections, review rollout timing, and verify the published result.
Product
Published · 5 min read
Compare Thally's Free, Cloud, and Enterprise plans, included sites and seats, AI credits, add-on costs, and self-hosting responsibilities.
Choosing a documentation plan starts with two counts: how many sites you need to publish, and how many people need to manage them. Thally's Free plan covers one managed site. Cloud adds team access, more sites, and automation. Enterprise covers requirements that need an agreed scope and contract.
These are the published USD prices as of November 10, 2026. Check the pricing page for current terms before buying.
Free: one managed documentation site
Free costs $0 and includes one managed site per workspace, pull-request previews, documentation analytics, and unlimited pages and readers. It suits a single owner publishing a product's first docs site.
The publishing engine serves HTML, Markdown, JSON, and JSON-LD. It also provides an MCP server and hybrid search. Custom domains, hosted AI answers, Track, and team access are paid features.
Your editable docs source stays in your Git repository. Keep the repository, assets, and configuration available so you can build and move the site yourself. Managed hosting still processes and serves your content; keeping source in Git is about ownership and portability.
Cloud: shared work and more capacity
Cloud costs $199 per workspace per month, or $1,990 billed annually. The annual total is $398 less than twelve monthly payments. A 7-day trial is available without a credit card.
Cloud includes:
- Three managed documentation sites and unlimited connected product repositories
- Five team members, with Owner, Editor, and Viewer roles
- 50,000 shared AI credits each month, with unused credits rolling over while the subscription remains active
- Hosted AI answers and chat, Track, documentation quality checks, and custom domains
For example, a team with a public API guide and a separate help center uses two of the three included sites. Readers do not use team seats. The five included members are the people managing the workspace.
What happens when you reach a limit
Additional managed sites cost $39 per month or $390 per year each. Additional active members or pending invitations cost $20 per month or $200 per year after the five included members.
A one-time $79 pack adds 10,000 AI credits. Packs do not automatically recharge. AI usage stops when the credit balance reaches zero, so review usage before relying on an AI workflow for a busy release.
Track analysis and drafting have different permissions
The public Track preview analyzes the last five merged pull requests against connected content. Its GitHub App uses read access for that analysis. A finding is a candidate to investigate, with a linked change to review.
Cloud's documentation automation can prepare update pull requests when the connected site and repositories have the required authorization. Your team reviews the proposed change before it lands. Installing the read-only preview app alone does not grant write access or publish a correction.
Enterprise: agree the scope before rollout
Enterprise uses a custom annual contract. Site, member, and AI allowances are agreed with each customer, along with security review, invoicing, support, and contract requirements. Assisted migration is scoped per source site.
Bring a concrete inventory to that conversation: the sites you run, the people who need access, your security requirements, and the content you plan to migrate. Test representative pages and redirects before committing to a cutover schedule.
Self-hosting the engine
The publishing engine is MIT-licensed and can be self-hosted, including for commercial use. This is useful when you want to manage the deployment or modify the engine. You take responsibility for hosting, upgrades, and operational checks.
Start by building your docs repository and testing a representative page, search, navigation, and any API reference. Check which Cloud services your site depends on before moving. An open-source publishing engine does not make every hosted service part of the self-hosted installation.
Pick a plan around the work you need to do
Use Free when one person needs one managed site. Evaluate Cloud when several people need to manage content, you need a custom domain, or you want change analysis and reviewed documentation updates. Discuss Enterprise when procurement, support, or capacity needs require an agreement.
If you already have docs, try the workflow with a small set of pages first. Preview an edit, check the published outputs, and confirm who can approve changes. That gives you a better basis for choosing a plan than a feature checklist alone.
Sources
Published under the Thally editorial policy. Technical conformance is defined in the agent-readiness methodology.
Build docs that stay close to your product.
Create a managed site, or use the open-source engine to run Thally yourself.
