Based on the knowledge sources provided, Ory self-hosted does not support multi-tenancy. This information is clearly stated in the following source: [Ory Kratos Guides: Multitenancy](https://www.ory.sh/docs/kratos/guides/multi-tenancy-multitenant) states: "[Ory Network](https://console.ory.sh) is the only available option to have a multi-tenant Ory Kratos set up. It is not possible to self-host Ory Kratos as a multi-tenant service as its data model does not support this due to data, scalability, and operational complexity." This document explicitly mentions that multi-tenancy is only available through Ory Network and cannot be implemented in a self-hosted Ory Kratos setup.

Based on the information provided in the knowledge sources, multi-tenancy support is available in the Growth and Enterprise pricing tiers of Ory Network. Here's the breakdown: 1. Production tier: Does not support multi-tenancy. 2. Growth tier: Supports multi-tenancy. [Ory Pricing](https://www.ory.sh/pricing/) states: "Multi-Tenant Production Environments: $15.00 / tenant" 3. Enterprise tier: Also supports multi-tenancy. The same source confirms this feature for the Enterprise plan. It's important to note that multi-tenancy is not available in the self-hosted version of Ory, as mentioned in the previous answer. Only Ory Network offers this feature. The Growth plan starts at $850/month, while the Enterprise plan requires contacting Ory for custom pricing. Both of these plans include multi-tenancy support, allowing you to manage multiple tenants within your Ory Network environment.

To answer your question accurately, let's refer to the information provided in the Ory pricing documentation. Ory uses a metric called Average Daily Active Users (aDAUs) for their pricing model. According to the [Ory Pricing FAQs](https://www.ory.sh/pricing/): "Average Daily Active Users (aDAUs) measures the average number of unique users who engage with your product on a daily basis. It's calculated by dividing the total number of active users per day in a given month by the number of days in that month." This means that: 1. The count is based on unique users, not the number of accesses. 2. If the same user (identified by their email or other unique identifier) accesses your page 100 times in a day, it still counts as 1 daily active user, not 100. 3. 100 daily users would mean 100 different users (with different emails or unique identifiers) accessing your application on average per day. Additionally, Ory uses a fair pricing model based on aDAU (average Daily Active Users). As explained in the [Ory Network Workspaces and fair pricing with aDAU](https://www.ory.sh/ory-price-2024-dau-mau/#fair-pricing-with-adau) document: - A single 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. This model ensures that you're not overcharged for users who are not consistently active, and it smooths out usage spikes. So, to directly answer your question: 100 daily users in Ory's pricing context refers to 100 unique users accessing your application on average per day, not 100 accesses by the same user.

To calculate the average Daily Active Users (aDAU) for the scenario you've described, we need to use the formula provided by Ory. Let's break it down step by step using the information from the [Ory Network Workspaces and fair pricing with aDAU](https://www.ory.sh/ory-price-2024-dau-mau/#fair-pricing-with-adau) document. The formula for calculating aDAU is:

Total number of active users per day in a given month / Number of days in that month

For your example: - Day 1: 100 users - Day 2: 600 users - Day 3: 50 users Let's assume these are the only days in the month with activity (to keep the calculation simple). Here's how we would calculate it: 1. Sum up the total number of active users: 100 + 600 + 50 = 750 total active users 2. Divide by the number of days in the month (let's assume a 30-day month): 750 / 30 = 25 aDAU So, for this example, your average Daily Active Users (aDAU) would be 25. It's important to note that this is a simplified calculation. In reality, Ory would calculate this over an entire month, including days with zero activity. The actual formula smooths out usage spikes and ensures you're only billed for consistent, genuine engagements. Remember, as stated in the pricing FAQ: "This approach smoothes out spikes in user activity and only bills you for consistent, genuine engagements rather than erratic peaks like with Monthly Active Users (MAUs)." For accurate billing and detailed calculations, you would need to track daily active users for an entire month and then apply Ory's pricing model to determine the final cost.

Yes, one Ory account can provide authentication for multiple apps. This capability is part of Ory's multi-tenancy and multi-brand features. Let me explain based on the information from the knowledge sources: 1. Multi-tenancy: Ory Network supports multi-tenancy, which allows you to manage multiple applications or brands within a single Ory account. This is mentioned in the [Ory Pricing](https://www.ory.sh/pricing/) page, where it lists "Multi-Tenant Production Environments" as a feature available in the Growth and Enterprise tiers. 2. Multiple domains: The [Ory Network GitHub issue on Bring Your Own Domain](https://github.com/ory/network/issues/16) discusses the ability to use custom domains for different applications. A comment by an Ory team member states: "In that case you would run Ory on a subdomain (e.g.

<http://auth.example.org|auth.example.org>

or

<http://ory.example.org|ory.example.org>

) and your primary app on the TLD or also a sub-domain". 3. Multiple brands: The [Ory Kratos Bring-your-own-ui documentation](https://www.ory.sh/docs/kratos/bring-your-own-ui/configure-ory-to-use-your-ui#multiple-custom-domains) provides an example of how one Ory project can serve multiple brands or applications: "With the Multibrand feature enabled for your workspace, you can add multiple custom domains to each Ory Network project. You can add a different custom UI base URL of each of the custom domains registered in the project. This allows for a high degree of flexibility, where each of the domains serves its own set of UI views that have a common path makeup but different base URL." 4. OAuth2 and OpenID Connect: Ory also supports becoming an OAuth2 and OpenID Connect provider, which allows you to provide authentication services for multiple applications. As stated in the [Ory OAuth2 and OpenID Connect documentation](https://www.ory.sh/docs/oauth2-oidc#use-cases): "Federated identity: Become an identity provider, authenticate users, and provide access to applications just like Google, Facebook, or GitHub." These features combined allow you to use a single Ory account to provide authentication for multiple applications, each potentially with its own branding, domain, and user interface. Remember that some of these features, particularly multi-tenancy, are only available in certain pricing tiers of Ory Network, not in the self-hosted version.