Can I keep my existing Sentry SDKs?
Yes. urgentry keeps the existing Sentry SDK packages in place, so the first migration proof is a DSN change plus one real event through the current SDK.
Migrate and evaluate
Short answers. No scavenger hunt.
These are the questions new evaluators usually ask first. If you need the long version, the links below point straight at the guide that actually answers it.
SDKs stayStart with the existing Sentry SDKs and a DSN change.
Tiny firstUse Tiny mode when you want the fastest path to a working DSN.
Self-hosted laterUse self-hosted mode when you already need shared services.
Data staysTiny stays local. Self-hosted stays on your infrastructure.
When should I choose Tiny mode?
Choose Tiny mode when you want the fastest path to a working DSN, one-binary operation, and the smallest possible operator footprint.
When should I choose self-hosted mode?
Choose self-hosted mode when you already need shared services, split roles, and operator runbooks around backup, maintenance, and rollout safety.
Is urgentry source-available?
Yes. urgentry is source-available under FSL-1.1-ALv2, and the public repo links the license directly so the legal boundary is easy to inspect.
Where does the data live?
Tiny mode keeps product data on the local machine, and self-hosted mode keeps the data on your infrastructure without a phone-home product telemetry path.
Where do I look when something feels off?
Start with Troubleshooting, move to Support for public issue intake, and use Security when the problem should stay private.
Next docs
When the short answer stops being enough, jump straight into the guide that actually moves the work forward.