The member that remembers, for a team
The open-source member runs on your laptop and remembers one person’s work. That is exactly right for one person, and exactly wrong for a company — where the person who knows the codebase best is the one who just went on holiday. AI Member Cloud gives that memory to the whole team: organisations, roles, invitations and API keys, with every team’s work walled off from every other.
Amethyst — one person’s memory, held for a team
Everything a team needs around it.
How the member remembers does not change — that is the open core, unchanged. This is what has to exist once more than one person is involved.
One memory, the whole team
Everyone works with the same understanding of your codebase, instead of each person building their own from scratch and losing it when they change laptops.
Teams, roles and invitations
Invite people, give them what they need, and let finance see the bill without seeing the work. Four roles, which is enough to run a company and few enough to explain.
Your work stays yours
Your organisation’s memory is walled off from every other organisation on the service — enforced underneath, not left to anyone remembering a filter.
Access ends when you end it
Remove somebody and it takes effect immediately, not whenever their login happens to expire. The person who left this morning is already out.
Keys that belong to the team
An API key acts for the organisation rather than for whoever created it — so it keeps working after they leave, and never quietly carries their access with it.
Two-factor, when you want it
Available per account and off by default. A security upgrade you offer your team, not a wall everyone has to climb on their first morning.
No lock-in, no surprises.
The awkward questions, answered before you have to ask them.
Built on the open core
The member doing the remembering is the same open-source one you can run yourself, and improvements to it reach the hosted service automatically. You are not on a fork that quietly drifts.
Nothing trains on your code
Your codebase and your conversations are yours. They are not a dataset, not a training set, and not a product we sell to anybody else.
Leave whenever you like
The core is AGPL and self-hosting it is a real option, not a bluff. If the hosted version ever stops earning its keep, the exit is already built.
Prefer to keep it on your own machine? Then do — that is what the core is for. ai-member is open source, runs on your computer, and remembers one person’s work with no account and nothing leaving the box. The Cloud is what you reach for when the memory stops being one person’s.
Give the memory to the whole team.
An organisation, the people in it, and keys that belong to the org rather than to whoever happened to make them.