🌐 deepsource.io → deepsource.com

“Knock, knock!”

“Who’s there?”


deepsource.io, who?!” :eyes:

I’m excited to announce that we’ve migrated our primary domain to deepsource.com. All of DeepSource’s services which are available on .io are now redirected to .com, including our homepage, dashboard, docs, and the public API.

As we continue to grow our business and serve some of the largest enterprises on our code health platform, this is an important step in strengthening our brand with a more recognizable and trustworthy TLD. So long, .io!

deepsource.io → deepsource.com

How does this affect you?

  • As a user of DeepSource Cloud or Enterprise Cloud, the migration is 100% graceful. You will be redirected to the new domain automatically if you’re still using the old domain, with a HTTP 301 Moved Permanently response. You will, however, be required to log in again so we can set those new cookies properly. :cookie:

  • We’ve also now serving the dashboard on app.deepsource.com. So if you have a GitHub team with login acme-corp connected to DeepSource, you’ll now be automatically redirected to app.deepsource.com/gh/acme-corp, instead of deepsource.io/gh/acme-corp.

  • If you’re consuming our public API, the old endpoint at api.deepsource.io will continue to work as expected without any redirects. However, we recommend updating the endpoint to api.deepsource.com.

  • If you’re a customer of DeepSource Enterprise Server, this change doesn’t affect you in any way.

If you have any questions related to the migration, please comment on this post or reach out to our support. We’re happy to help!