ilumd

For product teams · One repo, every audience

One repo. Your developer docs, help centre, and team wiki.

Your team already writes the docs in Markdown. ilumd publishes each one to the right people — customers, developers, or just your team — and flags it when the code moves on.

Start free trial See pricing

Thirty days free, no card. Every reader free.

We never move your docs — edits come back as pull requests.

Step one · Discover

Connect your repo. Every doc your team has written comes into view.

API reference, guides, runbooks, onboarding notes — ilumd finds every Markdown file, including the ones nobody remembers writing. The repo stays the source of truth; ilumd keeps a synced copy to serve and search them.

One search across all of your product's docs, scoped to what each person may see.

Two minutes to connect. Nothing to migrate.

Sources · GitHub · GitLab

Inventory · 6 documentsquickstart.mdquickstart.mdapi-keys.mdapi-keys.mdrate-limits.mdrate-limits.mdsso-setup.mdsso-setup.mdincident-runbook.mdincident-runbook.mdroadmap-internal.mdroadmap-internal.md

Step two · Choose who sees it

Public, customer, and team docs, from one repo.

Every doc starts private. Publish your developer docs to the world, put customer guides behind sign-in, keep internal notes for your team, and share early docs with beta testers. Each audience sees only what’s shared with it.

Your docs site, help centre, and wiki stop being three tools.

Who should see the SSO setup guide? Pick one, or several.

Lit for Customers and Beta testers. Not visible to anyone else.

Your teamGuide not shared hereYour teamSSO setup guideCustomers, signed inGuide not shared hereCustomers, signed inSSO setup guideDeveloper docs (public)Guide not shared hereDeveloper docs (public)SSO setup guideBeta testersGuide not shared hereBeta testersSSO setup guide

Step three · Keep up with releases

You ship. The docs keep up.

Every doc carries a freshness rating from its last edit and how recently the code it relates to has changed. When a release moves the code on and the doc doesn’t, ilumd flags it and links the change, so someone re-checks it before a customer finds the gap.

No more “the docs say v2, the app says v3”.

Customers read docs that match the product they're using.

Rate limits

docs/api/rate-limits.md

FreshAging · 1 commit sinceStale · code changed sinceVerified · checked today
Freshness
This doc
Code it describes
2 Mar11 Mar19 Martoday

Edited 2 Mar. Nothing has changed beside it since.

The code moved on 11 Mar. The doc didn’t.

Flagged. Re-check requested from JL.

JL confirmed it’s right. Verified today.

Step four · Fix it with a pull request

Anyone can suggest a fix. Your review still decides.

  1. 1Customer spots an error1 / 5

    Help centre

    Retries run every 30s

  2. 2Suggests an edit2 / 5

    - retry every 30s

    + retry every 60s

  3. 3ilumd opens a PR3 / 5

    #482

    ilumd/webhooks-retry-interval

  4. 4Your team reviews4 / 5

    JLapproved

    merged to main

  5. 5Portal updates5 / 5

    Help centre

    Retries run every 60s

Integrations

Works with the tools your team already uses.

ilumd finds your docs in GitHub and GitLab. A reader’s request for an update becomes an issue in GitHub, GitLab, Jira, or Linear. Copies in Notion or Confluence are updated automatically, so they don’t go stale, and the right people hear about changes by email.

Find docs in

GitHubGitLab

Every Markdown file in your repos.

ilumd

Raise issues in

GitHub IssuesGitLab IssuesJiraLinear

Keep in sync

NotionConfluence

Updated automatically from ilumd.

Notify by

EmailSlacknext

Step five · Ask your docs

Customers ask. Your docs answer.

Customers ask in plain words in your help centre and get a cited answer from the docs they’re allowed to see. Internal notes and beta docs stay out of it.

Support can point to the same answer instead of writing it again.

Included on every workspace.

How do I rotate an API key without downtime?

Answering from 4 documents this person can see18 excluded
Create a second key and deploy it alongside the first. Both keys work during the overlap, so once your services use the new one you can revoke the old key with no failed requests.
API keysRotating keysRate limitsQuickstart
Knowledge base · 22 docs can see not shared with them
  • Internal · incident runbook
  • Beta · billing API v3
  • Internal · on-call rota
  • API keys
  • ADR-021 · key storage
  • Internal · pricing model
  • Beta · webhooks v2
  • Internal · release checklist
  • Rotating keys
  • ADR-018 · auth service
  • Internal · postmortems
  • Beta · usage dashboard
  • Internal · support macros
  • Rate limits
  • ADR-024 · rate limiter
  • Internal · roadmap
  • Beta · SSO for teams
  • Internal · security review
  • Internal · deploy guide
  • Quickstart
  • ADR-019 · queue choice
  • Beta · audit log export

Pricing

$29 for your product. Every reader free.

One product is one workspace: your developer docs, help centre, and team docs together, each doc shown only to who you choose. Not per seat, not per doc, and never per reader — customers, developers, and your team all read free.

Growing team? Your first 10 editors are included, and readers stay free however many customers you have.

Start free trial See full pricing

30-day trial · no card

  • Your team

    read free

  • Customers

    read free

  • Developers

    read free

Straight answers

For product teams.

How many workspaces does a product need?

One. Your public developer docs, your signed-in customer help centre, and your team's internal docs all live in the same workspace, and each doc is shown only to the audience you choose.

Do our docs have to move?

No. They stay as Markdown in your GitHub or GitLab repo, versioned in Git. ilumd keeps a synced copy to serve and search them, and edits come back to the repo as pull requests.

What do customers and readers cost?

Nothing, however many there are. You pay $29 a month for the workspace after a 30-day trial with no card, and your first 10 editors are included.

Stop being the help desk. Let your docs answer for you.

Connect your repo, choose who sees what, and send customers to docs that keep up with what you ship. Thirty days free, no card.

Start free trial Back to the overview