How many applications and tenants can I have in FusionAuth?

dan · 12 Aug 2020, 15:30

I'm curious, how many applications and tenants can I have running in FusionAuth?

dan · 8 Dec 2020, 15:32

There are no hard limits in FusionAuth. If you use the community edition, you can have unlimited applications and tenants for free.

We've tested 100M users, but haven't pushed the boundaries of tenants or applications.

However, we have clients in production with 5,000+ tenants and 5,000+ applications.

ashutosh · 14 Aug 2020, 06:48

And What if all applications are pre-developed and you can still integrate with Fusionauth SSO? without disturbing their own sign-in processes?

dan · 14 Aug 2020, 14:21

I'm not quite sure I follow.

Do you mean using FusionAuth as the identity provider and connecting these applications using OIDC or SAML?

ashutosh · 17 Aug 2020, 05:58

My case is Thant I have 3 different application that i want to bring under 1 umbrella , out of 3 one is developed via MEAN stack and other 2 are PHP applications. Currently all 3 of them uses its own user login and registration system. I wish to have single sign on (like google uses for all apps) so user with one sign in can have access to all 3.

So my question is
1- can it be done with FusionAuth ?
2. if yes, in that case what about the existing login/reg flow already exist in 3 applications, do i have to get rid of them completely and than add fusionauth or let them sit as it is and fusionauth will provide another layer top of it?

And what will be best way connecting these applications using OIDC or SAML (i am not sure whats diffrence)?

Thanks

dan · 17 Aug 2020, 19:22

Ah, yes, thanks for explaining.

Yes
You have two options

use the API to integrate with the current login/reg flow with FusionAuth. This lets you keep your existing html pretty much untouched, you're just calling out to FusionAuth instead of the database.
remove them and use the FusionAuth provided pages with OIDC. This lets you use the theming and localization capabilities of FusionAuth, including super simple social signon.

It's your choice based on what your needs are, either way will work.

I'd only recommend using SAML if you have an application which only supports SAML, not OIDC.

You'll also want to make sure that when someone registers with one of your applications in FusionAuth, they register with all three. I'd probably use a webhook to ensure that.