682
Multi-tenancy
Aurélien Georget
It might happens that you're going to develop a website which includes a blog. It could be interesting to split the APIs into two different projets. However, it can be annoyed to deploy on two different servers for such a little API. That's why the multi-tenancy is interesting!
The multi-tenancy (or multi-projects) changes the architecture of an application to allow multiple projects in a single Strapi application. Each project is fully independent, you can use different databases, configurations, plugins, etc.
More details https://github.com/strapi/strapi/issues/1465
Activity
Newest
Oldest
Dean
sad that i've to leave my fav open source cms and go for paid one because of one feature
Vladimir Kudinov
This is the second top voted feature request. Why it still be ignored?
Leonardo Rojas
+1 on this
M
Mohammad Farahmand
yes it's so helpful for business application that has multi level account(for example B2B projects)
Kieran Harris
Yeah this would be great, as i need to run multiple regional accounts and can do this in other frameworks.
Marko Žmak - Pepe
Does anyone know what's the status of this feature?
We are considering moving our websites to another CMS and use it as our weapon of choice for new projects, Strapi is one of the candidates. But the Multi-tenancy feature is a must have, hopefully will be implemented in near future.
Derrick Mehaffy
Marko Žmak - Pepe: Currently we don't have any short to medium term plans to implement multi-tenancy it's still being considered but won't happen in the next 6 months for sure. (we don't know if we will build this feature or not)
madwyn
I’d welcome this feature.
Web agencies often use one VM to host many WordPress websites to save costs, as most small websites don’t generate much traffic.
Imagine using Strapi, it would be a waste of resources to run multiple instances of Strapi for different websites.
The case is more obvious if you run Gatsby for static sites, then only when editing the content or building the static sites need Strapi.
A multi-tenancy layer is great also for sustainability, thanks to the fact there will be less RAM, CPU and storage used for multiple websites.
There are other CMS systems providing this capability, e.g., webiny-js implemented a thin layer to isolate the tenants by a header, then each request is accompanied with a tenant ID.
I would prefer Strapi for its elegant design and better interface, but lacking multi-tenancy and ignoring the request since 2018 raised some concerns for me.
I also can understand if you have already made decision internally that you would not make this feature available in the open source version, but please let us know so we can make smart decisions.
E
Erick Barron
madwyn: +1 to this.
Personally, I wouldn't be against paying for this feature but we need to know if it will be implemented.