Documentation that people and AI can read
EvoHub Docs publishes your product and API documentation on your own domain. Write in Markdown, upload an OpenAPI file for the reference, and every site comes with search, llms.txt, a Markdown copy of every page and its own MCP server.
What is EvoHub Docs?
EvoHub Docs is a hosted documentation platform. You write pages in Markdown in the EvoHub console, publish them to a site on your own domain (docs.yourcompany.com), and the site is rendered as HTML at the edge with search, an OpenAPI reference, and machine-readable copies (llms.txt, llms-full.txt, .md pages, an MCP server) for AI tools.
Write in Markdown, publish when it's ready
Pages are Markdown with a toolbar and a live preview next to the editor. Organize them into sections, reorder the navigation, and publish page by page.
- Markdown editor with a side-by-side live preview
- Sections and pages, reordered from the navigation tree
- Drafts: editing a published page changes nothing live until you publish again
- Revision history on every publish — view any version and restore it into the draft
- Logo, brand colour and light/dark theme that follows each reader's system setting
Your own domain, with TLS handled
Every site lives on your own domain. Connect docs.yourcompany.com by adding two CNAME records; the certificate is issued and renewed for you. Until then, preview the site in the console.
- Your domain with automatic TLS — the console shows the records to add and their status
- Preview the whole site in the console before the domain is live
- Canonical URLs, sitemap, llms.txt and the MCP server all use your domain
- Logo upload (PNG, JPEG or WebP) and a brand colour used as the accent
Server-rendered at the edge, built for search engines
Pages are rendered as plain HTML on Cloudflare's edge, not assembled in the browser, so they load fast and every crawler sees the full text.
- HTML rendered at the edge, cached and refreshed within about a minute of a publish
- Keeps serving the last published copy if the EvoHub API is briefly unreachable
- sitemap.xml, robots.txt, canonical URLs and Open Graph tags per site
- schema.org TechArticle and BreadcrumbList on every page
- On-this-page headings, previous/next links and a mobile navigation drawer
Built-in search
Every site has search over all published pages and API operations — no search service to set up.
- Open with / or Cmd/Ctrl-K, navigate with the keyboard
- Matches titles, headings and body text, and links straight to the heading that matched
- API operations are searchable by summary, method and path
API reference from OpenAPI
Upload an OpenAPI 3.0 or 3.1 document in JSON or YAML. EvoHub validates it, lists every problem it finds, and publishes a reference with a page per endpoint.
- OpenAPI 3.0 and 3.1, JSON or YAML, validated on upload with readable error messages
- A page per operation: parameters, request body, every response and its headers
- Schemas shown as nested property lists, with recursive types handled
- A generated curl example for every endpoint
- Replace the file and publish when ready — readers keep the published version until then
Roles, review and docs-as-code
Give each site its own members and turn on review when changes should be approved before they go live. Keep the docs in a GitHub repository if your team prefers to write there.
- Site roles — owner, reviewer, editor, viewer — on top of your organization's permissions
- Optional review: changes go live through change requests with 1–3 required approvals, a diff and a private preview link
- GitHub sync in both directions: link a site to a folder of a branch and edit in the repository or in EvoHub
- Versions of a site (up to 20), each with its own pages, navigation and API references
- Translated pages in other languages, with a per-language status of what is still to translate
Analytics, feedback and private docs
See what readers look for and what they think of a page — without cookies — and decide who may read a site.
- Cookie-free analytics: page views, unique visitors, referrers, countries and devices, with CSV export
- Search analytics, including the searches that found nothing, and how AI tools read your docs
- Reader feedback: a was-this-helpful vote and an optional comment on each page, collected in the console
- Private sites behind a password, limited to your EvoHub organization, or signed in through your own login with a JWT
- Pages limited to reader groups, so one site can serve public and customer-only docs
AI-ready docs: llms.txt, Markdown and an MCP server
Every page as Markdown
Add .md to any page address — or ask with Accept: text/markdown — and get the page as clean Markdown, with links rewritten to the other pages' Markdown.
llms.txt and llms-full.txt
Each site publishes /llms.txt (an index of pages and API operations, per llmstxt.org) and /llms-full.txt (the whole site as one Markdown file).
An MCP server per site
Each site answers at /mcp. Claude, Cursor and VS Code can search your docs, read a page and look up an API operation through tools such as search_docs and get_api_operation.
Open in Claude or ChatGPT
A page menu lets readers copy the page, view it as Markdown, open it in Claude or ChatGPT, or copy the connection settings for their AI tool.
You decide on AI crawlers
One switch per site: allow AI crawlers such as GPTBot, ClaudeBot and PerplexityBot in robots.txt, or keep them out. Search engines are unaffected.
Structured data
schema.org markup on every page (TechArticle, BreadcrumbList, and WebSite with a search action on the home page) helps search engines and AI assistants understand the site.
Roles and review
Site members with their own roles (owner, reviewer, editor, viewer) and an optional review step: with it on, every change goes live through a change request — a diff, a private preview link, and 1–3 approvals before it is merged.
Pricing
2.5 EvoHub tokens per hour a docs site is published on your domain — about $27 a month. No per-seat fees for the people who write. See pricing.
Compare documentation platforms
Frequently asked questions
What is EvoHub Docs?
EvoHub Docs is a hosted documentation platform. You write pages in Markdown in the EvoHub console, publish them to a site on your own domain (docs.yourcompany.com), and the site is rendered as HTML at the edge with search, an OpenAPI reference, and machine-readable copies (llms.txt, llms-full.txt, .md pages, an MCP server) for AI tools.
Can I host my docs on my own domain?
Yes — that is where every site lives. Enter docs.yourcompany.com in the site's Domain settings and add the two CNAME records shown there; EvoHub issues and renews the TLS certificate. Until the domain is active you can preview the site in the console.
Does EvoHub Docs support llms.txt?
Yes. Every published site serves /llms.txt and /llms-full.txt automatically, and every page is available as Markdown by adding .md to its address. There is nothing to configure.
What is the MCP server for my docs?
Each site runs an MCP (Model Context Protocol) server at /mcp. Connect it to Claude, Cursor or VS Code and the assistant can search your docs, read pages and look up API operations directly instead of guessing from training data. It is read-only.
Can I publish an API reference?
Yes. Upload an OpenAPI 3.0 or 3.1 document (JSON or YAML, up to 2 MB). It is validated on upload and published as a reference with a page per operation, schemas, responses and a curl example. Pages and references share the site's navigation and search.
Can I keep AI crawlers away from my docs?
Yes. Each site has an "Allow AI crawlers" switch. When it is off, robots.txt tells AI crawlers such as GPTBot, ClaudeBot and PerplexityBot not to crawl the site; regular search engines are unaffected.
Is there Git sync, analytics or versioning?
Yes. Link a site to a folder of a GitHub repository through the EvoHub GitHub App and changes sync in both directions. A site can hold up to 20 versions, each with its own pages, and pages can be translated into other languages. Every site has first-party, cookie-free analytics — page views, unique visitors, referrers, countries, devices, searches (including the ones that found nothing) and AI-reader traffic — with CSV export, and readers can rate a page and leave a comment.
Can I keep my docs private?
Yes. A site can be public, behind a password, limited to members of your EvoHub organization, or signed in through your own login with a JWT. Single pages can also be limited to reader groups, so one site can hold public and customer-only docs.
How is Docs priced?
A published docs site is metered per hour it is live on your domain, at 2.5 EvoHub tokens an hour — about $27 a month for a site that is live all month. No per-seat fees, and every account gets 200 free EvoHub tokens each month. See the pricing page for how EvoHub billing works.
Start free — 200 EvoHub tokens every month. See pricing.
Last updated: · EvoHub is built and operated by EvoSync Teknoloji A.Ş.