Public
Open guides and references for anyone evaluating or using the product.
SaturnDocs includes reader authentication, so one documentation site can serve the public, signed-in customers, and internal teams without exposing protected material.
Private developer documentation is technical content that only approved readers can access, such as customer integration guides, partner APIs, beta documentation, or internal runbooks. SaturnDocs includes reader authentication and applies each reader’s access rules to pages, navigation, search results, and AI-generated answers.
The access model is part of the site rather than a separate portal. Approved readers keep the same search, reference, and assistant experience as readers of public documentation.
A SaturnDocs site can be fully public, fully protected, or divided by audience. Public onboarding pages can remain indexable while customer-only integrations and internal operational material require authentication. You decide who belongs in each audience; SaturnDocs configures and operates the access rules.
Open guides and references for anyone evaluating or using the product.
Protected integrations, account workflows, and product material for signed-in customers.
Runbooks and technical procedures restricted to the people who operate the product.
Protecting a page is incomplete if its title appears in navigation, its text leaks into search, or an AI assistant quotes it to the wrong reader. SaturnDocs carries the same reader permissions through every surface so unauthorized material stays absent rather than merely difficult to open.
This fail-closed behavior means a configuration problem refuses access instead of serving a private page publicly. The visible documentation experience and the machine-readable experience follow the same boundary.
Reader authentication is part of both Standard and Enterprise. The platform also includes the site, hosting, search, interactive API reference, and cited AI assistant. AI agents perform the writing and ongoing updates. We scope additional access, security, and organizational requirements with you.
See the complete SaturnDocs pricing and subscription terms, or compare the access model with Mintlify and GitBook.
Yes. A SaturnDocs site can be public, private, or mixed. Public guides can remain open while customer-only or internal sections require sign-in.
Reader authentication is part of both Standard and Enterprise. We scope any additional access, security, or organizational requirements with you.
Yes. Documentation access can change as products, customer groups, and internal needs change. SaturnDocs updates the access rules as part of operating the site.