bitdrift
Agentic mobile observability for engineering teams
About bitdrift
bitdrift is observability built for mobile, and its most consequential decision is commercial rather than technical. Traditional logging platforms charge by volume ingested, which quietly trains teams to log less. That is exactly backwards: the logs you did not capture are the ones you need when a crash only reproduces on one device model in one country. bitdrift charges by unique monthly active applications instead, and states plainly that there are no overages and no log limits, which removes the incentive to under-instrument.
The mobile focus is the other half. Mobile is where observability is hardest, because you cannot SSH into a user's phone, you cannot reproduce most crashes, and the release cycle runs through app store review so a fix is days away rather than minutes. The platform covers crash reporting, performance monitoring, session replay on higher tiers, and workflows that trigger on conditions you define. The free tier is unusually substantial for this category: five users, 100,000 crash reports a month across unlimited devices, 50,000 active applications a month of basic performance monitoring, 14 days of retention, three custom workflows and Slack alerting. That is enough to run a real small app rather than a token trial.
Instrument your mobile app with the SDK and telemetry starts flowing. Crash reports arrive with the context needed to act on them, and basic performance monitoring covers the health metrics you would otherwise assemble by hand. Because billing counts unique active applications rather than log lines, the instrumentation decision is about what is useful rather than what is affordable, which is the point. Define workflows to react to conditions automatically instead of watching dashboards, and route alerts into Slack on the free tier or into PagerDuty and custom SLOs on Enterprise. Retention is 14 days on free and configurable above that. Higher tiers add session replay, custom dimensions, advanced performance monitoring, unlimited workflows, SSO and 24/7 support. The intended workflow is that a crash in production produces enough signal to diagnose without waiting for a user to describe what they were doing.
- •Priced Per Application, Not Per Log - No overages and no log limits, so instrumenting more does not cost more
- •Mobile-first - Built for the environment where you cannot reproduce the bug or ship a hotfix in minutes
- •Crash Reporting - 100,000 reports a month across unlimited devices even on the free tier
- •Performance Monitoring - Basic health metrics free, advanced monitoring on Enterprise
- •Session Replay - Available on Enterprise for reconstructing what the user actually did
- •Custom Workflows - Three on free, unlimited on Enterprise, reacting to conditions automatically
- •Alerting - Slack on free, PagerDuty and custom SLOs on Enterprise
- •Substantial Free Tier - Five users and 14-day retention, enough to run a small production app
- •Enterprise Controls - SSO, configurable retention, custom integrations and 24/7 support
Mobile engineering teams who have been rationing their logging to control an observability bill, which is most of them. The pricing model is the argument: if you have ever removed instrumentation to save money and then regretted it during an incident, this is aimed at you. The free tier is generous enough that a small app can run on it indefinitely rather than as a trial, which makes it easy to evaluate honestly. Teams shipping to a wide range of devices benefit most, since that is where unreproducible crashes concentrate. It is not a general backend observability platform, so if your problem is server-side tracing you want a different category of tool. Enterprise pricing is contact-only, so budget planning above the free tier requires a conversation.
Pricing
From $0/mo
- Free Tier$0/mo
- EnterpriseContact sales
From the vendor pricing page, 2026-09-19
