docs.dev vs Papercrane

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no...

Every analytics vendor is bolting an AI copilot onto their dashboards. Power BI has one. Tableau has one.

About docs.dev

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no platform fee, no metered AI. Reviews, branches, and rollbacks come free, because it is just git. Your content in their database, and an export button you hope works when you leave. Writing AI is the agent you already have; reader-facing AI runs on your Workers AI.

About Papercrane

Every analytics vendor is bolting an AI copilot onto their dashboards. Power BI has one. Tableau has one. They all work the same way: the human drives the old tool, and the AI sits in a sidebar making suggestions. I took the agent you already use and built the BI tool around it. papercrane-cli is a command line tool that gives Claude Code everything it needs to turn a business question into a live dashboard: authenticated access to your data, a real dashboard workspace, and a path to a link you can send to anyone.