Teams
One plan for everyone, shared vaults next to each person's own, team channels, and a log of what Alwen did.
On Team and Business, a whole team shares Alwen. The owner creates the team on the Team page and invites people with a link. Everyone in it has the team's plan, keeps their own vault, tools and keys, and shares the team's vaults and its AI. The price stays the same however many join.
People
- Owner: pays, makes admins, ends the team. They can't leave it.
- Admins: invite people, remove members, add shared vaults, see the team's log.
- Members: use everything the plan has. Someone on Free who joins keeps what they connected; when they leave, they go back to their own plan with their own vault.
An invite link works once, for 14 days. With an email, only the person signed in with that email can use it.
Shared vaults
The team's memory, next to everyone's own: three on Team, as many as you like on Business. Each one is kept by Alwen, or lives in a private repository in your GitHub or your organization's: name it as owner/name, create it on GitHub and give Alwen access to it. Everyone's tools read the shared vaults; search says which vault each note is in, and a tool saves to a shared vault when asked to. In the dashboard, Notes opens each one: everyone reads them, the owner and admins fix and remove notes.
Team channels
Say “@alwen answer everyone here” in a Slack channel or a Telegram or Discord group. Everyone there gets answers from the team's first shared vault, and the work they ask for goes to the team's agents; each request keeps who asked. Private chats with @alwen stay personal. “Stop answering everyone here” ends it.
The team's log
The owner and admins see everything Alwen did in the team: what it saved to the shared vaults and through which tool, its answers in team channels, every step of the work it handed to agents, and who joined, left or changed what. On Business it downloads as CSV or JSON. Teammates' own vaults and private chats stay out of it.
Which tools read each vault
On Business, choose for each vault: every tool, or only the ones you tick (Claude, Cursor, Slack and so on, your own tools, any other). Your own vault on Tools, each shared vault on the Team page. An agent Alwen hands a job to reads that job's vault while it works, and the dashboard always shows it.
A smaller plan
Nothing is deleted. What the smaller plan doesn't include pauses: shared vaults beyond its count stop taking new ones, tools beyond its count say why they're paused, and your own tools wait for Business.