docs.dev vs Selfship

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...

When 300 customers hit the same wall, Selfship finds the exact moment it goes wrong and opens an eval-backed pull request. You review, you merge.

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 Selfship

When 300 customers hit the same wall, Selfship finds the exact moment it goes wrong and opens an eval-backed pull request. You review, you merge. Your live traffic shows what to fix next, and the loop handles the rest. Selfship reads what each customer was trying to do, and whether they got it. A proposed change lands in your GitHub with eval evidence attached, impact, sample sessions, and scores you can audit in the PR.