I worked closely with Accenture for a few years. They are not a development company. They outsource the development work and get huge margins on these kinds of projects by paying cheap wages to developing countries. They are an extremely expensive middle man. They sell people on their "process" (agile, etc) but those of us on HN know how much that's really worth (hint: not $33M).
A major part of the success of open source has been the fact that companies have the option to fork/tweak/sell the code. MongoDB has benefited from this as much as anyone. They gained the adoption levels they have now by advertising these exact benefits. Only later did they decide you need a commercial license to provide it as a service. How many companies would have thought twice about using MongoDB had they thought they would eventually have to pay for it and/or couldn't monetize it themselves?
You don't need a commercial license to provide SSPL code itself as a hosted service if you release the service-rigging code you use to do so.
As for the most typical use case, web apps, see their FAQ:
> The copyleft condition of Section 13 of the SSPL applies only when you are offering the functionality of MongoDB, or modified versions of MongoDB, to third parties as a service. There is no copyleft condition for other SaaS applications that use MongoDB as a database.
Compare their prior, public clarification on the scope of AGPLv3:
> Note however that it is NOT required that applications using mongo be published. The copyleft applies only to the mongod and mongos database programs. This is why Mongo DB drivers are all licensed under an Apache license. You application, even though it talks to the database, is a separate program and “work”.
Much as Kernel developers published a statement clarifying and limiting the sweep of GPLv2 copyleft, Mongo published a statement clarifying and limiting the sweep of AGPLv3 copyleft.
I've heard from a former Mongo employee that Mongo wrote several letters to users and vendors, assuring them that AGPLv3 didn't require release of their app code.
Amen to this... "You will get many ups and downs on your way — A new feature might have a significant bug you haven’t noticed and it would cause some customers to quit. I recently experienced that but I would think it was a necessary process to make the app more reliable. You are not perfect. So is your product. Finish your work and see how it goes. Don’t be afraid."
Seriously misleading headline. They didn't vote to replace him at all. They voted to add another executive (A COO). He would have remained CEO. Also, the vote failed.