docs.dev vs Memoars

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

Memoars is a user-owned, encrypted memory layer that carries approved context across AI assistants while keeping you in control of what is learned, changed, and forgotten.

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 Memoars

Memoars is a user-owned, encrypted memory layer that carries approved context across AI assistants while keeping you in control of what is learned, changed, and forgotten. Only encrypted memory content is written to your bucket. Memory content is ciphertext, while organization, workspace, identity, grant, version, usage, transcript, and proposal metadata may be visible to the coordinator. On an opt-in run, the dreamer will review this lifecycle and propose what to keep, update or merge. Running memoars against your own bucket is free and complete: one agent, one machine, fully encrypted.