IANAL, but I guess this comes down to the interpretation of "Required Components". 1.12 "Required Components" means any text, programs, scripts, schema, interf

IANAL, but I guess this comes down to the interpretation of "Required Components". 1.12 "Required Components" means any text, programs, scripts, schema, interface definitions, control files, or other works created by You which are required by a third party of average skill to successfully install and run Licensed Software containing Your Modifications, or to install and run Your Derivative Works. You have to make the source of the required components available under the RPL (section 6.0-6.1). Would provisioning software to operationalize a database within a cloud environment be considered a "required component"? Maybe. If the cloud provider made modifications to the db source to get it to run well inside of their cloud environment, and did it in a way that made it impossible to run the modified db outside of their cloud environment, without using their custom provisioning scripts, then I would argue that those provisioning scripts would be considered "required components" under the definition in 1.12. But if they are able to run the db without making modifications to it, so that it is the same as upstream, and a third party developer does not need the provisioning scripts to run the modified db, then the provisioning scripts would not be considered required components. So, the RPL is perhaps stronger than the AGPL, but not strong enough for MongoDB or Redis Labs.