# Sentry Developer Documentation We recommend going through the [engineering practices](/engineering-practices/) and our [development philsophy](/getting-started/philosophy/) before contributing a change to Sentry. [](/development-infrastructure/) ### [Development Infrastructure](/development-infrastructure/) [How to get your local dev environment up and running.](/development-infrastructure/) [](/backend/) ### [Backend](/backend/) [The monolith that is powering Sentry.](/backend/) [](/frontend/) ### [Frontend](/frontend/) [How we write frontend code.](/frontend/) [](/services/) ### [Services](/services/) [Running alongside the monolith.](/services/) [](/integrations/) ### [Integrations](/integrations/) [Connecting Sentry to other products.](/integrations/) [](/ingestion/) ### [Ingestion](/ingestion/) [Receiving and processing data.](/ingestion/) [](/sdk/) ### [SDKs](/sdk/) [Instrumenting user code.](/sdk/) [](/self-hosted/) ### [Self-Hosted Sentry](/self-hosted/) [How you can run all of Sentry on your own server, without paying anything.](/self-hosted/) You can also take a glance at the [Sentry Dockerfile](https://github.com/getsentry/sentry/blob/master/self-hosted/Dockerfile) for more information on how the Sentry server is configured, including its system dependencies.