Docs-as-code · You decide who sees every doc
The answer is already written down. It’s just hidden from view.
It’s in a repo nobody outside the dev team can open. So the question comes to you. Again, and again… and again.
Thirty days free, no card. Every reader free.
We never move your docs — edits come back as pull requests.
Step one · Discover
Connect a repo. Every doc you’ve already written comes into view.
ilumd finds every Markdown file in it — including the ones everybody forgot. Your docs stay where they are and the repo stays the source of truth; ilumd keeps a synced copy to serve and search them.
Search every repo at once. You decide who sees what, and each person searches only what they’re allowed to see. How you solved it last time is one search in ilumd, not an email chain or a Slack thread full of follow-ups.
Two minutes to connect. Nothing to migrate.
Sources · GitHub · GitLab
Step two · Choose who sees it
Nothing is visible until you say so.
Every doc starts private. You set the audience on each one — your team, one client, the public, or named people — and each audience sees only what’s shared with it. Your client signs in; the public browses your branded portal.
Your client sees their docs, and nothing else.
Who should see the deployment runbook? Pick one, or several.
Lit for Acme (client) and Specific people. Not visible to anyone else.
Step three · Keep it current
Automatic detection. Know it’s accurate, not just recent.
Every doc carries a freshness rating based on when it was last edited and how recently the code it relates to has changed. When that code moves on and the doc doesn’t, ilumd flags it, links the change that caused it, and puts it in front of your team to re-check.
A doc touched last week still gets flagged if the code moved on after it.
You can tell a client a doc is current, and be right.
Webhooks
api/webhooks.md
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.
1Client spots an error1 / 5
Acme portal
Retries run every 30s
2Suggests an edit2 / 5
- retry every 30s
+ retry every 60s
3ilumd opens a PR3 / 5
#482
ilumd/webhooks-retry-interval
4Your team reviews4 / 5
JLapproved
merged to main
5Portal updates5 / 5
Acme portal
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
Every Markdown file in your repos.
Raise issues in
Keep in sync
Updated automatically from ilumd.
Notify by
Step five · Ask your docs
Ask the docs, and get an answer they’re allowed to have.
Ask a question in plain words. ilumd answers from your governed docs — only the ones the person asking is allowed to see — and cites them, under the same access rules as the portal itself.
Raw repo access is all-or-nothing. This answers from your docs without handing over everything in them.
Included on every workspace.
How did we handle the fixed-fee migration scope?
- Globex · rollout plan
- Initech · pricing
- Internal · on-call runbook
- Migration playbook
- Hooli · incident review
- Vandelay · SOW
- ADR-014 · queue choice
- Globex · runbook
- Fixed-fee SOW template
- Internal · release checklist
- Hooli · contract
- Initech · roadmap
- Vandelay · API keys
- Change-request policy
- ADR-009 · auth provider
- Globex · retro
- Initech · SLA
- Hooli · audit
- Internal · postmortems
- Hypercare checklist
- Vandelay · pricing
- Globex · contract
Pricing
$29 a workspace. Every reader free.
A workspace is one client or project: its repos, its docs, who can see each one, and its own branded portal, with copies in Notion or Confluence kept in sync. Not per seat, not per doc, and never per reader — staff, clients, and the public all read free.
Run client work? Give each client a workspace, then let them pay ilumd directly, or fold it into your own service and bill them your way. Your first paying client covers your own workspace.
Your team
read free
Your clients
read free
The public
read free
Side-by-side: ilumd vs Docusaurus, ilumd vs Notion, ilumd vs GitBook, ilumd vs Zendesk, ilumd vs Confluence, ilumd vs Mintlify, and ilumd vs Miradorly.
Straight answers
Questions you’re right to ask.
How do I get started?
Sign up, connect a GitHub or GitLab repo, and pick who sees what. Thirty days free, no card. Your docs never move — ilumd reads them where they are, and edits come back as pull requests.
Do I have to move my docs?
No. Your docs stay exactly where they are — Markdown in your GitHub or GitLab repos, versioned in Git. ilumd reads them; it never migrates or locks them in.
How do edits work?
Anyone can suggest an edit and ilumd opens a pull request against your repo. Docs stay docs-as-code, and your normal review process still decides what merges.
How is one client kept from seeing another's docs?
Every doc starts private, and each client sees only what you've shared with them. That rule is enforced in the database itself, not by hiding things on the page, so Client B's docs aren't in anything Client A can request.
Do I pay for readers?
Never. You pay for what you govern, per workspace. Staff, clients, and the public read for free — that's the whole point.
What does ilumd cost?
$29/mo per workspace, after a 30-day trial with no card. A workspace is one client or project: its repos, its docs, who can see each one, and its own branded portal. Your first 10 editors are free; larger teams are banded. Readers are always free, and there's no permanently free plan, just the trial. If you run client work, your first paying client covers your own workspace.
Stop being the help desk. Let ilumd answer for you.
Connect a repo, choose who sees what, and send your client a link. Thirty days free, no card, every reader free.