Difference b/w CodeScan Self-Hosted and CodeScan Cloud

Most of the differences between CodeScan Cloud and Self Hosted lie in the integration types and scanning options available.

Feature	CodeScan Self-Hosted	CodeScan Cloud
Requirements	Hosted SonarQube™ server	None
Branch Analysis	Requires SonarQube™ Developer edition	Yes
Reporting	Requires SonarQube™ Enterprise edition	Yes
GitHub Integration	Requires ARM/ Salesforce CLI and other CI tools	Yes
Bitbucket Integration	Requires ARM/ Salesforce CLI and other CI tools	Yes
Salesforce Integration	Requires ARM/ Salesforce CLI and other CI tools	Yes
Generic Git Integration	Requires ARM/ Salesforce CLI and other CI tools	Yes
480+ Included Rules for Salesforce	Yes	Yes
Custom Rules	Yes	Yes
VS Code/IntelliJ Plugin	Yes	Yes

On CodeScan Cloud, all scanning are done from the GUI. The tool integrates with your version control/Salesforce orgs to pull the metadata and scan it on our server.

On Self-hosted, the metadata collection and scanning are completed by an external scanner and pushed to the SonarQube™ dashboard. This can be accomplished with AutoRABIT's ARM, CodeScan’s Salesforce CLI plugin or SonarQube™’s own SonarScanner.

Your edition of SonarQube™ also limits the features. SonarQube™ provides a free and open-source version and multiple tiers of paid versions. Please ensure that the version you choose to use has the features you need.

Platform API endpoints are very similar but are also subject to the version and the edition of SonarQube™ you are using.

Note: SonarQube™ documentation can be found at https://docs.sonarqube.org and has information on current integrations and analysis options with a self-hosted installation.