Logto adopts token-based authentication following the OAuth 2.0 and OpenID Connect standards. Each authentication or authorization request results in Logto issuing tokens that represent the user’s authentication or authorization status — such as access tokens, ID tokens, and refresh tokens.

For billing purposes, only access tokens are counted (ID tokens and refresh tokens are excluded).

MAU-based billing charges per unique user per month, regardless of activity. Token-based billing instead charges by actual usage: every time an access token is issued.

Token-based billing represents true pay-as-you-go pricing. Unlike MAU-based models that charge for the entire month regardless of usage, you only pay for actual authentication and authorization activities. This approach is budget-friendly for low-frequency users who only access your product occasionally, as they generate fewer tokens, resulting in lower costs compared to flat MAU pricing. This makes Logto more cost-effective than competitors, especially for applications with varied engagement patterns.

For example, one sign-in may consume 1 access token. Using features like M2M or Organizations can generate additional tokens. To keep track, Logto provides real-time token usage monitoring in Console > Dashboard, which helps you better understand the relationship between MAU and tokens for your specific project.

When considering a downgrade to a lower-tier plan, it's important to ensure that you meet certain criteria before making the switch. Once you meet these criteria, you can proceed with the downgrade.

It's worth noting that both downgrades and upgrades take immediate effect. Your quota will be immediately shifted to the Free plan quota. Your base price will be adjusted proportionately, and any refunds owed to you will be deducted from your current bill.