New message text here

Ory calculates Daily Active Users (DAUs) in a unique way, using a metric called average Daily Active Users (aDAU). Here's how Ory calculates DAUs and aDAUs: 1. Daily Active Users (DAU): - A single user active on a given day counts as 1 DAU. 2. Average Daily Active Users (aDAU): - This is the metric Ory uses for billing purposes. - It's calculated by averaging the DAU over a 30-day period. Here's how the aDAU calculation works: - A user active daily counts as 1 DAU. - A user active once a month equates to 1 DAU / 30 days = 0.03 aDAU. - A user active five times a month equates to 5 DAU / 30 days = 0.167 aDAU. Ory provides an example of aDAU calculation in their [pricing documentation](https://www.ory.sh/ory-price-2024-dau-mau/#fair-pricing-with-adau): If your application has 1,000 DAUs for 29 days and a spike to 5,000 DAUs for one day, the aDAU is calculated as follows:

(1000 DAU * 29 days + 5000 DAU * 1 day) / 30 days = 1,133.33 aDAU

This aDAU model is designed to be fairer than Monthly Active Users (MAU) pricing, as it prevents spikes in usage from disproportionately affecting billing. It smooths out usage over time, providing a more accurate representation of your actual user activity. Ory claims that this pricing model can lead to significant savings compared to MAU-based pricing models used by some competitors, potentially saving customers up to 85% on their identity infrastructure costs.

Based on the knowledge sources provided, I can clarify how the Daily Active Users (DAUs) or more specifically, the average Daily Active Users (aDAUs) are applied in the Growth plan for Ory Network. According to the [Ory pricing page](https://www.ory.sh/pricing/), the Growth plan includes: 1. 2 production environments 2. 5 staging environments 3. 20 development environments However, when it comes to billing for DAUs/aDAUs, it's important to note that only the production environments are counted towards your usage-based billing. The staging and development environments are not included in the DAU/aDAU calculations for billing purposes. This is further supported by the information on [project rate limits in workspaces](https://www.ory.sh/docs/guides/rate-limits#project-rate-limits-in-workspaces), which shows different rate limits for Production environments compared to Staging and Development environments in the Growth plan. To directly answer your question: On the Growth plan, the DAU (or more accurately, the aDAU) is only applicable to production environments. Staging and development environments are not included in the DAU/aDAU calculations for billing purposes. It's worth noting that while staging and development environments don't count towards your billable DAUs, they still have their own rate limits and are included in your plan for testing and development purposes.

The $21 of included credits for usage-based features mentioned on the pricing page refers to a specific benefit of the Ory Network Production plan. Let me explain what this means based on the information from the [Ory pricing page](https://www.ory.sh/pricing/). For the Production plan, which starts at $70 per month, Ory includes $21 worth of credits that can be applied towards usage-based features. These usage-based features typically include: 1. Average Daily Active Users (aDAUs) 2. Machine-to-Machine (M2M) Tokens 3. Permission Checks The pricing page shows the following rates for these features on the Production plan: - Price per aDAU: $0.12 - Price per M2M Token: $0.007 - Price per Permission Check: $0.000090 The $21 of included credits can be used to offset the costs of these usage-based features. For example, you could use these credits to cover: - Approximately 175 aDAUs ($21 / $0.12 per aDAU), or - About 3,000 M2M Tokens ($21 / $0.007 per token), or - Around 233,333 Permission Checks ($21 / $0.000090 per check) Or any combination of these features up to the value of $21. It's important to note that these credits are included in your monthly subscription cost and do not roll over to the next billing period if unused. Any usage beyond these included credits would be billed additionally based on your actual consumption of these features. This credit system allows you to have a predictable base cost while providing some flexibility for varying usage patterns in your application.