Agents for the legwork. People for the decisions.
SalesOS started with one operator running outbound for several projects at once. The work was the same every week: find the right people, read up on them, write something worth reading, follow up, answer replies. Most of it was legwork an AI could do well. Sending was the part nobody should hand over blindly.
So SalesOS gives the legwork to agents, your own Claude first, with a curated set of the operations a person has in the dashboard. And it keeps the decision about what leaves with people, enforced by the server rather than by a prompt the model could talk its way around.
It is self-hosted because the data it holds (your contacts, your conversations, your mailbox credentials) belongs on infrastructure you control, and because nothing about running it should depend on someone else's service staying up.
Built on warmbly. A fork, credited plainly.
SalesOS is built on warmbly, an open-source email warmup and cold outreach platform, used under its Apache 2.0 licence. The email channel (warmup, careful sending, the unified inbox, the CRM, automations, the API and MCP server, and the self-host installer) comes from that work.
SalesOS is an independent project. It is not warmbly, and it is not affiliated with or endorsed by warmbly or its authors. The licence and copyright notices travel with the code.
The stance. Rules we hold ourselves to.
A person on every send, by default
Agents are good at legwork and bad at knowing when not to write. The server holds what they ask to send until a person says yes, unless your team chose otherwise for an action.
Nothing promised that is not built
Planned work is listed in full on the roadmap and badged as planned anywhere else it is mentioned. A feature reaches its product page when it ships.
No guarantees we cannot keep
No inbox placement promise, no account that cannot be restricted, no forecast dressed up as a probability.
Your servers, your keys
It runs where you run it, on your own AI and data accounts, and it reports nothing back to us.
Run it on a server you control.
Self-host it with your own keys, and keep the decision about what leaves with people. Pre-release: the installer brings up the upstream warmbly release until SalesOS publishes its images.