SonarQube Community Edition self-hosted versus SonarCloud for low-traffic private repositories

Objective

Reduce monthly cost for a low-traffic SonarQube deployment that analyzes private repositories by selecting either self-hosted Community Edition or SonarCloud.

Constraints and uncertainty

Community Edition has no license fee but requires a virtual machine, PostgreSQL, and search infrastructure. JVM heap and search resource requirements apply even at low analysis frequency, so a small instance may still exceed a minimal budget. SonarCloud removes server maintenance but charges private repositories by lines of code; its free tier is intended for open-source projects.

Assuming a current SonarQube LTS release and current SonarCloud private-project pricing, the cost break-even point is undefined. Data residency and available analysis features also differ between the two options.

Open questions

• Is self-hosted Community Edition cheaper than SonarCloud for a private repository below one million lines of code analyzed weekly?
• Can Community Edition run on an instance below documented minimum RAM without disabling search or degrading analysis quality?
• Which option fits a fixed monthly budget when scans are intermittent but must finish within a fixed window?