docs.dev vs Nova

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

Nova is the analytics and orchestration layer for AI products. Track usage, evaluate quality, and iterate on prompts, all in one dashboard.

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 Nova

Nova is the analytics and orchestration layer for AI products. Track usage, evaluate quality, and iterate on prompts, all in one dashboard. Nova gives you the observability layer your AI features deserve. Run controlled experiments across prompt variants and route traffic to the winner automatically. By the end of the day we had dashboards our whole team actually uses. You can redact PII at the SDK level before anything leaves your servers. Overage is billed at $1 per 10k events, and you can set a hard cap if you prefer strict budgets.