I just want to say thanks for Metabase and the work you guys have put into it over the years. I've deployed the package at a number of organizations I've worked for and I've greatly enjoyed using it as a tool to teach people about self-serve data analytics.
I'm very much looking forward to the upcoming .41 release, but there's a few things I think you guys should consider.
First, for self-hosted products, please consider something other than a per-user-per-month fee. The whole point of self-hosted is that you can scale on your terms. I think you'll to push [otherwise honest] people to password share resulting in lost revenue. Instead, consider charging per-core. We'd gladly pay you $1000/mo per core or more if it meant no restrictions on users. Any business has to de-couple their expenses from their scaling plans in order to succeed. The "per-user" model is becoming a hinderance to that; with $10/mo for slack, $15/mo for jamf, $15/mo for MDM, $15/mo for email, in addition to payroll taxes, health insurance, etc, and it gets very expensive monthly to hire people.
Second, I would encourage you guys to do the following. This statement is from the .41RC release notes:
For Pro and Enterprise plans, Admins can now see all subscriptions and alerts set up in their instance.
I agree, I think this is an "Enterprise" level feature. Oversight is very important in larger organizations.
Plus, Admins in these plans can now restrict the domains to which Subscriptions and Alerts can be emailed.
This is a tad concerning. By running this software, you're essentially stating data exfiltration is a real possibility, and given the previous EE-only feature, you won't be aware it's happening. This doesn't give anyone confidence their internal secrets won't be leaked. I would encourage you guys to include this very basic control in the OSS Version.
Thank you for your consideration