docs.dev vs RouterFuel

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

RouterFuel is an async Rust LLM gateway routing to 330+ models (OpenAI, Anthropic, Google, Meta, Mistral, and every model on OpenRouter) with semantic caching and...

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 RouterFuel

RouterFuel is an async Rust LLM gateway routing to 330+ models (OpenAI, Anthropic, Google, Meta, Mistral, and every model on OpenRouter) with semantic caching and automatic failover. RouterFuel is a single async proxy layer in front of every model provider you use: direct integrations for 11 major labs, plus every model on OpenRouter as a fallback. Postgres + pgvector are provisioned automatically by Docker Compose. Every provider named is one RouterFuel actually routes to; nothing here is fabricated, it's just not connected to a real running instance on this page.