Dike vs docs.dev

A gateway proxy that makes your chatbot or RAG pipeline EU AI Act compliant with one base-URL change. Audit-grade logging, oversight records, incident reporting.

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

About Dike

A gateway proxy that makes your chatbot or RAG pipeline EU AI Act compliant with one base-URL change. Audit-grade logging, oversight records, incident reporting. PII is redacted, malicious calls are blocked, and every request becomes an audit record with full traces. Dike captures every prompt, retrieval, and override as you run, so the audit trail builds itself. Tamper-evident by construction: auditors can cryptographically verify that nothing was altered or deleted. Dike opens the case, tracks the clock and drafts the report to your market surveillance authority.

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.