Managing MAU Impact for FusionAuth Non-Production Environments

[wesley]

We have 5 FusionAuth environments: 4 dedicated to testing and development, and 1 for production. In the testing environments, we plan to run automated tests to register and log in users to verify functionality before deploying new code to production.

1. Does authentication activity in our non-production environments contribute to the Monthly Active Users (MAU) count used for billing?
2. If it does, what strategies can we use to run these tests without affecting our MAU totals?

[wesley]

1. MAU Billing in Non-Production Environments:
   Authentication activity in your non-production environments will not count toward your MAU billing as long as you are not using the "production" license key on those instances.
2. How to Ensure Testing Does Not Impact MAU Totals:
   • Use separate non-production license keys for your testing environments.
   • Ensure these keys are applied to your non-production instances, isolating them from your production MAU calculations.

For more information, refer to the following resources:

• FusionAuth Licensing Documentation
• What Makes a User Active?

This setup allows you to run comprehensive automated tests in your non-production environments without affecting your billing.