Write once in a block editor. OpenDocs publishes it on your own domain and serves the same page to Claude through a built-in MCP server.
docs.northwind.example / publishing
Every space publishes to a custom domain on the Pro plan, with your own logo and colours. Readers never see an OpenDocs address unless you want them to.
Pages can be translated into 38 languages, and each language keeps its own URL so search engines index them separately.
Claude connects through the built-in MCP server. Each site also exposes llms.txt and a .md version of every page.
You write it once. OpenDocs does the formatting for each reader, human or machine.
Branded, fast, searchable. Password-protect a space when a doc is for customers only.
Claude searches and reads your published pages as a connector, and cites the page it used. Highlighted words in the excerpts show why each page matched.
A plain index that AI tools read first. Generated and kept current for you.
Add .md to any published page address and get clean Markdown. Good for agents, scripts and copy-paste.
Translate with Claude, review in the editor, publish each language on its own URL.
Pick a stage. Each one opens to show what it does.
Turn a finished space into 38 languages in one pass. Every translation stays editable, so a person has the last word.
Put the space on your own domain with your logo, colours and navigation. Public, or behind a password.
Create and update pages from any pipeline through the REST API, with API keys scoped to your workspace.
Developers document repos. HR teams publish handbooks. The editor is the same.
With the OpenDocs plugin for Claude Code, Claude reads your repository and writes the pages into OpenDocs as drafts. Nothing goes live until you say so.
Publish onboarding guides, policies and the employee handbook in a space restricted to your team. Translate it for offices in other countries, and every edit is kept in page history.
Readers search your docs, and the matching words are highlighted in the results. Claude can answer from the same pages and cite the one it used.
Keep standard operating procedures in a single space instead of scattered files. When the source of truth lives in GitHub, GitHub Sync pushes each approved change to the page.
Give each customer step-by-step guides at your own address, with your branding. Switch a space to restricted access while a rollout is still private.
Open a real OpenDocs portal and read it the way your team would.
Sample content for a fictional company.
The company is made up. The portals are real, published with OpenDocs.
See all the examplesEvery account opens with 14 days of Pro, no card. When the trial ends, your work stays.
Prefer email? Create an account. No credit card for the trial or the Free plan.
On day 15 you choose. Nothing disappears either way.
See it running: docs.p4software.cloud, the documentation for P4 Software’s own products, published on OpenDocs. Also listed in Claude’s connector directory.
Hosted on Microsoft Azure, which holds industry certifications such as ISO 27001 and SOC 2. These are Azure’s certifications, not OpenDocs’.
When Claude uses your docs, the reader gets the answer and the source, not a guess.
“Refunds are available for 14 days after purchase.”
Claude read that sentence on your refunds page, quoted it, and linked it.
# Northwind Docs > Product docs for Northwind. - /billing/refunds: Refund policy - /publishing: Publish your space
# Refunds Refunds are available for 14 days after purchase. Contact support from your account page.
