Find a plan that is right
for you

While Large Language Models can speed up the development process, their main focus is in quantity, not quality. For DCM it's not that important whether the code was written by a developer or Copilot, it will still analyze the code to find possible bugs, style issues and other problems. If you want to maximize your productivity, you might want to use both.

Let's say you develop an app. If you have a multi-step release process, each time you introduce a bug might either result in the code being returned to you from a later step (delaying the time when users of your app get the feature you are working on) or the bug gets into the production and becomes a problem for your users leaving a possibility that the affected users may never use your app again. The latter is true even if you have a simpler release flow. That's why addressing different issues during development can save you a lot of time and keep your users happy.

Sadly, static analyzers are not perfect, which is why time from time you can get false positives. They are easy to suppress. For example, in the IDE you can add a comment with a rule ignore. Additionally, you can help us make the tool better for you and also report the problem to our support.

No. All analysis is performed locally on the end user's device. And any logs the tool produces are stored on the end user's device only.

No. Currently no account is needed to purchase a license.

You will receive an email with all the data needed to activate and use DCM both locally and on a CI/CD.

No, there is no limit.