Beta Docs that design themselves

Other tools render docs. We design them.

Docklin turns the shape of your code into a documentation workspace that feels clear, composed, and ready to be used.

See how it works
No credit card. Bring your repository.
app.docklin.dev / atlas / overview
v 1.4.0
Introduction

Build with clarity.

Everything you need to build thoughtful integrations with the Atlas API.

A considered starting point
const atlas = new Atlas({
  key: 'your_api_key',
  version: '2024-04-01'
});
Your first request
A quiet layer behind ambitious teams
Repository-aware by default

Your codebase is the starting point.

Connect a repository and Docklin traces the paths between routes, concepts, and the people reading your docs.

acme / atlas-apiPublic repository · mainReady to scan
openapi.yaml18 routes
/src/routes/checkout.tsupdated 2m ago
#README.md6 pages found
How it works / 01

From blank page to complete docs.

Documentation should start with the shape of your product, not a blinking cursor.

01 — Plan

See the whole picture.

Docklin maps your codebase and finds the stories your users need to follow.

02 — Purpose

Give every page a job.

Turn endpoints, concepts, and edge cases into a calm, navigable system with a point of view.

03 — Fill

Make it unmistakably yours.

Bring in your voice and examples. Docklin handles the structure, so you can focus on the signal.

The difference / 02

Messy code / Beautiful docs.

Structure is not decoration. It is how your best work gets understood.

BeforeUntitled.md
## API Reference
// TODO: explain auth
POST /v1/checkout
response: 200 ??
see internal notes
AfterDocklin / Checkout
Concept / Checkout

Make every payment
feel considered.

Accept secure payments with one clear request. Start with a session, then let Atlas handle the rest.

POST /v1/checkout2 min read
Built for the loop

A better path from commit to publish.

npx docklin sync
01
Repository synced8f31c2a · 14 pages updated
02
Preview ready3 broken links fixed automatically
Publishedatlas.docklin.dev · 2 mins ago
A better default

For teams who care how their work is experienced.

We stopped treating docs like a release checklist. Docklin gave our product a front door.
LMLeah Morgan
Product engineering, Northstar
Common questions

Before you start.

Everything teams usually ask before connecting a repository.

Does Docklin write the docs for me?

Docklin drafts structure and first-pass copy from your codebase, but it's built for you to shape — bring your own voice and examples on top of what it generates.

What can it read from my repository?

Docklin reads route definitions, OpenAPI specs, and README files to trace the paths between routes, concepts, and the people reading your docs. It never needs write access to scan.

Can I self-host or keep docs private?

Yes. Publish to a private subdomain restricted to your team, or export the generated pages to host wherever your product already lives.

What happens after the beta?

Beta workspaces stay free while we build. We'll give every team notice and a fair path to a paid plan before anything changes.

The future of documentation

Let the work speak clearly.

Join the teams building a better way to explain what they make.

building.sh