DOCS

Data & privacy.

Agent Manager is self-hosted, which means your data stays on your machine by default. This page covers where everything is stored, what is sent to external model providers, and how to back up and restore.

The short version

Agent Manager runs as one binary on a machine you control. There is no Agent Manager cloud account, no telemetry endpoint, and no required phone-home.
Your model provider keys live on your disk. The crew only sends them where you configured them to go: outbound to the model providers you picked.
Your code, repos, tasks, and agent memory stay on disk in plain files and a local database. Nothing is uploaded to us, because there is no “us” in that path.
The only network calls the crew makes on your behalf are (a) calls to the model providers you configured, with your keys, and (b) calls to integrations you connected.

Read that again: nothing about your code or your tasks is sent anywhere except to the model providers you configure, using your keys.

What runs where

The Agent Manager server, its database, the agent runtimes, the orchestrator, and every worker bot all execute on your hardware (laptop, home server, rented VM, on-prem box). The web UI is a local app served from that same process.

You reach it from your browser at http://localhost:<port> or behind whatever reverse proxy you put in front. There is no external relay.

What gets stored on disk

Everything below lives in your install directory. Default locations follow; configure them in Settings.

Config & secrets — provider keys, webhook secrets, integration credentials. Encrypted at rest with a key derived from your install passphrase.
Projects — one directory per project, holding the repo reference, lane assignments, agent definitions, and per-project settings.
Tasks & transcripts — every task with its full stream: the prompt, every model call and response, the tool calls, the diff, the resulting commit.
Agent memory — lessons learned, preferences, and notes each agent has stacked up across runs. This is the “self-training” data: see Concepts.
Heartbeat log — every floor-walk the boss took, with what it noticed and what it did.
Inbox & escalations — what was sent to whom, and what came back.

What leaves your machine

Only what you deliberately wire up to leave. Concretely:

Model provider calls. When an agent needs a model, the crew sends the prompt and any required context (file contents, prior turns) to the provider you configured, authenticated with your key. That call is between you and that provider, governed by that provider's terms.
Connected integrations. If you connected GitHub, your CRM, Slack, a database, or anything else, the crew talks to those endpoints to read and write on your behalf. Same story: you configured it, you control the credentials, you see the calls in the audit log.
Optional update check. Agent Manager can ping a version endpoint once per day to tell you a new release is out. This is opt-in and the request carries no project data. You can disable it.

That's the list.

What does not leave your machine

Your code, your diffs, your commit messages.
Your task descriptions and agent transcripts.
Your agent memory — every lesson an agent learned, every preference it picked up.
Your credentials, beyond the call they were made for.
Your board state, your inbox, your heartbeat log.

Backups

Since everything is plain files plus a local database, the backup story is the boring one: copy the install directory. Stop the server first for a consistent snapshot, or use the built-in Snapshot command which does the safe flush for you.

Restore is the reverse: stop the server, drop the directory back in place, start it. No importer, no vendor lock-in.

Hardening checklist

If you want to push the privacy posture further than the defaults:

Bind the web UI to 127.0.0.1 and reach it via SSH tunnel or your own VPN.
Put it behind a reverse proxy with TLS, even on a LAN.
Use per-project keys and scope integrations to the project that needs them (see Settings).
Turn off the optional update check.
Encrypt the disk the install lives on. The at-rest encryption covers the secrets store too.

Early-access honesty

Agent Manager is in early access. The privacy story above describes the current behaviour of the build you run. As features land during early access, this page is the source of truth — if a future feature would change what leaves your machine, it shows up here before the feature ships.

If you find a behaviour that contradicts this page, that's a bug. Report it through the support channel and we'll fix the page, the code, or both.