Docs start fresh and useful, but give them a sprint or two and they’re outdated, misplaced, or flat-out wrong. They live in wikis no one checks, fall out of sync with the code, and end up like an unmerged PR—forgotten and full of conflicts.
The core problem? Docs platforms aren’t designed for developers.
It’s an internal docs platform built for devs who’d rather ship features than format wikis.
⚡️ CLI-first – Write docs like you write code.
🌲 Auto-updating – No more stale docs (always evergreen!).
🛠 IDE-integrated – Docs where you work, not buried in a wiki.
🔷 All-in-one – READMEs, collaborative docs, and diagrams in one platform.
Ever found a doc that actually solved your problem—without asking in Slack?
Yeah, neither have we. Docs are either missing, impossible to find, or outdated.
It’s the 2020s, yet every docs tool still treats documentation like a wiki, not something built for developers. So we asked:
- Why can’t we write docs in a CLI, like code?
- Why can’t we find and edit them in our IDE, where we work?
- Why don’t docs auto-update, like dependencies?
Turns out, the entire documentation space is stuck in the past. So we—Seth (CEO) and Zac (CTO), two brothers and builders—created Joggr: a docs platform made for developers 🚀🚀
Seth (left) and Zac (right)
We believe in Open Source, we believe building in public (as much as possible) is key to success, we want to give back to the developers that make our company what it is. See our projects below.
- 🟦 tempo - Programmatically create Markdown documents.
- 🏰 dungeons & docs - A library of battle tested documentation templates in markdown.
- 🔼 fastify-prisma - Fastify Prisma plugin to share the same PrismaClient across your entire server.
You can sign up for free at our website: https://joggr.io
(or click button below 👇)
