Billing and seats
What each plan includes, how seats are counted, and where to manage payment.
The Owner, Co-owners, and Billing admins manage billing from Settings → Billing — see Teams and roles. They are also the only people who see it: prices, the billing cycle, invoices, and the payment method. Every other member sees the plan and its seat counts, which is what feature gates and upgrade prompts need, and nothing about money.
What each plan includes
| Free | Pro | Team | Enterprise | |
|---|---|---|---|---|
| Prompt optimization | Yes | Yes | Yes | Yes |
| Usage history | Yes | Yes | Yes | Yes |
| AI fluency score | Yes | Yes | Yes | Yes |
| Inline coaching | — | Yes | Yes | Yes |
| Trail catalog | — | Yes | Yes | Yes |
| Personal insights | — | Yes | Yes | Yes |
| Context memory | — | Yes | Yes | Yes |
| Organization dashboard | — | — | Yes | Yes |
| Team leaderboard | — | — | Yes | Yes |
| Custom trail authoring | — | — | Yes | Yes |
| Organization context memory | — | — | Yes | Yes |
| API access for AI agents | — | — | Yes | Yes |
| SSO (SAML and OIDC) | — | — | — | Yes |
| SCIM provisioning | — | — | — | Yes |
| Audit log | — | — | — | Yes |
| Bring your own key | — | — | — | Yes |
| Governance | — | — | — | Yes |
Each tier includes everything to its left.
Seats
A seat is a member of the team who is not an external collaborator. On a plan that meters seats, the bill follows that count as people join and leave. On a contract with a fixed seat count, a pending invite holds a seat until it is accepted or expires, and an invite that was never accepted frees it again. Inviting several people at once needs a seat for each new or renewed invite that is not for an external collaborator; when the contract cannot hold them all, none of the invitations are sent.
External collaborators are never billed and never count toward a contracted seat count, however many of them a team has. They are on the roster, hold the roles they were given, and are left out of every seat number.
Removing someone frees their seat. Their historical activity stays in the organization's aggregate reporting — removing a person does not retroactively change what last quarter looked like.
Workspaces managed by a partner
Some workspaces are rolled out and paid for by a Joring partner, such as an AI-adoption consultancy. In that case the partner is Joring's customer, and the workspace is not billed by Joring at all.
What members of a partner-managed workspace see:
- Settings → Billing shows the plan, the seat counts, and who manages the workspace, with a way to contact the partner. There are no prices, no invoices, no payment method, and no plan comparison.
- Upgrade prompts and locked features say "Contact partner to add this" instead of linking to a pricing page.
- Seat limits, when the partner has set one, say "Contact partner to add seats".
To change the plan, add seats, or ask about an invoice, contact the partner. Joring staff can also end the arrangement, for example when a workspace moves to paying Joring directly: the workspace keeps its plan until an agreed date, then subscribes on its own from Settings → Billing.
The partner side of this is described in the Partner guide.
Bring your own key
On Enterprise, you can supply your own OpenAI or Anthropic API keys under Settings → LLM Keys, so coaching inference runs against your account and under your provider agreement. Keys are validated when saved and encrypted at rest. Because the key decides whose provider account processes the team's content, managing keys is reserved for the Owner and Co-owners, like encryption and data collection.
NextAudit logBilling and subscription changes are recorded.