Connected docs hosting for product and platform teams

Host docs portals that already understand your auth, tools, and release flow.

DevDocs turns documentation into an extension of your DevDocs.ai workspace with shared auth on mcp.devdocs.ai, branded portals, preview deployments, custom domains, and operator-visible lifecycle state.

1 MCP server3,000+ connectionsshared auth on mcp.devdocs.ai

Connected docs lifecycle

Shared auth to publish proof

Operator-visible
1A portal inherits workspace auth, orgs, and connected tools
2Every change opens a reviewable docs environment
3Operators inspect portal, preview, and domain lifecycle state
4Publish only after the evidence is clean

Preview every docs change

Every branch can get a reviewable docs URL, lightweight checks, and promotion evidence before it reaches a customer domain.

Share auth across every portal

Keep docs, operators, and connected tools on the same identity layer so org access and account context stay consistent.

Ship AI-ready docs surfaces

Publish docs that work for readers, agents, and search workflows with llms.txt, MCP-adjacent context, and structured delivery.

Built for docs operations

A public portal for readers. A real dashboard for operators.

The public site explains the hosted docs platform. The dashboard is the authenticated workspace for portals, previews, domains, org access, and lifecycle state.

Landing page

Explain the hosted docs product in terms of shared auth, preview proof, and AI-ready delivery.

Dashboard

Use a dense shadcn sidebar layout matching DevDocs.ai MCP.

Account menu

Keep the signed-in user in the sidebar footer with settings and workspace switching.

Lifecycle visibility

Render real portal lifecycle machines when the control-plane feed provides them.

Why teams move docs operations into DevDocs.

Keep the polished public docs experience, then add shared auth, connected tools, and governed release workflows around every portal.

Git-backed docs hosting with branded public portals
Preview proof and release checks before publish
Shared auth, org context, and connected tools across docs and operators
Lifecycle visibility for portals, domains, and running state machines