docs.dev vs Sovereign AI Registry

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

Compare AI vendors on data residency, training defaults, retention, subprocessors, certifications and EU AI Act role. One row per vendor × product × deployment, every...

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 Sovereign AI Registry

Compare AI vendors on data residency, training defaults, retention, subprocessors, certifications and EU AI Act role. One row per vendor × product × deployment, every claim linked to its source. Governance grade A single A–F letter covering residency, retention, training defaults and how well each claim is evidenced. Data residency Which regions a vendor can genuinely pin your data to, and whose infrastructure it actually runs on. Government access exposure Whether the US CLOUD Act reaches the data, whether PRC law does, or whether neither applies.