One workspace per project, one instance for all of them.
Run outbound for several projects or brands from one installation. Each project gets its own workspace, and your own Claude connects to each one you grant it.
Kept apart. Each project keeps its own data, keys, limits and members.
Senders and limits apart
Each project connects its own mailboxes and domains, each with its own daily caps and health. Workspaces share the instance’s workers and warmup pools.
Contacts apart
Contacts, suppression lists, campaigns and the inbox belong to one workspace. Every read is scoped to it.
Members and keys apart
Each workspace has its own members and roles, its own encryption key, and its own autonomy policies for the agent sends coming with WhatsApp and LinkedIn.
Data that moves
Export one project’s workspace to an archive and import it on another instance, for a handover or a spin-out.
One install. Your servers carry every project.
One instance holds every workspace, so there is one thing to back up, update and secure. Add worker machines as the projects grow.
Today your Claude connects to one workspace per connection. A single connection that works across every workspace you grant, naming the workspace on each call, is planned. See the roadmap
Pre-release. SalesOS release images are not published yet; to run SalesOS today, build it from source.
This is not an agency platform with client logins yet. Client roles for agencies running a workspace per client are on the roadmap for later.
Put every project on one instance.
Install SalesOS once, add a workspace per project, and connect your Claude to each.