Private developer documentation

The right documentation for each reader.

SaturnDocs includes reader authentication, so one documentation site can serve the public, signed-in customers, and internal teams without exposing protected material.

The direct answer

What is private developer documentation?

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.

One site

Public, private, or mixed 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.

Public

Open guides and references for anyone evaluating or using the product.

Customer-only

Protected integrations, account workflows, and product material for signed-in customers.

Internal

Runbooks and technical procedures restricted to the people who operate the product.

Consistent enforcement

Access rules cover the page, search, and the answer.

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.

Included in the plan

How much does private developer documentation cost?

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.

Reader access questions

Frequently asked questions.

Can one documentation site contain public and private pages?

Yes. A SaturnDocs site can be public, private, or mixed. Public guides can remain open while customer-only or internal sections require sign-in.

Do protected pages appear in search or AI answers for unauthorized readers?

No. Reader access rules are enforced across page delivery, navigation, search, and AI answers. A reader only receives material that reader is allowed to see.

Which plans include reader authentication?

Reader authentication is part of both Standard and Enterprise. We scope any additional access, security, or organizational requirements with you.

Can we change access after launch?

Yes. Documentation access can change as products, customer groups, and internal needs change. SaturnDocs updates the access rules as part of operating the site.

Public and protected

Tell us which readers need to see which material.

Get your docs done
START HERE

Tell us what you build. We will show you your docs.

Send the context you already have. A repository, a spec, old docs, or a short walkthrough is enough.

Get your docs done

What are you building?

Tell us about your product and what documentation exists today. We reply within one business day.

Prefer email? hello@saturndocs.com reaches the same people.