Interfaces
No new app to learn.
Swa shows up where they already are.
Your team asks Swa a question in the thread they were already working in, on the device already in their hand. One identity across every surface, the same agents everywhere, and the same rules applied wherever the question is asked.
Same account, same governance, every surface.
Three ways in
Start alone, or bring the team.
In the browser
Swa Solo opens in any browser with nothing to install and no admin approval to wait for. It is the fastest way to put Swa in front of one person and see what it does.
In the chat tools you run
Slack and Microsoft Teams, installed once for the whole workspace. Swa answers in public channels, private channels, group chats, DMs, and threads, and it reads the thread it is answering in.
On the phone
iPhone and Android apps, for the people whose work does not happen at a desk. Same account and same history as the browser, picked up mid-conversation.
Where Swa runs
Live today, on the surfaces your team opens anyway.
Adoption dies when AI lives somewhere people have to remember to go. Every surface below is one your team already has open, and each one carries the same account, the same agents, and the same rules.

Swa Solo, in the browser
Chat, projects, documents, and your own agents in one clean workspace, on any device. Nothing to install, no IT ticket, and 23+ models behind it with Swa choosing between them for you.
Slack
One OAuth install covers the whole workspace. Swa works in public and private channels, DMs and group DMs, handles files and images, and is aware of the thread it is answering in.
Microsoft Teams
Team channels, conversations, and group chats, with the admin controls an enterprise rollout needs. Ask Swa right where the work is already being discussed.
iPhone and Android
Native apps for the people who are not at a desk. The same account and the same conversation history as the browser, so a thread started on a laptop is picked up on a phone.
One platform underneath
Different door, same building.
A surface is a way in, not a separate product. Whichever one a person opens, they are the same user, under the same rules, on the same balance, with the same agents and the same history behind them.
Consistency
Governed the same way, wherever it is asked.
A question asked in a Slack thread is checked against the same compliance modules, routed by the same model policy, and recorded on the same balance as one asked in the browser. There is no back door where the rules do not apply.

One identity across every surface
A person signs in once and is the same user everywhere. Their role, the models they may reach, and the rules they work under follow them from surface to surface.
The same agents everywhere
An agent built in Solo answers in Slack. Build a helper once, share it with the team, and it is available on whichever surface each person prefers.
No model picker to learn
Nobody has to know which model suits which job. Swa pairs each ask with the right tool, agent, and model, and right-sizes the compute behind it.
One balance behind all of it
Every surface draws on the same balance, so finance sees one picture rather than a per-tool sprawl, and every request stays traceable to whoever ran it.
Get started
Put it in one team's Slack and watch.
One install, one team, the rules that team is held to. You will know inside a week whether people reach for it.
