Documentation

One home for internal, public and API docs.

Write internal knowledge, public guides and API references in one editor. Publish on your own domain with your branding, and keep private pages private with permissions.

The problem it solves

What changes with Documentation.

Internal wikis, public help centers and API docs, written once and published on your domain.

  • Without Documentation: Internal wiki in one tool, help center in another, API docs in a third.

    With WrkOS Documentation: Internal, public and API docs live in one editor.

  • Without Documentation: Two people edit the same page and someone’s work is lost.

    With WrkOS Documentation: Real-time collaboration keeps every change.

  • Without Documentation: Public docs look like someone else’s website.

    With WrkOS Documentation: Docs publish on your domain, in your brand.

Features

What you can do with Documentation.

What each part does, what it looks like, and how it helps.

Internal wikis and playbooks

Write policies, playbooks and onboarding guides for the team, organized the way people look for them, with private pages kept private.

How it helps you

New hires and teams find answers on their own instead of asking in chat.

  • Internal wikis and playbooks
  • Permissions for private pages
  • Embeds for live context
01 · Documentation

Public help centers on your domain

Publish guides and help articles for customers from the same editor, on your custom domain or a subdirectory, with your logo and colors.

How it helps you

Customers get a help center that looks like your product, and your team doesn’t maintain a second tool.

  • Custom domain or subdirectory
  • Your logo and colors
  • Search-friendly publishing
02 · Documentation

API reference docs

Write API references with code samples right next to your product guides, structured so developers and search engines find the right page.

How it helps you

Developers get clear docs, and product and API documentation stay in step.

  • API reference pages
  • Code samples
  • Kept next to the product guides
03 · Documentation

Write together, see what’s read

Edit the same page at the same time without overwriting each other, and see which pages people actually read.

How it helps you

Docs stay accurate because updating them is easy, and you know where to spend effort.

  • Real-time collaboration without overwrites
  • Analytics on what gets read
  • Rich text editor with embeds
04 · Documentation

Use cases

Who uses Documentation, and how.

Product and engineering teams

Product guides and API docs in one place

Today
API docs and guides live in separate tools and drift apart.
With WrkOS
Both are written in one editor and publish together on your domain.

Founders and operations

A wiki the team actually uses

Today
Knowledge lives in chat threads and people’s heads.
With WrkOS
Policies and playbooks live in WrkOS, with permissions for what’s private.

Support teams

A help center on your own domain

Today
Your help center looks like someone else’s product.
With WrkOS
Articles publish under your domain and brand, from the same editor as internal docs.

How it works

Up and running in three steps.

  1. 1

    Structure the space

    Organize internal, public and API sections the way people look for them.

  2. 2

    Write together

    Edit at the same time in the rich text editor without losing a change.

  3. 3

    Publish where you want

    Custom domain or subdirectory, with analytics on what gets read.

From a customer
It’s much easier to use compared to Mintlify or GitBook. It has significantly streamlined our workflow.
Shriya GuptaFounder

FAQ

Questions, answered.

Something else? Talk to the team or email hello@wrkos.com.

Can I publish docs on my own domain?

Yes. Publish to a custom domain or a subdirectory with your logo and colors. Private pages stay private with permissions.

Can internal and public docs live in the same place?

Yes. Internal wikis, public help centers and API references are written in one editor, and permissions decide what’s published and who can see it.

How many pages can I create?

Personal includes 50 documentation pages and Core includes 300, including sub-pages. Enterprise limits are custom.

Can someone help us move from another docs tool?

Yes. WrkOS solution partners handle setup and migration. Ask for one when you book a demo.