Monthly Active Users & Limits
How Abrova Auth counts monthly active users, the free 1,000 a month, what users above that cost from your wallet (10,000 Toman per 1,000), what happens when the wallet is empty, and the daily limit on new anonymous users.
Abrova Auth is paid by monthly active users (MAU): the number of different users who signed in or renewed a session during a calendar month. A user counts once per month, however many times they open the app and on however many devices.
What counts#
A user is counted the first time in a month (UTC) that they:
- sign in with any method, including anonymous sign-in and linking a method, or
- renew a session (the SDK does this in the background about once an hour while the app is used).
Everything else is free: reading the current user, calls to other Abrova products with the token, sign-out, account deletion. A user who installs your app and never opens it again in the next month is not counted that month.
Free every month, then from your wallet#
| Free every month | Above that | |
|---|---|---|
| Monthly active users | 1,000 | 10,000 Toman per 1,000 users, from your wallet |
| New anonymous users per day | 200 | Daily cap: no more new anonymous users that day |
| Sign-in methods | All 6 | Included |
| Activity log | Included | Included |
There is no plan or subscription. Abrova bills from a prepaid Toman wallet: you top it up when you like, and usage above the free allowance is taken from it. See the pricing page.
At the limit#
With money in your wallet
Nobody is refused. Users above the free 1,000 are paid from your wallet at 10,000 Toman per 1,000. You see the month's count under Abrova Auth › Overview.
When the wallet is empty
When 1,000 users have been active this month and the wallet cannot pay for more, a new user of the month cannot sign in: the call fails with MAU_LIMIT.
- Users already counted this month keep working: they sign in and renew their sessions as usual.
- A user who is refused keeps their saved session. It works again on the 1st of next month, or as soon as you top up the wallet.
- Nothing is deleted: your users and settings stay as they are.
Show a friendly message for MAU_LIMIT ("Sign-in is unavailable right now, please try again later"). Your users cannot fix it; you can, by topping up the wallet.
New anonymous users per day#
Separately from MAU, a project can create up to 200 new anonymous users a day. This stops bots from filling your user list (and your MAU count). You can set a lower limit under Abrova Auth › Settings › Anonymous users.
Over the limit, signInAnonymously() fails with RATE_LIMITED and a retry time. Users who already exist are not affected, and other sign-in methods keep working.
Keeping the count honest#
- Do not create a new anonymous user on every start. Check for a signed-in user first; the SDK restores the session at start.
- Abandoned anonymous users are removed after 90 days without use (adjustable). They stop being counted the month after they stop using the app anyway.
- One user per person. Link a sign-in method to an anonymous user instead of creating a second user. See Anonymous users & upgrading.
Daily active users, new users and how many come back are in Usage insights (turn it on per project).