Help me understand Domains, Applications and Plans

Q1: Relationship between Domains and Applications
Although the term “Domain” is not used anywhere in the Dashboard, it appears that it is the actual unit of licensing, based on this FAQ (https://www.algolia.com/doc/faq/accounts-billing/can-i-use-my-algolia-account-with-multiple-domains-sites-or-applications/).

My understanding from there is that multiple software applications of different types - say, a website, a console-based tool, and a mobile app - all associated
with data from the same website subdomain - say https://docs.example.com -
are all considered as one “Domain” (with uppercase D) and represented by one “Application” in Algolia Dashboard. Is this understanding correct?

If the site has a mobile version - say https://m.docs.example.com - which uses the same data and indices as above but is on a separate subdomain - does it
require a separate Domain with its own plan?

Q2: Limits on number of Applications
Trial plan seems to allow only one Application.
In the Upgrade plan page, Community, Starter and Pro plans mention “One Domain” in their limits sections, but don’t state anything about “Applications”.

How many maximum Applications are allowed under these plans?

Or, if my understanding in my previous question is correct - that each “Domain” is represented by an “Application” - it means the maximum number of
Applications that can be created in Community, Starter and Pro plans is also 1. Is this correct?

Q3: Relationship between Applications and Plans
Based on the Dashboard user interface, my understanding is that each Application under an account can have a different plan. For example, App1 can be on Starter and App2 on Pro. Is this correct? Or does a plan apply universally to all Applications under an account?

Q4: What does multi-user access mean?
The plans mention limits like “Multi-User Access (up to 4 users)”.
Does “user” here refer to collaborators in Dashboard > Team > Add Collaborator page?
Or does it refer to number of end users of the website, who type search queries?

Hi @pthbrk,

Q1: Relationship between Domains and Applications

My understanding from there is that multiple software applications of different types - say, a website, a console-based tool, and a mobile app - all associated
with data from the same website subdomain - say https://docs.example.com -
are all considered as one “Domain” (with uppercase D) and represented by one “Application” in Algolia Dashboard. Is this understanding correct?

They are one “Domain” if they are all from the same HTTP referrer, in this case https://docs.example.com. Also, as stated, we make an exception for a mobile app to be considered the same domain as a web app, if they happen to have separate HTTP referrers.

Whether they represent the same “Application” is not related to the Domains in any way. Think of an Application as the warehouse that stores your data. You can keep all your data in the same Application (the same warehouse), whether you use separate domains or not.

Q2: Limits on number of Applications

How many maximum Applications are allowed under these plans?

You can have as many Applications as you want. Each Application is a separate plan subscription. Therefore if you started 10 Applications, you would have 10 separate subscriptions.

So you can login with your email pthbrk@email.com to Algolia and have many Applications connected with that one account login.

it means the maximum number of
Applications that can be created in Community, Starter and Pro plans is also 1. Is this correct?

Please see above! You can have as many Applications as you wish.

Q3: Relationship between Applications and Plans

For example, App1 can be on Starter and App2 on Pro. Is this correct? Or does a plan apply universally to all Applications under an account?

Yes, each Application can be on a different plan.

Q4: What does multi-user access mean?

Does “user” here refer to collaborators in Dashboard > Team > Add Collaborator page?

Yes, this 4 user count includes you as the account owner + 3 Team collaborators. It is not the end user that types the search queries.

I hope this helps. To the extent you have questions about which plan might be best for you, please do not hesitate to reach out to support@algolia.com and let us know you’d like to talk with a team member about plan options!

@ajay.david, thank you for your help! Q2,3,4 are now clear to me.

For Q1, I’m still a little confused about some scenarios.

Assume that my data is a large searchable product catalog I have indexed in Algolia. And my business is a multi-tenant product catalog web app https://example.com where my customers can buy and customize their own subdomains - https://c1.example.com, https://c2.example.com and so on - each subdomain includes a product catalog search box .

I can create only one Application and one index, and route all queries from any subdomain to that single index. However, since each of my customers is a separate subdomain as well as separate legal entity, I assume that is a breach of Algolia’s licensing terms.

To conform to your licensing terms, I have to buy a separate plan per customer. And since a plan is scoped to an Application, it effectively means I have to create a separate Application per customer to be able to buy separate plans, even though the data is the exact same product catalog.

Doesn’t it imply that one licensed Domain corresponds to one Application in this case?

Hi @pthbrk,

Thanks for the clarification. In your situation, indeed, because each of these customers has a separate subdomain:

To conform to your licensing terms, I have to buy a separate plan per customer.

So in your specific situation, this is correct. To the extent you’d like to understand other options or you think you have a unique model that needs consideration, I’d invite you to contact support@algolia.com, reference this thread and begin a conversation with our account specialists about the plan that is best for you!

Thank you again for your help! My doubts are fully answered.

For context, I’m a search specialist writing a book on managed search services, and am researching Algolia’s offerings. Since I’m not a customer, I didn’t want to waste support’s time on research questions. Additionally, I think answers here would help other engineers who’ll evaluate Algolia, since they’re likely to have some of the same questions I have. I hope it’s ok if I approach this forum first for any other technical questions in future, and contact support only for in-depth details if required.