
The Kotzilla SDK captures app startup, screens, ANRs and crashes on real devices, with the components behind them. In a Kotlin Multiplatform app, the same SDK in your shared code also covers the iOS, Desktop and Web targets.
Built for mobile from the first line: app startup, ANRs, crashes, the main thread and low-end devices. Each event is tied to the component, the thread and the screen it comes from.
App startup
Cold and warm starts, up to the first frame. Launches from a push notification are classified correctly, and a crash during startup is reported on the next launch.
Screens and ANRs
Render times for Compose with Navigation 2 or 3, screens outside navigation, Activities and Fragments, plus main-thread blocks and ANRs with the component behind them.
Crashes on every target
Android crashes, plus iOS, Desktop and Web crashes in Kotlin Multiplatform apps, symbolicated with the full Kotlin stack trace and matched to each build’s mapping file.
Starts before your app code
Early start boots the SDK before Application.onCreate on Android and before main() on iOS targets, so slow startups are caught early.
Data volume under control
Choose the share of sessions you capture in production, and turn data collection on or off per app version, so costs stay predictable.
Consent built in
With consent mode on, the SDK starts at launch but sends nothing until your app records the user’s consent. No consent, no data.
Works with any DI
Koin, Hilt, Metro, Dagger or manual DI. With Koin, you also get the dependency graph and the resolution time of every component.
Release gate in CI
A Gradle task builds a performance and stability report at the end of your build, and can fail it when an issue crosses your threshold.
Safe by design
The SDK is built not to crash your app, and a failed mapping or dSYM upload never fails your build, so monitoring stays out of your way.
Ask your AI agent, use the IDE plugin, or follow the guide in the Console.
Ask your agent
With the Kotzilla MCP Server connected, ask it to register your app and set up the SDK.
Review the changes
The agent updates your version catalog, adds the Gradle plugin, creates kotzilla.json and, in a Koin app, adds the monitoring() call. You review every change.
Run your app
The first session appears in the Console within minutes.
Your AI agent
kotzilla MCP connected
> Register my app on Kotzilla and set up the SDK
✓ Read the project structure: package name and app type
✓ Registered the app on the Kotzilla Platform
✓ Applied the SDK changes: version catalog, Gradle plugin, kotzilla.json
✓ First session received from your app

Laurent Paquot
Senior Android Engineer @Worldline
“Enabling the Kotzilla SDK in the release build made a big difference. It’s night and day.”
2s+
startup time saved on low-memory devices at Canal+
78%
fewer ANRs at Bankin’


