Teams, plans & billing#
Everything in Tollan lives inside an organization. This page covers members and roles, plans and limits, usage metering, and how billing works.
Organizations#
An organization (org) is the tenant boundary. It owns your devices, routes, certificates, and billing, and it isolates them from every other org. Your first org is created when you sign up.
You can belong to multiple orgs (e.g. personal and work) and switch the active one in the console. Resources never cross org boundaries.
Members & roles#
Invite people to an org by email. Each member has a role:
| Role | Can do |
|---|---|
| Admin | Everything: manage members, billing, devices, routes, and org settings |
| Operator | Manage devices, routes, certificates, and access rules |
| Viewer | Read-only visibility into the org |
Admins send and revoke invitations; invitees accept via an emailed link and pick up their role on joining. The number of seats you can fill is a plan limit.
Plans & limits#
A plan defines what your org may use. Limits typically include:
- Devices — how many you can register.
- Routes — how many exposures you can create.
- Egress — outbound tunnel bytes per month.
- Seats — how many members the org may have.
- Custom domains — how many of your own domains you can attach.
Limits are enforced as quotas when you create resources: registering a device or route past your plan's limit is refused with a clear message until you upgrade. There's a Free plan to start, with paid tiers for larger fleets and features like custom domains.
Usage and quotas#
The relay meters traffic per device and pushes periodic summaries to the control plane, which rolls them up into your org's monthly egress. The console shows current usage against your plan so there are no surprises. Device and route counts are checked live against your quota whenever you add one.
Billing#
Billing runs through Stripe. As an admin you can:
- Start a checkout to subscribe or change plan.
- Open the billing portal to update payment methods and see invoices.
- View your org's transactions/invoices in the console.
Checkout-first purchase#
You can buy a plan before creating an account: pick a plan, check out with just an email, and you'll receive a claim link. Sign up or log in and claim the purchased org to attach it to your account. This lets you pay first and set up later.
How entitlements change#
Your plan and status are only ever updated by a verified billing event from the payment provider — never by a browser redirect. The source of truth for "what plan am I on" is the provider's confirmed events, so a bookmarked success URL can't grant an upgrade.
An org's status is one of active, trialing, past_due, canceled, or suspended.
Past-due & suspension (dunning)#
If a subscription goes past_due, Tollan enters dunning and service for that organization is paused until payment is resolved — at which point it resumes automatically. Nothing is deleted and you don't have to re-provision anything.
Audit log#
Admins can review an audit log of who did what and when — device and route changes, member and billing actions, certificate operations. It's immutable and useful for compliance and incident review.