Skip to main content

Should I create separate Sentry projects for my frontend and backend?

Issue

I want to know whether my frontend and backend can share the same DSN, and whether they should. I am deciding between one shared project and a separate project for each service.

Applies To

  • All SaaS Customers and Self-Hosted Users

  • Projects

Resolution

Yes, create a separate Sentry project for each service, such as one for your frontend and one for your backend. A DSN (Data Source Name) belongs to a single project, so sharing one DSN means both services report to the same project.

Separate projects, each with their own DSN, are the recommended approach because they:

  • Give each event a clear origin, which makes troubleshooting easier.

  • Let you set the correct platform per project, for example React for the frontend and Django for the backend. Each platform tailors the Sentry UI and features, which a single shared project cannot do for two different platforms.

To trace requests from your frontend to your backend across these separate projects, use distributed tracing. See the Sentry tracing documentation.

Did this answer your question?