From reading the blog article about multitenant it seems like GrandNode is not multi-tenant because you have to run an instance per tenant.

To create a "Tenant" during the registration process, the registration would ask for a unique tenant id. This id would be either directly or indirectly use the id as the directory to run the instance against. Then you would launch the instance and execute the installation page. Then when the site launches it would have to launch one or more instances per tenant.

GrandNode is no longer a multi-tenant app. It is a shared codebase solution that is not truly scalable. With under a couple of dozen tenants that is fine. But thinking Shopify scale no thank you. The company would go bankrupt due to running multiple instances of everything. At the launch of our alpha, we have 50-100 tenants. By the end of the first year conservatively we will be at several hundred if not thousands of tenants.

Am I missing something?

Hi,
There are many ways to implement Multi-Tenant applications.
Each type of multi-tenant architecture has advantages and disadvantages.
Our Multi-tenant Database Architecture uses one database instance per tenant. This technic is most costly but it complies is security, it is the best for performance, scalability, and data isolations.

I actually have no problem with the databases being separate. The problem I have is each tenant has to have their own instance or instances.

I actually have no problem with the databases being separate. The problem I have is each tenant has to have their own instance or instances of the website running.

Yes, every tenant has their own instance of the application, but every tenant uses the same application files.
This type of architecture provides the following benefits:
- Increasing resources is easier for a customer because only its infrastructure will need to be modified. We will be able to allocate more CPU, RAM or storage according to their needs.
- If an instance fails for some reason, this issue will not affect all of your customers
- Since there is only one infrastructure, it is easier to maintain
- Updates will only be done once so that they will benefit all of your users.
- This choice of architecture is less cost-effective

Your app is no longer able to scale. Sadly we will have to find a different e-commerce component for our SAAS platform.

Please check this plugin: https://grandnode.com/multi-tenant-ecommerce
you can also read post on our blog: https://grandnode.com/the-ultimate-guide-to-building-saas-ecommerce-platform-multi-tenancy