docs.dev vs Mocktail

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

Self-hosted mock API server + dashboard in one ~25 MB binary. Define endpoints, generate realistic data, test errors and latency, and inspect live traffic.

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 Mocktail

Self-hosted mock API server + dashboard in one ~25 MB binary. Define endpoints, generate realistic data, test errors and latency, and inspect live traffic. Model the responses your app expects, headers, delays, even the flaky 401, and let Mocktail keep the data lively. Keep responses fixed, generate fresh values on every request ( uuid, email, price, name ), or swap real fields for fake data when you need to anonymize a response. Create an endpoint, hit Test right from the dashboard, and watch it land in the live stream, method, status, latency, and the exact response and headers served.