Docs.dev
Pricing
- Free Tier
- Free tier on Cloudflare goes a long way; no platform fee
Summary
Documentation debt accrues the moment a feature ships — and most teams pay for it twice: once in the platform subscription, again in metered AI credits, on top of the coding agent they already have. docs.dev is built to stop that double billing.
The tool is a deployable template, not a hosted platform. You own the GitHub repo; you own the Cloudflare account. Your existing coding agent — Claude Code, Codex, whatever you already pay for — drafts the docs branch; your team reviews the rendered page and publishes with a commit. Git handles branches, rollbacks, and review history for free because there is no separate platform state to reconcile. The ceiling appears when your team has no Cloudflare account and no coding agent already in the stack — the workflow assumes both, and neither is negotiable.
Bottom line: Pick this if your team already runs Claude Code and wants doc drafting without a third subscription; skip it if your org has no Cloudflare footprint and no appetite to own infrastructure, because the entire value proposition collapses without both.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Deploys to your own GitHub and Cloudflare accounts, which means your content never lives in a vendor database and an export button is never the difference between leaving and staying.
- Uses the coding agent your team already pays for to draft docs branches, so you avoid a second AI subscription for writing work you could route through an existing contract.
- Every page exposes a raw markdown URL by appending `.md`, so LLM tooling and agents can read your docs without a separate API integration or format conversion step.
- Git handles branches, rollbacks, and review history natively, which means your documentation change process gets code-review discipline without adopting a second approval workflow.
- The template ships with prebuilt agent skills and a `CLAUDE.md`, so agents can draft, navigate, and publish from one-line requests without custom prompt engineering on day one.
Cons
Sign in to edit- The entire workflow requires an active Cloudflare account as the deployment target. Teams with no Cloudflare footprint cannot use the tool as designed — there is no fallback hosting path, and standing up a Cloudflare account solely for this adds an infrastructure dependency the team then owns permanently.
- The drafting loop only produces value if a coding agent is already in the team's stack. Without Claude Code or an equivalent agent, the AI-drafts-your-docs pitch reduces to a markdown site template with a review UI — useful, but not differentiated from static site generators teams may already run.
- Review and publishing are git-native, which is a feature for engineering teams and a hard stop for organizations where documentation is owned by writers or product managers who do not work in pull requests. Teams in that position typically revert to a hosted platform — Notion, Confluence, or a documentation SaaS — where non-engineers can edit without touching a repo.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- Cloudflare Workers, GitHub
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-07-14T16:48:29.097Z
Best For
Who it's for
- Teams already using Claude Code or similar agents
- Projects wanting Git-native documentation workflows
- Users with Cloudflare accounts seeking no extra platform costs
- Documentation requiring machine-readable markdown outputs
What it does well
- Drafting docs for new code features via agent prompts
- Team review of documentation changes before merge
- Hosting docs on custom domains with edge delivery
- Answering reader questions with site-specific AI
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare Docs.dev
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is Docs.dev free?
- Docs.dev has a permanent free tier alongside paid upgrades. You can keep using a baseline version indefinitely without paying.
- Is Docs.dev open source?
- No — Docs.dev is a closed-source tool. Source code is not publicly available.
- Can I self-host Docs.dev?
- Yes. Docs.dev supports self-hosting on your own infrastructure.
- What platforms does Docs.dev support?
- Docs.dev is available on: Cloudflare Workers, GitHub.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
Every code feature ships with a docs debt attached to it. docs.dev attacks that debt at the source: point the coding agent your team already uses at your code repository, ask it to document what changed, and it opens a docs branch with drafted pages. Teammates review the draft on the rendered page — same layout readers see — edit in place, and publish with a single commit. Because the site lives in your GitHub repo and deploys to your Cloudflare account, branches, rollbacks, and review history are just git. No separate platform state, no export anxiety.
The differentiating architecture is ownership. Competing documentation platforms charge monthly seat fees, host your content in their database, meter AI writes on top, and hand you an export button you hope works when you leave. docs.dev is a template you deploy to infrastructure you already control. Reader-facing AI runs on Cloudflare Workers AI in your account. Writing AI is whatever agent your team already has a contract with. The vendor takes no cut of either. Every page also exposes a raw markdown URL by appending `.md` — the convention LLM tooling already expects — so your docs are machine-readable by default without extra configuration.
The tool fits tightly defined conditions: teams already using Claude Code or a comparable agent, projects with an existing Cloudflare account, and engineering organizations comfortable owning a repo-as-documentation-site. It breaks outside those conditions. No Cloudflare account means no deployment target. No coding agent means no drafting loop, and the review-and-publish workflow becomes manual markdown editing with a nicer renderer. Teams whose documentation workflow is owned by a non-technical content or marketing team will hit the git-native model as a hard wall before they reach any AI feature.
The template ships with a `CLAUDE.md` and prebuilt agent skills, so requests like ‘add a page’, ‘fix the nav’, or ‘draft this for review’ work from day one without custom prompt engineering. An agent can create the site, deploy it, and return a single claim code — you sign in once and own everything it built. A reader-facing AI assistant answers questions from your pages, running on Workers AI inside your account, so reader questions resolve against your actual content without leaving your infrastructure.