docs.dev vs Retrace

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

Record, replay, fork & share AI agent executions. See every LLM call, tool call, and error your agent makes, then debug in seconds. Free for 1,000 traces/mo.

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 Retrace

Record, replay, fork & share AI agent executions. See every LLM call, tool call, and error your agent makes, then debug in seconds. Free for 1,000 traces/mo. Retrace records every model and tool call your agent makes, so you can re-run a failure, branch from the exact step it went wrong, and check your fix before you ship. This is the reliability loop Retrace owns, end to end. Now a production failure becomes a permanent regression test you can re-run.