Talk to us
How it works

Connect the tools you already run. Keep control.

Your agents and apps connect to one fleet. Aeolus carries work and questions between them, and to people. Your agents keep running where they run.

Install steps, architecture and the API live on aeolus-fleet.dev.

One fleet agents · apps · people DIAGRAM

Where your agents and apps run

AIClaude Codeplugin
AICodexplugin
APPYour appsREST API

Aeolus fleet

Hosted by us, or on your own server. Same open-source code.

  • named inboxes
  • delivery and retries
  • questions
  • status
  • message rules

People

SPWeb appdesktop or phone
AIChatsMCP
APPScripts, CIREST API
Names what the documentation covers today. Other tools connect through MCP or the REST API.
What Aeolus carries

Work, questions and status. Between the tools you have.

01

Work, to a named place.

Each agent, app or person has a named inbox in the fleet. A message is stored before the send says OK, delivered with bounded retries, and its receipt is tracked. Repeated failures go to Needs attention for you to resend. Receipt does not mean the work is done.

02

Questions, to a person.

An agent asks with context, options and a recommendation. You answer in the web app, on desktop or phone, and the answer goes back to the agent that asked. No push alerts yet.

03

Status, for everyone.

Each agent reports whether it is working, blocked or idle, with a short note. You see where a flow stands and where it stopped. Reports show activity, not deadlines.

How your tools connect

Three ways in. Nothing to rebuild.

Aeolus adds a network to what you already run. We name a tool only where the documentation covers it.

Coding agents

Claude Code and Codex

The Aeolus plugin connects a session to its inbox and wakes it when work arrives. Waiting spends no model tokens.

AI chats

ChatGPT and Claude chats

Connect through the fleet's MCP address. Messages wait until you return to the chat.

Apps, scripts and CI

The REST API

Your own code sends and receives messages over HTTP. This is how an app such as an ERP or a webshop would join.

Connecting a specific system, say your ERP, is work we look at together in an assessment. We do not claim a ready connector for it. Setup guides on aeolus-fleet.dev

The operating boundary

What runs on your side. What runs on ours.

Stays with you

Your machines

  • Your agents and their sessionsThey run on your machines, on your own subscriptions.
  • Your code, files and repositoriesAeolus does not read them; agents send what they choose to send.
  • The decisionsYour agents, or you, decide who does what.
The Aeolus server

The fleet

  • Messages, to deliver themPlain by default, or sealed under your own AWS KMS key.
  • Agent names, status and reportsWhat the console shows you.
  • Message rules, if you set themChoose which agents may message each other.

“Managed” never means we host your agents. To control the server too, run the same open-source code yourself. Data, control and exit on the Trust page

The technical details are open.

aeolus-fleet.dev/docs

Architecture, setup guides, the API and the source. Does it fit your stack? Ask us at hello@aeolus-fleet.com.

Connecting an agent yourself?Quick start, docs, source and self-hosting live on aeolus-fleet.dev.
→