Getting Started

The following content provides guidance for SDK development at Sentry, helping both internal and external developers understand the motivations behind our design decisions.

Philosophy
The values that shape what we build - what makes a good SDK and the design tradeoffs we navigate around trust, compatibility, minimalism, and user impact.
Principles
These working principles govern how SDK teams collaborate, review, and ship. They build on the SDK philosophy, which governs what we build and how our SDKs should behave.
Standards
Enforceable rules, each with a defined automation/enforcement mechanism. Cross-SDK baseline with per-SDK overrides.
Playbooks
Step-by-step workflows for common scenarios. Each references the standards it operationalizes.
Templates
Shared resources used to standardize key documentation and process patterns across all SDK repos.
AI Tools
AI tools available for SDK development at Sentry — how they layer together and when to use each.

Was this helpful?

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").

How to contribute | Edit this page | Create a docs issue | Get support