docs.dev vs Wattfare

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

Users connect, set a spending cap, and you call any model through one SDK, charged to them, not you.

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 Wattfare

Users connect, set a spending cap, and you call any model through one SDK, charged to them, not you. OpenAI-compatible Works with the Vercel AI SDK ~5-min integration. One button connects a user's inference budget to your app, metered, capped, and revocable. The problem AI costs are the one line item you can't predict. Every AI app makes the same uncomfortable bet: price high enough to survive your power users, ration usage so nobody hurts you, or quietly lose money on the heavy ones.