docs.dev vs PassControl

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

Give every AI agent its own identity, scope and budget. PassControl checks each model call while keeping provider keys out of agent environments.

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 PassControl

Give every AI agent its own identity, scope and budget. PassControl checks each model call while keeping provider keys out of agent environments. Each model call is checked before PassControl uses your provider key server-side. Send a call through PassControl's real identity, scope, budget and kill-switch path. Agent message Say hello in 3 words Run governed call. This demo does not contact a paid model or access a provider key. The control decisions are real; the model response is simulated.