Billing, seats and leaving
What the subscription covers, the tiers, what happens when somebody leaves, and cancelling versus deleting the organisation.
Memtro is billed per organisation, by how many people are in it. One subscription covers the whole organisation and its admins manage it from Dashboard → Organisation → General, under Billing. Model usage is not part of it: you bring your own provider keys, so tokens are billed by your providers at their rates.
What you pay for
The price is set by the organisation's member count, admins included, and by nothing else. Connectors, jobs, memory, teams, API keys and saved chats are never counted. An organisation API key that acts as an agent is a member in its own right and takes a seat (agents as members); a key that acts as a person does not.
The billed quantity follows the member list. When somebody joins or leaves, the subscription's seat count is updated at that moment and the difference is prorated on the next invoice, so the bill tracks the organisation's size without anybody adjusting it.
The trial
A new organisation gets seven days free. The card is taken when the subscription is started, so the trial becomes a paid subscription on its own at the end of the week; a trial that reaches its end with no card on file is cancelled rather than charged. The General tab shows how many days are left and what the first charge will be.
Tiers
| Users | Per month |
|---|---|
| Up to 10 | $50 |
| 11–25 | $150 |
| 26–50 | $350 |
| 51–100 | $1,000 |
| 101–250 | $2,500 |
| 251–500 | $5,000 |
| More than 500 | Custom plan: sales@memtro.com |
Moving between tiers happens by itself as the member count changes. Above 500 users an organisation is on a custom plan: adding a member past that limit, or accepting an invitation that would, is refused with a note to contact sales. Organisations on complimentary access are exempt from the limit.
What the subscription's state means
- Trialing or active: everything works.
- Past due: the last payment failed. Access continues while Stripe retries the card; update it from the billing portal.
- Unpaid, cancelled, or a checkout that was never completed: the organisation cannot be used until a subscription is started again from the General tab. Its data is kept.
- Complimentary: no charge. Set by Memtro.
An API request for an organisation with no usable subscription is refused with a subscription_inactive error (HTTP 402) rather than answered, and the dashboard sends an admin to the subscription page.
Adding and removing people
Admins add members and send invitations on the General tab; an invitation also lets that address create an account on an instance that is otherwise closed to sign-ups. Roles, teams and what each member may do are described under Teams and permissions. Each addition and removal changes the seat count the same day.
When somebody leaves
Removing a member asks what happens to what they knew. Personal memory belongs to the organisation the person was in, so once their membership goes nobody could read it: not them, and not the organisation. Removal, done from the person's page, therefore makes the choice first:
- Hand it to a team: their working knowledge goes to the people who need it next.
- Keep it for the organisation: everybody reads it from now on.
- Erase it: it goes, and the receipt proves it.
The choice is carried out in its own transaction, with a receipt, before the membership is removed. A handover that fails removes nobody; a removal that fails after the handover leaves the receipt, which is recoverable.
The receipt sits with the erasure receipts under Organisation → Privacy, and an offboarding done by mistake can be put back from it: the memory returns to the person it came from, and their membership, role and teams are restored. Anything that has moved on since the receipt was written is left where it is and counted. The receipt is kept and marked undone rather than deleted.
Removal deliberately leaves alone the things a leaver owned that keep working: their connections and the tokens in them, their API keys, their scheduled jobs and their provider keys. They are counted on the receipt as flagged, so they can be dealt with from their own pages.
Cancelling versus deleting
Cancelling stops the money and keeps everything else. Cancel from the General tab, or from the Stripe billing portal, which also handles card changes and invoices. Access continues to the end of the paid period, or of the trial, and nothing further is charged; until then the subscription can be resumed with one click. After it ends the organisation and everything in it stay as they were, unusable until a new subscription is started.
Deleting the organisation is the other thing entirely, described next. Choose it when the organisation is finished with, not when you want a pause.
Deleting the organisation
The owner, and only the owner, can delete the organisation, from the box at the bottom of the General tab, by typing the organisation's name. Then, in this order:
- The subscription is cancelled at once. Nothing further is charged, and nothing is refunded for the remainder of the period. If Stripe refuses, nothing is deleted and the owner is told.
- Every member is signed out on every device, the owner included.
- Everything the organisation holds is deleted in one transaction: shared, personal and team memory, teams, members and invitations, connections and the credentials in them, provider keys, API keys and the agent identities behind them, jobs and their runs, chats, usage figures, allowances and receipts.
It cannot be undone, and the organisation's receipts go with it, so an erasure receipt somebody may need should be downloaded first.
What stays
- People's accounts. Members keep their sign-in, so they can create another organisation or accept an invitation to one. Their personal memory does not come with them: it belonged to the organisation.
- The Stripe customer and its invoices, as the accounting record of money that changed hands.
Nothing else.