Plans & billing

auth.is is priced on usage, not features. Every plan includes the whole product — issuers, clients, federation, passkeys, key rotation, theming, and the full MCP surface. What you pay for is scale, measured in monthly active users (MAU). Start free, and move up only when your real usage says so.

Plans

Prices are set per workspace and can be adjusted by an operator, so treat the table above as the standard tiers rather than a contract — your Billing page always shows the plan and figures that apply to your team. The lowest overage rate rides with the highest tier: the more you grow, the less each additional user costs.

What counts as a monthly active user

An MAU is a distinct end user who has at least one token issued from one of your issuers within a UTC calendar month. We identify the user by the token sub, and we sum MAU across all of a team’s issuers for billing.

Two things deliberately do not count:

• Machine-to-machine traffic. A client_credentials grant has no user behind it (no sub), so it never adds to MAU. Rate limits, not MAU, bound M2M usage today.
• Repeat logins. The same user signing in ten times in a month is one MAU, not ten. The metric is distinct users per month, so it resets at the start of each UTC month.

Your month-to-date MAU is read from hourly usage rollups, so the number can lag live activity by up to about an hour.

Overage — billed monthly in arrears

On a paid plan there is no hard ceiling. If a month’s MAU exceeds your included allowance, the excess is charged at your tier’s per-MAU rate and appears on the next month’s invoice — you are only ever billed for users you actually had.

The Free plan is the one exception: with no card on file it has a genuine hard cap at 1,000 MAU. Add a card by moving to any paid plan and that ceiling becomes metered overage instead.

Changing plans

Plan changes are owner-only and always happen through an interactive login — for security, personal access tokens cannot change a plan.

• Upgrades apply immediately. The base fee is prorated for the rest of the current period, and the new tier’s full-month MAU allowance takes effect at once.
• Downgrades take effect next period. Moving to a cheaper paid plan is scheduled for the next billing period; your current allowance holds until then.
• Moving to Free schedules cancellation at the end of the current period.

You can change plans from the developer dashboard or by asking your AI assistant through the MCP (change_plan).

Checkout

Starting a paid subscription creates a secure checkout. The card form is always hosted by our payments provider (Paddle) — never inside auth.is, and never inside a chat. Whether you start from the dashboard or ask your assistant to run start_checkout, you receive a checkout link that the team owner opens in a browser to enter payment details.

After a successful payment, activation is confirmed by a webhook from the provider, so your plan may take a moment to flip to active on the Billing page. Payment details, receipts, and tax are handled by the provider as the merchant of record.

Invoices

Each closed billing period produces an invoice you can see on the Billing page and via the MCP (list_billing_invoices). An invoice records the period, the plan, the base fee, any overage (both the MAU count and the amount), and the total. Its status moves through:

Managing billing from your AI assistant

The MCP exposes the customer billing surface directly:

• get_billing — your current plan, month-to-date MAU vs. included, and estimated overage.
• list_billing_invoices — your invoice history.
• start_checkout — begin a subscription on a paid plan (returns a checkout link to open in a browser).
• change_plan — upgrade, downgrade, or move to Free.

Reads are available to any team member; start_checkout and change_plan are owner-only.