Comparisons
ilumd vs the alternatives
Most tools ask you to move your docs into them and manage access there. ilumd doesn’t. Your Markdown stays in GitHub; ilumd adds the layer it never had — who sees what, whether it’s current, and branded portals per client. Here’s how that compares to the tools teams reach for today.
ilumd vs Docusaurus
the open-source static-site generator
Devs love it for docs-as-code — but it has no access control, no cross-repo visibility, and no way in for non-developers.
ilumd vs Notion
the all-in-one workspace
A great workspace — but engineering docs in Notion are a second silo, copied out of the repo and stale the moment code moves.
ilumd vs GitBook
the documentation platform
A polished docs platform — but you author in their tool and pay per editor. ilumd never moves your docs and never charges for readers.
ilumd vs Zendesk
the customer-support platform
A full support suite — heavyweight and seat-priced for what's often just a self-serve docs portal. ilumd builds that portal from docs you already have.
ilumd vs Confluence
the enterprise wiki
The corporate wiki of record — but a seat-priced silo your docs get copied into, disconnected from the code.
ilumd vs Mintlify
the AI docs platform
Beautiful AI-era docs — but you publish into their platform, meter AI credits, and access control sits in enterprise.
ilumd vs Miradorly
the closest neighbour
A read-only portal over your repo's Markdown — the same starting point as ilumd, without the write-back, freshness, or per-client portals.
The common thread
One layer, over the docs you already have.
Docusaurus, Notion, GitBook, and Zendesk are all places docs live; Miradorly, like ilumd, reads them where they are but stops at read-only. ilumd is a layer over the docs that already live in your repo — so you never migrate, never pay per reader, and non-developers, clients and their customers all get exactly the access they should. Keep writing docs in code; let ilumd govern, freshen, and share them.