AgentX runs your agents on your own infrastructure. Your daemon owns your agents, sessions, messages, and artifacts at rest. Our control plane sees only what it needs to sign you in, bill you, and route your fleet — never the work itself. Here is exactly where everything lives and what leaves your machine.
Your agents, sessions, messages, and artifacts live in a local SQLite database on the machine you run the daemon on. They are created, stored, and replayed there. Daemon-local work never leaves the daemon unless you reach for it.
Core is the control plane: identity, billing, and the registry of which daemons and agents exist. It meters your usage as a count, never message content. Core never executes agent work and is never on the per-message data path.
When you open the console, terminal output streams live through the Bridge and web edge, and transcript and artifact reads are relayed on demand. The edge holds this content only transiently, in memory, for the active stream or request — it is not persisted. It also carries coordination between agents on different machines. Daemon-local data stays local.
AgentX supervises the agent CLIs you already install; it does not run them for you and does not proxy your model calls. You bring your own model subscriptions and API keys. We never bill AI inference and never see your model traffic.
When an agent or a teammate addresses a message to a person on your team, we deliver its full text to that person by email, with a link to the console. If they turned on browser notifications, the first line is also shown as a notification. The email is sent through Amazon SES in the EU (region eu-west-1, Ireland). We keep only a message ID and a timestamp for quota counting, not the text.
| Data | Where it lives | What leaves your machine, and when |
|---|---|---|
| Agents, sessions, messages, artifacts — your work product | Local SQLite, on your infrastructure | Nothing at rest. Content leaves only while your console is open — terminal output streamed live and transcript/artifact reads relayed on demand through the edge, held only transiently in memory and not persisted there. The one exception is a message addressed to a person: see the last row. |
| Your identity | Core | On sign-in. |
| Billing & subscription | Core | When you subscribe or your plan renews. |
| Registry metadata — that a daemon and named agents exist | Core | On enrolment and heartbeat. |
| Usage counts — messages metered for your quota | Core | Periodically. A count, never the message body. |
| Cross-machine coordination — agents on different hosts working together | Bridge | Only when agents on separate machines coordinate. Daemon-local work never leaves the daemon. |
| Model API keys — BYOK | Your daemon / your environment | Never. We don't proxy or bill model inference. |
| Messages addressed to a person on your team | Your machines | When the message is sent: its full text goes to that person by email, through Amazon SES in the EU (Ireland). If they turned on browser notifications, the first line is also shown as a notification. We keep only a message ID and a timestamp for quota counting, not the text. |
~ Your daemon owns the data at rest