Skip to content

Your MicroAuth plan ​

Each service is on its own MicroAuth plan, so a side project can stay free while your main product grows. You see and change it under Settings, MicroAuth plan. Sign in services and APIs have separate plans, and a service can only use plans of its own kind.

What each plan costs and includes is on the pricing page, and the plan picker in the dashboard shows the same.

Teammates belong to the workspace, not to a service, so everyone you invite can work on all of its services.

The user limit ​

When a sign in service reaches its plan's user limit, new sign ups wait: password sign ups, external sign in and invites all show a polite message, and owners and admins get an email once a day while it happens. People who already have an account keep signing in. The number of applications you can register is capped the same way. See Users.

When a sign in service moves to a plan without a feature it uses, that feature stops where it's configured. For example, a custom domain stops being served, an external provider the plan doesn't include stops showing on the sign in pages, and emails come from no-reply@microauth.com instead of your own domain.

The request allowance ​

This applies to APIs. The allowance counts every authenticated request the SDK reports, billable or not, including the test customer's. It runs per calendar month in UTC and resets on the 1st.

  • At 80%, workspace owners and admins get an email.
  • At 100%, they get another one, and the SDK answers 429 to new requests until the month resets or you upgrade.

The Overview tab and the platform_monthly_* fields of the snapshot show how much is left.

One Free service of each kind ​

Each person can have one API and one sign in service on the free plan, across all the workspaces they own, so a Free API and a Free sign in service don't get in each other's way. A service counts toward every owner of its workspace, so in a workspace with two owners, one Free API uses up the Free API allowance of both. Admins, editors and viewers don't count.

The rules below are written for APIs, and sign in services follow them too. When the allowance is taken, the Free service that has been on the free plan the longest keeps it, and the others of the same kind pause:

  • A new API starts paused. The dashboard warns you before you create it and takes you to the plan picker right after. It works as soon as it has a paid plan.
  • An API that moves to the free plan gets 14 days. That happens when its paid plan ends, when a failed payment isn't fixed in time, or when someone becomes an owner of its workspace. Owners and admins get an email saying when it will pause, and when a paid plan ended, that same email says so. If it still has no paid plan 14 days later, it pauses and they get another email.
  • The 14 days don't start over. If the API stops being over the allowance and goes over again within 30 days of its warning, it keeps the first pause date and nobody gets a new warning. If that date has passed, it pauses right away and they get the pause email. A paid plan in between gives it a fresh 14 days next time.

To bring a paused API back, give it a paid plan, or upgrade or delete the other Free API. It starts working again right away.

What a pause means ​

A paused API keeps its portal, customers, keys, balances and settings, and customers can still sign in. Only its requests stop: the snapshot reports a platform_monthly_limit of 0, and the SDK answers every request with 429 and Platform monthly request allowance exhausted. Since SDK 3.1.1 that answer names the start of next month as the reset time, with Retry-After, but the pause doesn't lift then.

A paused sign in service keeps its users, applications and settings, but refuses new sign ins and token refreshes, so your apps can't renew sessions once their access tokens expire.

Deleted Free APIs count until the month ends ​

When you delete a Free API, the requests it made this month keep counting toward the free allowance of each of its owners until the 1st. If it made 600,000 requests, the Free API that holds the allowance has 600,000 fewer for the rest of the month, and its full allowance again on the 1st. Requests from paid or paused APIs don't carry over.

The customer limit ​

When an API reaches its plan's customer limit, new sign ups on the portal are turned away with a polite message, and owners and admins get an email once a day while it happens. Existing customers keep working. The test customer doesn't count.

Changing plans ​

Admins change plans under Settings, MicroAuth plan:

  • The first upgrade goes through Stripe Checkout. After that, moving between paid plans changes the subscription in place, and Stripe prorates the difference.
  • Moving to the free plan ends the paid subscription right away. If an owner already has a Free service of that kind, this one pauses 14 days later.
  • Invoices and card opens the Stripe billing portal for your receipts and payment method.
  • After a transfer, the previous owner's plan runs until the period they paid for ends. Picking a plan starts your own subscription through Checkout, and a plan that costs the same or less starts charging on that date.

Free trials ​

Some paid plans come with a free trial, which the pricing page and the plan picker show on the plan. Picking one starts the trial through Stripe Checkout, which asks for a card, and the first payment is due when the trial ends. The plan's limits and features apply right away.

  • Each workspace gets one trial, and so does each card, across all of MicroAuth. A subscription that would be a second trial is canceled in Stripe before anything is charged, and owners and admins get an email saying why. The service keeps its current plan, and picking the plan again starts it right away without a trial.
  • MicroAuth plan shows when the trial ends, and owners and admins get a reminder 3 days before.
  • Moving to the free plan before then ends the trial, and you aren't charged.
  • Picking another paid plan during the trial ends it too. The new plan goes through Checkout and is paid right away.
  • A service that still runs on a plan carried over from a transfer gets no trial.

When an API moves to a plan without a feature it uses, that feature stops. A custom domain stops being served, for example, and your microauth.dev address keeps working. Customer teams keep their members, but nobody can invite new ones.

Custom plans ​

If you need limits the listed plans don't cover, contact us. We can set up a custom plan for your workspace:

  • It shows up in the plan picker of every service of its kind in the workspace, with a Custom badge, and owners and admins get an email when it's ready.
  • It isn't listed on the pricing page, and other workspaces don't see it.
  • You pick it like any other plan, and a paid one goes through Stripe Checkout. A custom plan at $0 doesn't count as your Free service.
  • If the offer ends, services already on the plan keep it. They just can't move back to it after switching away.
  • When a service is transferred to a workspace without the offer, a $0 custom plan stays behind and the service moves to the free plan.

When a payment fails ​

A failed renewal starts a 7 day grace period. The service keeps its plan, and owners and admins get an email to update the card. If the payment still hasn't gone through after 7 days, the plan ends and the service moves to the free plan's limits, and the dashboard says why. Users, customers, keys, balances and history are never deleted, and upgrading again restores everything. If one of its owners already has a Free service of that kind, it then has 14 days to get a paid plan before it pauses.

MicroAuth is a product of Zyref, LLC.