Question: How could I go into providing an unique CMS instance for each of my customers, in a SaaS multi tenancy scenario?
Hi! I've been playing with some SaaS ideas to develop, and all of then happen to fall under a multi-tenancy scenario, and I am having trouble figuring out some of the ways to fully implement this architecture.
I'll start providing the example: a webapp for showing restaurant's menu. Customers would go to myapp.com and upon registration, receive their own customer1.myapp.com, which would be the page displaying their menu. I've found that this frontend part requires a few sets of domain/dns configurations and it's doable. Even better, vercel has recently launched its "Platforms Starter Kit" which includes this config out of the box.
But for my case, I'd need a way for my customer to edit their pages, register their menu itens and so on.
I am familiar with headless CMS solutions like Strapi and Sanity.io, but I haven't found any native support of them for such scenarios.
Basically, upon every registration, the "backend" structure should all be generated automatically, creating a new cms instance that the user would deal with and affect only his own tenant.
I am currently not being able to wrap my head around what would it take to do so... and if there's any CMS that provide such support? Perhaps I will need to develop my own micro cms? And then attach it to a route on the tenants like customer1.myapp.com/admin...
Sorry for the long post, and if I couldn't be clear or more precise. Appreciate any input!
Top comments (3)
If I understand correctly, you are using certain products for CMS. Maybe you should include the names in the title and tags. Also you could summarize at the beginning, what you are currently using.
Is the frontend application your development? What about the backend application, is this some kind of product you are using?
Spam. The comma after ‘automatically’ is a link.
Any Idea?