Your domain, your brand, your access rules
Custom domains, your branding, and single sign-on for private portals. The help site reads as part of your product, not a vendor page.
Publish help sites people actually use.
Documentation Portals turn approved content into public or private help sites for customers, staff, partners, and approved AI tools.
One portal at a glance: status, pages, versions, languages, readers, and the approval workflow it inherits.
API reference that stays true to the spec.
Every portal has a place for API specs. Register one, and the pages that follow it are rendered from the spec itself rather than copied by hand.
01
Import a spec
Register an OpenAPI spec with a portal version. Its endpoints, methods and sections are read from the spec.
02
Pages that follow the spec
Pages marked as auto-synced pull their content from the spec; when it changes, they re-render with the new endpoints, parameters and examples.
03
Drift, checked
The portal reports how many synced pages have drifted from the spec, and when it last checked.
Versions with a draft → active lifecycle
Draft the next version while the current one serves readers, then switch. Translations, including nine Indian languages, stay organized per version.
Readers include AI
Readers get search and Ask AI grounded in your approved content; approved AI tools read the same current pages through MCP.
From approved content to a useful help site.
The portal is not just a place to host pages. It is where guidance gets read, measured, improved, and reused by people and AI.
01
Publish docs, SOPs, training, or portal pages from the same workspace.
02
Organize pages by audience, version, language, and access rule.
03
Track reader behavior, search gaps, and page feedback.
04
Let approved AI tools read the same current content people see.
The specifics, stated plainly.
Publishing
- Custom domains and full branding
- Single sign-on for private portals
- Versions with a draft → active lifecycle
- Page editor, page tree, and navigation control
- Unlimited readers on every plan
Reach
- Translation, including nine Indian languages
- API reference with a try-it playground
- Ask AI for readers, grounded in approved content
- AI-readable through MCP with read and search tools
Signals & upkeep
- Reader analytics and search reports
- Page feedback and suggested fixes
- Automatic checks: links, translation freshness, doc health
- Spelling, grammar, and writing-style checks
Documentation Portal questions, answered.
What are Documentation Portals?
Documentation Portals are public or private help sites for customers, staff, partners, and approved AI tools. Each portal can have its own versions, branding, pages, and access rules.
Can portals use our own domain and branding?
Yes. Portals can use your own domain, logo, colors, fonts, and access settings.
Do portals show what readers need?
Yes. Portals can surface reader analytics, search patterns, page feedback, and suggested improvements.