diff --git a/develop-docs/sdk/philosophy.mdx b/develop-docs/sdk/philosophy.mdx
index 86f6ab37e7b9d..c5ea0f9c84471 100644
--- a/develop-docs/sdk/philosophy.mdx
+++ b/develop-docs/sdk/philosophy.mdx
@@ -5,6 +5,10 @@ sidebar_order: 2
 
 This document sets some general guidance for how to approach SDK development at Sentry. It should aid both internal and external developers to understand what motivations go into the design of the SDKs and why we're deciding in certain ways.
 
+## Trust is #1
+
+Sentry’s mission is to “Enable developers to ship with confidence” and their journey always starts with our SDKs. Above everything else, we need to make sure that our customers can rely on the stability of our SDKs because they depend on them. We are committed to having the most stable SDKs on the market and will own up to our mistakes with transparency and clarity.
+
 ## Dependencies Cost
 
 Dependencies come with a cost and that cost is high. Every dependency we use increases the surface area of the SDK and add more licensing, maintenance and security concerns. We understand that dependencies are necessary for supporting integrations, but dependencies must never be required for the base line functionality of an SDK. Obviously every rule also has exceptions and on some platforms we won't be able to work without a base level of dependencies. A good example is Python where we require an external library for HTTP requests to safely send HTTP requests.