Frequently Asked Questions

Which languages do you support?

Refer to the list of supported analyzers for the complete list of supported analyzers.

Which providers do you support?

GitHub Cloud, GitLab Cloud, Bitbucket Cloud, GitHub Enterprise Cloud, GitHub Enterprise Server and GitLab Server are fully supported. Support for Azure DevOps and Bitbucket Server is in the works.

Will I need to pay for my open-source projects?

No. Part of our systems are built on Open-Source software. DeepSource is and will be free to use for Open-Source.

What are the available modes of payment?

We use Stripe to process our payments. You can use a credit card to pay for both monthly/yearly plans. If your invoice exceed 10,000 USD per month, we can invoice you manually. Get in touch with [email protected].

Is there a plan for students?

Yes! DeepSource is a part of the GitHub Student Developer Pack that offers $50 in credits which can be applied against any plan. For individuals, DeepSource is free to use for unlimited public and private repositories. More details here.

Do you have plans for non-profit organizations?

After signing up, write to us at [email protected]. We will evaluate and grant applicable credits to your account on a case by case basis.

Why do you require write permission for a single file?

When granting permissions, we request access only to a single file — .deepsource.toml. We can't write to any other file with this permission except the pre-defined .deepsource.toml. We are working with providers like GitHub to make this clearer on their installation page.

How do I block PR merges until DeepSource checks pass for BitBucket?

Under Repository Settings -> Branch Permissions, add new and select "Check the last commit for at least 'N' successful builds and no failed builds":

Add new branch permission

Feedback/bugs/suggestions

You've got a bunch of options.

We constantly monitor these channels and will get back to you as soon as possible.

License Glossary