How to correctly implement the CMS architecture for distribution according to the SaaS model?

Question

Software design

Good afternoon, I wrote a CMS and I want to distribute it using the SaaS model.
With the help of CMS, you can create business card sites, landing pages, stores.
How to properly and better organize the architecture? How critical is it to isolate clients from each other with docker containers?
I use Mongo Atlas as a database, each client has its own database (settings, templates, everything is stored in the database), the main question is: Is it advisable to use one copy of the CMS for all sites? I would like to use just such an approach, because. I believe that updating and maintaining the system will be easier this way than if you deploy a separate environment for each client.

Answer 1

Docker is not about saas. And the base should be one, there is a user entity, and the user has a project that can be a business card, a landing page or some other crap. There is only one base, if you share everything, then you alone will be unable to maintain this system.

Answer 2

It is not necessary to do multisite on a single instance.
It is also possible as a regular hosting with access only to the CMS instance. I would do that.
Stop pushing Docker onto the Lamp stack. There, at the user level, everything is perfectly resolved with rights.