Why Second Brain runs on your Cloudflare account, not ours
Most AI memory tools store your data on their servers. That means your context, decisions, and personal knowledge live in someone else's infrastructure, governed by their retention policies, subject to their pricing changes, and potentially readable by their team.
Second Brain v2 runs entirely on your own Cloudflare account.
What that means in practice:
Your Cloudflare Workers and D1 database hold the graph. Queries run on your infrastructure. We never see your memories, because they never touch our servers. Your data does not disappear if we shut down.
The setup takes about ten minutes. You deploy a single command, connect your Cloudflare credentials, and the MCP endpoint is live. From that point, you own the stack completely.
Cloudflare's free tier covers most individual use cases. Vectorize, D1, and Workers all sit within the free limits for personal memory graphs.
The tradeoff is that you manage your own deployment. If something breaks, you are debugging your own infrastructure. We try to make this as rare as possible, but it is a real tradeoff.
For teams and shared contexts, Cloudflare's access controls let you gate who can query the graph without building auth from scratch.
What made you most interested in self-hosting your memory layer?
Replies
honestly it's less "self-hosting" and more "not wanting a startup's shutdown to be the thing that erases my memory graph" - I've had that happen with a note-taking tool before and it's a bad feeling. the part I'd want to know before deploying: when you ship a schema change to the D1 tables or the Workers logic, does my existing self-hosted instance need a manual migration step, or does the deploy command handle upgrading in place without me losing data?