docs.dev vs Knownbase

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

Stop re-explaining your codebase to AI. Knownbase gives Claude Code, Codex and MCP agents persistent project memory that survives every session.

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 Knownbase

Stop re-explaining your codebase to AI. Knownbase gives Claude Code, Codex and MCP agents persistent project memory that survives every session. Knownbase gives your AI coding agents persistent, searchable project knowledge, so architecture decisions, debugging discoveries, conventions and lessons survive across sessions and tools. Works with Claude Code, Codex, Cursor, ChatGPT and any MCP-compatible agent. They're storage failures: the agent learned something real and had nowhere durable to put it. Compaction loses the discoveries The context gets compacted mid-task and the hard-won finding from two hours ago is summarized down to nothing.