I have spent a couple of weeks evaluating SonarQube 6.2 for my organisation. We are fully on .NET with hundreds of ASP.NET MVC, WCF, Web API and Windows Service applications and a few million lines of code. We have a legacy of 10 years of code. During those years we have made migrations to newer versions of the .NET framework, different source control systems, different message queues and different architectures. Migrations to new technologies can be expensive with that much code, and bad decisions can be costly to undo and when you realise you have a bad decision after you have finished integrating it into everything it becomes a nightmare.
So, taking that into account, I spent quite some time looking into SonarQube. For me personally, if it isn't a hell yes, then it's not the right thing.
SonarQube is a code quality platform, that integrates with various build systems and can analyse a bunch of languages. If you have multiple languages in your codebase, multiple build systems then the chances are that SonarQube can handle it.