Customer documentation software
Publish product documentation your customers actually read — branded, self-serve, and on your own domain. OpenDocs is built for customer-facing docs, not internal wikis.
Customer docs are a sales and retention channel
For most software products, the documentation is the most-visited page after pricing. Prospects read your docs before they buy to check whether your product does what they need. New customers read them during onboarding to get to their first success. Existing customers return to them every time they hit a wall. Treating that traffic as a cost center is a mistake — good customer-facing documentation is one of the highest-leverage assets you own.
Great product documentation for customers lets people help themselves. Self-serve onboarding means a customer can go from sign-up to value without waiting on a sales engineer or a support ticket, which lowers your cost to serve and raises activation at the same time. Every question a doc answers is a ticket your team never has to work, and every friction point it removes is a renewal you are more likely to keep.
Documentation is also an SEO surface. When your how-to guides and reference pages are public and indexable, they rank for the long-tail queries your customers type into search engines — and they pull in new prospects who are looking for exactly what you do. OpenDocs ships built-in SEO on every space (clean meta tags, an auto-generated sitemap, canonical URLs, and reader search) so your docs are discoverable from day one, not something you retrofit later.
Everything customer-facing docs need
A branded portal on your own domain
Publish to your own custom domain with your logo, colors, and a custom theme. Your documentation looks like part of your product, not a third-party wiki parked on someone else's subdomain. On Enterprise you can also drop the "Powered by" badge entirely.
Restricted spaces for private docs
Keep general product docs public and searchable, and put customer-specific or partner documentation in restricted spaces behind reader access control. Readers of public docs need no account; private docs stay private.
AI Write Assistant to draft faster
Draft new pages with the AI Write Assistant and tighten existing ones with the AI Writer Improver, right inside the block editor. No Markdown or git knowledge required to write — bring your own Anthropic API key and usage is billed to your account.
AI Translations for multi-market customers
Serve customers in every market by translating your docs into up to 38 languages. Translations stay in sync when you update the source, so your localized documentation never quietly drifts out of date behind the English original.
GitHub Sync when eng owns the truth
When product and engineering own the source of truth, two-way GitHub Sync keeps a space and a repo in lockstep. Writers use the visual editor, engineers use git and Markdown, and conflict detection flags anything changed on both sides with a side-by-side comparison.
Feedback & analytics on what customers read
Readers can leave page feedback on any doc, so you hear directly where they got stuck. On Enterprise, analytics and insights show which pages customers actually read — the data you need to decide what to fix and what to write next.
Your docs, readable by AI agents
Customers increasingly reach your documentation through an AI assistant rather than by opening your site. OpenDocs meets them there. Every published space is available through OpenDocs' MCP (Model Context Protocol) server, secured with an OpenDocs API key, so AI agents and your own support bots can read your live documentation directly.
The MCP server exposes tools like list_spaces, get_page_tree, get_page (full page content as plain text), and search_pages, over streamable HTTP, and works with any MCP-compatible client — Claude Desktop, Claude Code, and others. That means your published documentation doubles as a live, queryable knowledge source: no scraping, no stale exports, and no second copy to keep up to date. When you fix a doc, every AI assistant that reads it gets the fix immediately.
One product or a hundred — each gets its own branded space
OpenDocs is multi-tenant by design. If you ship several products, each one can get its own space with its own domain, theme, and navigation, so a customer never sees documentation for a product they do not use. If you serve documentation to distinct clients or partners, each of them can get their own branded portal too — the same platform, cleanly separated.
That structure keeps your customer documentation organized as you grow: one product line does not turn into a sprawling wiki where everything lives together. Spaces can be public for open product docs or restricted for customer-specific and partner content, and you manage all of them from one account.
Pricing that does not punish a big audience
OpenDocs uses flat tiers with members included, which matters for customer documentation because your readers vastly outnumber your writers. Pro is $55/month (or $45.65/month billed annually, $547.80/year) and includes 5 members, with extra members at $5/member/month monthly or $4/member/month annual. Enterprise is $99/month (or $82.50/month billed annually, $990/year) and includes 10 members, adding analytics and insights, PDF and Markdown export, API access and full API docs, SSO/SAML, audit logs, and priority support.
The people who read your published docs are never billed as seats — whether a hundred or a hundred thousand customers read your documentation, your bill is the same. You can start on a 14-day free trial with no credit card and all Pro features; after the trial, an account that is not upgraded keeps one space and one member.
Frequently asked questions
What is customer documentation?
Customer documentation is the product documentation you publish for the people who buy and use your product: getting-started guides, how-to articles, reference material, release notes, and FAQs. Unlike internal wikis, it is customer-facing, so it needs to be branded, searchable, easy to read, and discoverable in search engines. OpenDocs is built specifically for publishing this kind of documentation on your own domain.
How is customer documentation different from an internal wiki?
An internal wiki is written for your own team and lives behind a login. Customer-facing documentation is written for the people who use your product and usually needs to be public, branded as part of your product, indexed by search engines, and readable without an account. OpenDocs handles both: public spaces for open docs and restricted spaces for customer-specific or partner content, all on your own custom domain.
Can I publish customer documentation on my own domain?
Yes. Every OpenDocs space can be published to your own custom domain with your brand, colors, and custom theme, so your documentation looks like part of your product rather than a third-party wiki. Custom-domain publishing is available on Pro and Enterprise; the free trial lets you evaluate everything else first.
How do I translate customer documentation for multiple markets?
OpenDocs includes AI Translations that render your documentation in up to 38 languages and keep the translated pages in sync when you update the source. Translations run on your own Anthropic API key (BYOK), so usage is billed directly to your Anthropic account. It is available on every plan, which makes serving customers in multiple markets straightforward.
Can my customers' AI assistants read my documentation?
Yes. Every published space is available through OpenDocs' MCP (Model Context Protocol) server, secured with an OpenDocs API key. AI agents and support bots can call tools like search_pages and get_page to read your live documentation directly, with no scraping and no stale exports. It works with any MCP-compatible client, including Claude Desktop and Claude Code.
How much does customer documentation software cost?
OpenDocs uses flat tiers with members included. Pro is $55/month (or $45.65/month billed annually) with 5 members, and Enterprise is $99/month (or $82.50/month billed annually) with 10 members and analytics, exports, API access, SSO/SAML, and audit logs. Readers of your public documentation are never billed as seats, so a large customer audience does not raise your cost.