Hello, my company is evaluating how to proceed with Metabase deployment.
Our needs: we have developed a nutrition web-app that has a "stats" module for which (in demo) we already use Metabase (deployed on Heroku), and we're really satisfied with it. Since the app is almost ready to go in production, we are trying to figure out what's the best way to proceed for us, given that:
- (a) every client that will use the app, will have its subdomain (eg: client1.webapp.it, client2.webapp.it); alternatively, (b) we could use a single domain like metabase.webapp.it where each user logs in with their credentials to see the dashboard
- we want each user to be able to only see the dashboard associated to their account (however, only we can create new MB users and change their permissions)
- we want the users to be able to export the data from the dashboard: to do so I think I understood the user would necessarily needs to login, because it's not possible to do so from the public link
So my questions are:
- can we do all of this with a single instance of Metabase or do we need to have multiple instances? I think that with (a) we're forced to have multiple instances, but maybe with (b) we can only use one instance
- if we go with Metabase Cloud, do we need to pay 85$/month per instance of MB?
- if we decide to get an AWS/Azure machine, what would the recommended specs be to run MB without troubles? How do we scale these specs with the quantity of instances we need on a single machine? (like, do we just multiply the single MB instance requirements for the number of instances)
Thank you in advance