Search "best API documentation tool" and you'll get the same names every time.
We tested them. Then picked one that never shows up.
The project: a developer platform built inside a regulated banking environment.
The docs couldn't just look good. They had to be:
→ Self-hosted
→ Self-serve
→ Embedded directly inside the app we were building
→ Flexible enough to pull documentation from multiple sources
@Redocly,
@scalar,
@mintlify, all genuinely good tools. But "good in general" isn't the same as "right for this." Each came with trade-offs on hosting, customisation, or how the docs were managed. The kind you don't get to make when you're building for a bank.
So we kept testing. And landed on a name that never autocompletes:
Fumadocs, FOSS created by
@fuma_nama
It gave us full customisation, clean self-hosting, and the flexibility to bring documentation into the app on the client's terms, not the tool's.
The lesson isn't "use Fumadocs."
It's that the most popular tool and the right tool are rarely the same thing. Test against your real constraints, not the internet's defaults.
That's where the good engineering decisions actually happen.