Docs-as-code · governance layer
Stop being the help desk.
Put your docs to work.
The answer is already written down. It’s in a repo nobody outside the dev team can open.
Thirty days free, no card. Every reader free.
We never move your docs — edits come back as pull requests.
- Slack · DMTuesday 9:14
hey — where's the deployment runbook for Acme?
- EmailWednesday 16:02
Sorry to chase — any chance of that API doc?
- Slack · #acme-projectThursday 11:40
where's the deployment runbook for Acme again?
The same question, three times, to the person least able to spare the time.
Step one
Every doc you’ve already written, in one place.
Connect a repo and ilumd finds every Markdown file in it — including the ones everybody forgot. Nothing moves, nothing is copied, and the repo stays the source of truth.
Once it’s found, it’s searchable across every client and every repo — how you solved it last time is a search away, not a Slack thread and a hope.
Two minutes to connect. Nothing to migrate.
Docs in the repo are read by the people and the agents working in that code. Docs in a wiki are not.
Repo
- acme-corp/docs
- onboarding/
- getting-started.md
- api/
- reference.md
- webhooks.md
- ops/
- deployment-runbook.md
- internal/pricing.md
Acme Corp · 24 documents
- Onboarding GuideFreshPublicStaff
- API ReferenceAgingAcme client
- Deployment RunbookVerifiedDev
- Pricing — internalFreshPrivate
- Sources ·
- GitHub
- GitLab
Deployment Runbook.md
ops/ · acme-corp/docs
Audience
Not visible to anyone else.
Internal team portal
Acme (client) portal
Deployment RunbookPublic portal
Step two
Nothing is visible until you say so.
Every doc starts excluded. You set the audience on each one — your team, one client, or the public — and ilumd publishes a branded portal for each audience that sees only what it’s meant to.
Your client sees their docs, and nothing else.
Step three
Current, not just recently edited.
Every doc carries a freshness rating from its last edit and its last human check, and ilumd flags it the moment code changes beside it. 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.
Doc edited
Code changed
Two commits beside this doc since its last edit — flagged for a human to re-check.
Doc edited
Human check
A person confirmed it’s right, recently. That outranks the calendar.
Step four
Anyone can suggest a fix. Your review still decides.
A client spots something wrong and suggests an edit. ilumd opens a pull request against your repo. Your normal review process decides what merges, and the portal follows the moment it does.
Docs improve without anyone leaving the repo behind.
- 1
Client spots an error
Acme portal
Retries run every 30s
- 2
Suggests an edit
- retry every 30s
+ retry every 60s
- 3
ilumd opens a PR
#482
ilumd/webhooks-retry-interval
- 4
Your team reviews
JLapproved
merged to main
- 5
Portal updates
Acme portal
Retries run every 60s
Doc work lands where your team already works — and published docs stay in sync with the source, so nothing drifts.
- Notion
- Confluence
- Jira
- Linear
- GitHub Issues
- GitLab Issues
- Slacknext
Step five
Ask the docs, and get an answer they’re allowed to have.
Ask your docs answers from the governed knowledge base, scoped to what the person asking may see. A client’s question is answered from their own material, with citations, under the same access rules as the portal itself.
Raw repo access is all-or-nothing. A governed view is the only way to answer from your docs without handing over everything in them.
Included on every workspace.
How did we handle the fixed-fee migration scope?
Same access rules as the portal. Nothing from another client in scope.
$29 a workspace. Every reader free.
A workspace is one governed view for one audience — your team, or one client. Not per seat, not per doc, and never per reader: staff, clients, and the public all read for nothing.
Run client work? Bill one client for their portal and your own workspace is covered — you start at $0.
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?
Isolation is a core primitive, not a permissions checkbox bolted on later. Access is default-deny and enforced at the data layer, not by filtering the UI — Client B's docs aren't in a response 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 — one workspace is one governed view for one audience — after a 30-day trial with no card. Your first 10 editors are free; larger teams are banded. Readers are always free, and there's no free-forever tier: just the trial. If you run client work, your first paying client's workspace covers your own.
Put your docs to work. We’ll make them findable, governed, and trusted.
Connect a repo, choose who sees what, and send your client a link. Thirty days free, no card, every reader free.