Multi-tenancy vs one single Nextcloud instance for a network of organizations

I have no support/technical question and have seen the support category. (Be aware that direct support questions will be deleted.)

on

Which general topic do you have

For a scenario in which you have a network of multiple organizations.
And each of these organizations has itself different workgroups (Teams works fine here)
And you want everybody to be able to communicate through Nextcloud Talk.

In one sense the ideal could be to have each organization have its own Nextcloud Instance (so we would need Multi-tenancy)

But that would isolate organizations from talking to each other.

The other scenario would be to have one huge Nextcloud instance with all the network organizations. But that would probably create too big and complex databases and could slow down the system?

What would you recommend?

thanks!

That depends how large it is and if you want a single server setup. There are large setups for universities and research organizations with thousands of users.

Having multiple smaller setups makes it easier to migrate between servers and if single units still fit on a server (vserver), you can start small, and if needed separate the setups. And also adjust the setups differently, if they need different apps and adjustments.

With federation, you can even share things between different instances, and I am not 100% sure, please check this, with talk this should be possible as well??

For resources etc., there was a rough number that you can manage ~100 users on a server. Then surely it depends which apps, how much they interact how many data everybody creates etc. E.g. for 5 organization with 100 users each, I’d directly try separate setups, with 5 organizations at 1-5 people, one instance is probably enough and managing 5 instances is not worth the effort.

If you setup is larger and your setup is part of a complex environment (external authentication backend, mail connection etc.), enterprise support might give you additional help to design a suitable setup, and have someone at hand if you have issues. But the community works as well, but you have to fiddle around yourself, exchange information with others, …

Thanks!
this makes sense
I think the best way for us will be to start with only one instance and put different organizations there just as teams, and also set up teams for specific teams within those organizations. (Ideal would be to have hierarchical teams but I guess that is not possible)

And then, if we ever get a lot of people, we’ll have to research about federation and multi-tenancy.

thanks @tflidd !!