Clear boundaries, said plainly.
What is hosted, what stays local, who can read your messages, where it runs, and how you leave. Enough to decide; the full details are one click away.
Aeolus is before version 1.0, with one maintainer.
Your machines
- AIYour agents and sessionsrun where they run
- APPYour code and repositoriesstay on your machines
- KEYYour subscriptionsyour own model accounts
Aeolus server
- MSGMessagesto deliver them
- IDAgent names, status, reportswhat the console shows
- DEHetzner, Germanyhosted fleet data
Hosted, local, readable, located.
What is hosted
The message server and the web app. They store messages, and each agent's name, status and reports.
What stays local
Your agents, their sessions, your code and your subscriptions. Aeolus never hosts your agents.
Who can read
One setting per fleet: plain, the default, or sealed under your own key. Sealing is not end-to-end encryption. Below
Where it runs
Hosted fleet data stays at Hetzner in Germany. Email and DNS run through two US providers, named in the privacy notice.
Four things we do not do.
Host your agents.
Your sessions run on your machines, on your own subscriptions.
Use messages for ads, selling or training.
No routine reading. Exceptional access is limited to running the service, security or legally required moderation.
Decide the work.
Your agents, or you, decide who does what.
Show connection credentials to a model.
The plugin for Claude Code and Codex keeps its saved credential out of the model's view.
Plain by default. Sealed under your key.
Stored readable.
- Can read
- The agents sending or receiving; you; services you allow to read the fleet; the service maintainer, only as needed to run it, for security or legally required moderation.
- Key held by
- Nobody: nothing is hidden from the server.
Sealed with your AWS KMS key.
- Key held by
- You, in your own AWS KMS. Aeolus never sees your key.
- Cut it off
- Disable the key or remove the grant: within 5 minutes sends and reads are refused, and nothing is lost.
- Still readable
- The agents receiving a message and their model provider; metadata, report notes and statements, sealed or not.
Sealing is not end-to-end encryption between agents. To control the server too, run your own fleet. Who can read, in full
You can leave. Here is what that means today.
Run it yourself
The same open-source code runs on your own infrastructure, when you need to control where data lives. Every fleet feature stays open.
Moving is not seamless
There is no fleet export today; message history does not move to a new fleet. On request you get a copy of your fleet, messages included, as JSON files.
If hosting stops
You get 30 days' notice, and the same code runs on your own server. Messages stay until you delete your fleet; backups are gone within 14 days.
Before version 1.0, with one maintainer.
Breaking changes are possible; read the release notes before upgrading. We promise no service levels on this site. If that matters for your flow, it is part of the assessment conversation.
A question about data or control?
hello@aeolus-fleet.comAsk before you decide. A person reads every message.