The concern for me isn’t the thresholds, it’s predictability. As a small SaaS startup building on Directus, I’m not trying to avoid paying. When we reach the scale where a commercial license makes sense, we’ll pay it. Frustrating if some enterprises are currently not paying.
Awesome, thanks!
But the combination of a custom, unreviewed license and mandatory registration keys makes it harder to confidently build a long-term product on this foundation. Potentially having some features behind a paywall is scary too.
The license was reviewed by us and license attorneys.
The BSL had a community behind it. A bespoke license means the terms are whatever Monospace decides they are, now and in future revisions. That’s a different kind of risk than the financial thresholds themselves.
Curious, I know it helps to have so many people who have reviewed the license, but what does a community for a license do?
I said this several times, but being able to “change our license now or in the future”… that’s the same for every piece of software out there. The copyright holder can change license at any moment, so there’s no risk that’s any different here.
Most importantly: Publishing the actual MSCL text before asking for feedback would go a long way here. It’s hard to evaluate a structure without seeing the language. You’re just saying it’s ”better”.
Sure. Here’s the diff between FCL and MSCL: