kumo and Sentry
What a studio uses Sentry for, where it lives in kumo, and what stays different.
Sentry, in its own words
Sentry sells application performance monitoring and error tracking: errors, logs, replays, tracing, profiles and metrics linked by one trace, with an AI debugger.
From Functional Software's page, read on 18 October 2026.
Where that work lives in kumo
What Sentry does that kumo does not
- Performance tracing, profiling, session replay and logs across web, mobile and server code.
- Symbolication and grouping at the scale of a large live service.
What kumo adds
- Each crash group becomes a bug on the board, tied to the builds that found and fixed it.
- Player feedback from Steam and Discord proposed as bugs in the same place.
- Test runs, playtests and certification beside the bugs.
- kumo's own receiver for Unreal's crash reporter, for a studio with no crash service.
Moving over
Keep Sentry: connect it, and kumo's Bugs page stays in step with it, merges included. A studio without it can use kumo's own crash receiver.