The process

How it starts.

No onboarding project, no migration, no blank workspace waiting for you. You send what exists, and the work comes back done.

From handover to maintenance

How does SaturnDocs build and maintain developer documentation?

SaturnDocs starts with the product material you already have. AI agents turn it into guides and an interactive API reference, you review the draft, and SaturnDocs publishes it on your domain. After launch, the agents follow releases, update pages, and fix anything you flag.

Step 01 · The hand-over

Send what you have. It is already enough.

A repository, an OpenAPI spec, an old docs site, scattered notes, or an hour on a call. You do not clean anything up first; turning that material into documentation is what the agents do. Most teams spend about fifteen minutes here.

The hand-over
SEND github.com/yourcompany/api received
SEND openapi.yaml · old-docs.zip · notes.md enough
Step 02 · The build

AI agents read everything and write your site.

The agents read the code, the spec, and every note, then structure it all into clear guides, a quickstart, and an interactive API reference, in your brand and on your domain. Your first draft is ready within 24 hours.

Build log
READ 214 files · 1 spec · 3 old pages done
WRITE guides · quickstart · API reference drafted
Step 03 · The review

You read the draft. The agents fix what you flag.

You review the site like a reader, not like an editor. Anything wrong, missing, or off tone, you flag in plain language and the agents rewrite it. No document handoffs and no tracked changes.

The review
YOU "The auth guide shows the old flow." flagged
DOCS auth guide rewritten from current code fixed
Step 04 · The launch

Your docs go live on your domain.

Search, the AI assistant, llms.txt, and reader authentication are already wired in. You add one DNS record to put the site on your domain; we send you the exact record, handle hosting and TLS, and then you send people the link.

The launch
DNS docs · CNAME · yourcompany.saturndocs.com you add this
GET docs.yourcompany.com 200 OK

From then on, it stays done.

Ship a release and the docs catch up. Spot something off and the agents fix it. The four steps above happen once; ongoing agent maintenance is included in your plan.

Frequently asked questions.

How much of our time does it take?

About fifteen minutes to hand things over, and however long you want to spend reviewing the draft. The one technical step on your side is adding a single DNS record so the docs live on your domain; we send you the exact record to add.

What if we barely have any docs?

Code and a conversation are enough. Products with no docs at all are some of our favorite starts, because there is nothing to untangle.

Do we have to migrate anything?

No. Send links to what exists and the agents handle the moving, restructuring, and rewriting.

What happens after launch?

We watch your releases and changelogs and keep the docs current. You can flag anything at any time, and you can always edit the plain files yourself.

Your docs are waiting

One hand-over is the whole project.

Everything after that is handled by the agents.

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.