Choose Your Trust Level

Four modes, ranked by how much outer.bot's own servers can see. Pick the one that matches how much you trust us — you're not locked into one.

            Blunt version: Proxy mode is a real man-in-the-middle: your prompts and code pass through our servers so we can inject context automatically. Hooks mode never sends your conversation through us at all, your own tool reads your memory repo directly. Self-hosted means our servers never see your memory, period, not even the metadata. There's no dishonest way to describe this tradeoff, so here it is straight.
        

Your memory lives in a git repository you hold, on any host, or your own hardware. We can't read it, lose it, or be compelled to hand it over. That isn't a privacy policy. It's where the data physically is.

What outer.bot's servers can see	Proxy	Hooks (hosted repo)	Hooks (client-only)	Self-hosted
Your prompts and code in transit	Yes — every request	No	No	No
Your memory repo's content	Yes — read every session to inject it	Yes — we host the repo	No — repo lives on your own git host	No — your infrastructure end to end
Who's using outer.bot, how often	Yes — token counts, latency, model, timestamps	Yes — same metadata	Yes — auth still checks in with us	No — nothing calls home
Your provider API key	Held encrypted on our servers, decrypted per-request	No — your tool holds it locally	No — your tool holds it locally	No — never touches us
Setup effort	Change a base URL. Nothing else.	Clone `memrepo-tools`, paste a hook config. We host the git remote.	Same, but the git remote is your own host (GitHub, GitLab, self-hosted).	Your own git host and your own CI engine. Most setup, most control.
Who runs the memory engine	Us, server-side, invisibly	You (or us, on the Pro hosted option) via a scheduled job	You, via a scheduled job (GitHub Actions, GitLab CI, or plain cron)	You, entirely — nothing about the engine touches our infrastructure

Why proxy mode still exists

Context injection that adapts to what you're actually asking — not just a static file dump — needs something in the request path deciding what's relevant per turn. That's proxy mode's whole value: it's the most capable mode, and the cost of that capability is that we're structurally in the middle. We think that's a fair trade for a lot of people. We also think you should be able to see the trade before you make it, which is what this page is for.

Why the self-hosted column is the honest answer to "why should I trust you"

Self-hosted means your memory repo lives on git infrastructure you control, and the engine that reads/writes it runs on compute you control — a cron job or CI runner with no dependency on outer.bot being reachable, funded, or even in business. We can't see your memory. We can't see your usage. If we disappeared tomorrow, self-hosted setups keep working exactly as they do today, because nothing about them depends on us. That's not a marketing claim — it's a description of what doesn't call our servers.

Switching modes

Your Trust Dial setting lives in your account settings and can be changed at any time. Switching to a more private mode doesn't lose history — your memory repo (once provisioned) is the same repo regardless of which mode is currently reading/writing it.