To complement Aurélie’s points, one of the questions you should ask yourself essentially is: where is you build pipeline (your Continuous Integration environment) currently running? (independently from SonarQube/SonarCloud)
- If your whole toolchain is already using online services (e.g. GitHub+Travis, or Bitbucket Pipelines, or Azure Pipelines online) then it likely means SonarCloud is a good fit (you’ll be leveraging native integrations we offer with these online tools, and wouldn’t have to maintain an on-prem installation when you’re used to consuming online services).
- If you build/test/package your application(s) on-prem, than fitting in an on-prem product like SonarQube likely makes more sense, as you’d likely want to avoid having a CI setup that spans across on-prem and cloud, with all of the technical considerations that this might imply (e.g. firewalls, NATs etc.).
A quick note too, to make it very clear from a static code analysis benefit point of view engine: SonarCloud runs the same Static Code Analysis engine as SonarQube Developer Edition.
Totally agree with Aurélie that, should you have any specific requirement/doubt, contacting SonarSource directly is a good way to clarify things (as was opening this topic in the first place). Mid-term our Product Marketing folks are also working on having clearer guidance available online to guide through our product offering.
Whatever best fits your needs, enjoy the product!