docs.dev vs Hydra, a local

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

Route to a target confidence of correctness, not just the cheapest model. Hydra samples models adaptively (SPRT), cuts AI API costs 70-85% along the way, and keeps...

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 Hydra, a local

Route to a target confidence of correctness, not just the cheapest model. Hydra samples models adaptively (SPRT), cuts AI API costs 70-85% along the way, and keeps sensitive data local. Hydra rides the cost/quality Pareto frontier, stops sampling the instant confidence clears the bar, and reads the code graph to know when a change is dangerous. A hub file with many transitive dependents is cascade-capable, so it demands more confidence. Every access an agent makes is recorded in a local, hash-chained ledger.