Hi HN. Some backstory, because it explains why this exists.
Our startup originally worked on AI-assisted documentation generation. When Claude Code and Cursor's agents matured, we asked ourselves the uncomfortable question: does a standalone "AI writes your docs" product still need to exist? We concluded no, and pivoted to what's now keyboard.dev.
That left us with the docs.dev domain. We had a buyer in the docs space lined up and were genuinely excited for it to have a proper home. A month later, they changed their mind. So instead of letting a domain we loved sit parked, we built the docs platform we'd always wanted as a side project.
The workflow it's built around: coding agents already write documentation well, but reviewing agent-written docs in raw MDX is miserable. So with docs.dev, Claude Code updates your docs template in the same session where it ships your code (the template carries a CLAUDE.md and skills, so it knows the conventions). Then you go to your actual docs site, on your domain, log in as an admin, and review the page exactly as readers will see it. Anything the AI got wrong, you edit or delete in place, directly on the live site. Publishing is a git commit to your repo, and CI redeploys. The same URL serves readers and, for admins, becomes the editor.
The economics are the other half of the pitch. There's no hosting on our side and no content database: one click clones the template into your GitHub account and deploys it to your Cloudflare account with push-to-deploy CI. AI writing, image generation, and chat run on Cloudflare's own primitives (Workers AI and friends), billed at Cloudflare's rates on your account. You're not paying a docs vendor to host your own documentation, and you're not paying their markup on AI calls. The optional docs.dev service adds exactly one thing, team sign-in, and it's a sign-in check, not a dependency: if we disappear tomorrow, your site keeps serving.
We deliberately built on existing technology rather than reinventing it: Fumadocs (Next.js + MDX) for the docs framework, chenglou's pretext layout engine for the reading experience (prose flows around figures like a magazine spread, while the server still renders plain indexable <p> text for crawlers and no-JS readers), and Cloudflare's out-of-the-box platform pieces for deploys, CI, and AI.
Honest caveats: it requires the Cloudflare Workers Paid plan ($5/mo) because the server Worker is ~5.3 MiB gzipped, over the free plan's 1 MiB limit. It's a side project, not our main company. And the magazine-style layout is the kind of thing you either love or find gratuitous. We'd genuinely like to hear which.
There's a walkthrough video on the homepage if you'd rather watch the workflow than read it. Happy to answer questions about the agent workflow, the in-place editing, the ownership model, or the pivot. Note it is an early but hope this helps people that wants easy, cheap, and effective documentation on their terms
Our startup originally worked on AI-assisted documentation generation. When Claude Code and Cursor's agents matured, we asked ourselves the uncomfortable question: does a standalone "AI writes your docs" product still need to exist? We concluded no, and pivoted to what's now keyboard.dev.
That left us with the docs.dev domain. We had a buyer in the docs space lined up and were genuinely excited for it to have a proper home. A month later, they changed their mind. So instead of letting a domain we loved sit parked, we built the docs platform we'd always wanted as a side project.
The workflow it's built around: coding agents already write documentation well, but reviewing agent-written docs in raw MDX is miserable. So with docs.dev, Claude Code updates your docs template in the same session where it ships your code (the template carries a CLAUDE.md and skills, so it knows the conventions). Then you go to your actual docs site, on your domain, log in as an admin, and review the page exactly as readers will see it. Anything the AI got wrong, you edit or delete in place, directly on the live site. Publishing is a git commit to your repo, and CI redeploys. The same URL serves readers and, for admins, becomes the editor.
The economics are the other half of the pitch. There's no hosting on our side and no content database: one click clones the template into your GitHub account and deploys it to your Cloudflare account with push-to-deploy CI. AI writing, image generation, and chat run on Cloudflare's own primitives (Workers AI and friends), billed at Cloudflare's rates on your account. You're not paying a docs vendor to host your own documentation, and you're not paying their markup on AI calls. The optional docs.dev service adds exactly one thing, team sign-in, and it's a sign-in check, not a dependency: if we disappear tomorrow, your site keeps serving.
We deliberately built on existing technology rather than reinventing it: Fumadocs (Next.js + MDX) for the docs framework, chenglou's pretext layout engine for the reading experience (prose flows around figures like a magazine spread, while the server still renders plain indexable <p> text for crawlers and no-JS readers), and Cloudflare's out-of-the-box platform pieces for deploys, CI, and AI.
Honest caveats: it requires the Cloudflare Workers Paid plan ($5/mo) because the server Worker is ~5.3 MiB gzipped, over the free plan's 1 MiB limit. It's a side project, not our main company. And the magazine-style layout is the kind of thing you either love or find gratuitous. We'd genuinely like to hear which.
There's a walkthrough video on the homepage if you'd rather watch the workflow than read it. Happy to answer questions about the agent workflow, the in-place editing, the ownership model, or the pivot. Note it is an early but hope this helps people that wants easy, cheap, and effective documentation on their terms