docs.dev vs Whissle Gateway

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

The whole Whissle voice stack behind one gateway, reverse proxy, real-time WebRTC pipeline, and the agent runtime. Run the lightweight backend (no model weights) on a...

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 Whissle Gateway

The whole Whissle voice stack behind one gateway, reverse proxy, real-time WebRTC pipeline, and the agent runtime. Run the lightweight backend (no model weights) on a small VM with your own API keys, or add the separate Whissle models service for on-prem ASR/TTS/video with nothing leaving your network. The same engine that powers the hosted platform ships as a gateway you can run on your own infrastructure: a reverse proxy in front of a real-time WebRTC voice pipeline and the agent runtime.