Debug your mobile app
before users complain
Session replay, crash reporting, and network monitoring for React Native and Flutter — without recording video or storing sensitive data.
This month
1,247
sessions captured
83% of free tier
Sessions
247 sessions today
Avg duration
3m 12s
Crash rate
0.24%
API errors
1.8%
usr_a1b2c3
iPhone 15 Pro · iOS 17.4
usr_d4e5f6
Pixel 7 · Android 14
usr_g7h8i9
iPhone 13 · iOS 16.7
usr_j1k2l3
Samsung S23 · Android 13
NullPointerException in PaymentController
at com.myapp.payment.PaymentController.process(PaymentController.kt:142)
Everything included
One SDK. Complete visibility.
Stop piecing together logs, screenshots, and support tickets. BugsPulse captures everything you need to understand and fix bugs — in a single install.
Session Replay
Rewind any user session as a timeline of structured events — taps, swipes, navigations, and state changes. No video, no screen recording. Zero privacy risk.
Crash Reporting
Crashes grouped by stack fingerprint. See affected devices, OS versions, and get an AI root-cause summary for every group.
Network Monitoring
Full API waterfall per session. Spot the exact request that caused a crash or slow screen.
AI Crash Summaries
Plain-English root-cause analysis for every crash — what happened, who was affected, and how to fix it.
Root cause
Network timeout on POST /api/payment/charge exceeded 3s threshold, triggering an unhandled exception in PaymentController.
Affected
Pixel 7 devices on Android 14 with flaky 4G connections (23 sessions, 0.4% of total)
Fix suggestion
Add retry logic with exponential backoff and a user-facing timeout state in the checkout screen.
Privacy by Design
Built for GDPR, CCPA, and App Store privacy labels from day one. You control exactly what is captured.
- Zero keyboard logging
- No video or screenshots
- Passwords auto-redacted
- Zero cross-app tracking
- On-device event filtering
- Configurable retention
Product Analytics
Session volume, crash rates, startup latency, app version adoption, and device distribution — all in one dashboard.
Smart Alerts
Get notified when crash rates spike or new crash groups appear. Integrates with Slack and email.
Team Collaboration
Invite teammates, assign crash reports, and share deep-linked session replays. No VPN or special access required.
How it works
Up and running in minutes
No infrastructure to manage. No complex configuration. Install, init, and ship.
Install in under 5 minutes
One npm install, one init call. No native modules, no Xcode configuration, no CocoaPods magic. Works with Expo managed and bare workflows out of the box.
- Zero native code changes required for Expo
- Automatic crash handler registered on init
- Network interception starts immediately
- Works with React Navigation out of the box
import { AppRegistry } from 'react-native';
import BugsPulse from '@bugspulse/react-native';
import App from './App';
// One call — that's the entire integration
BugsPulse.init({
apiKey: 'bp_live_your_key_here',
environment: 'production',
captureTouches: true,
captureNetworkRequests: true,
captureCrashes: true,
});
AppRegistry.registerComponent('MyApp', () => App);Events captured automatically
Taps, swipes, screen transitions, crashes, and API calls are all captured as structured JSON events from the moment you call init. No manual instrumentation needed for the basics.
- Session replay events stream in real time
- Crashes captured with full symbolicated stack
- Network requests logged with timing + status
- Optionally attach user ID and custom context
// Optional: identify the user (opaque ID only — no PII)
BugsPulse.setUser('user_abc123');
// Optional: attach context to every event in this session
BugsPulse.setContext({
plan: 'pro',
appVersion: '2.4.1',
featureFlag_newCheckout: true,
});
// Manual business event tracking
BugsPulse.track('checkout_completed', {
amount_usd: 29,
coupon_applied: false,
});Debug in seconds, not hours
Every session is searchable in the dashboard. Open any crash, scrub the event timeline, inspect the full network waterfall, and read the AI-generated root-cause summary — all in one place.
- Timeline scrubber with tap, nav, and crash markers
- Side-by-side crash stack and session replay
- Network waterfall: URL, status, latency, size
- AI plain-English root cause + suggested fix
AI Root Cause
Network timeout on POST /api/payment exceeded 3s, triggering an unhandled exception in PaymentController.kt:142.
Event timeline — 3m 24s
Network requests
Why BugsPulse
Built for mobile, not bolted on
General-purpose error trackers weren't designed for mobile session replay. BugsPulse was.
Event-based session replay
BugsPulse replays structured events — no video, no privacy risk
Network waterfall per session
See every API call linked to the exact session that failed
AI crash analysis
Plain-English root cause, affected users, and fix suggestion
React Native + Flutter SDKs
Privacy — no PII by default
Video recording risks capturing passwords and payment info
Free tier
Integration time
SDK bundle size
Comparison based on publicly available documentation as of 2025. Feature availability may vary by plan.
Pricing
Simple, predictable pricing
Start free. Upgrade when you're ready. No surprise bills.
Free
For side projects and early-stage apps getting started.
- 500 sessions / month
- 7-day session retention
- Session replay
- Crash reporting & grouping
- AI crash summaries
- Network monitoring
- 1 project
- Community support
Pro
For production apps and indie founders who need real visibility.
- 50,000 sessions / month
- 30-day session retention
- Everything in Free
- Up to 2 projects
- 5 team seats
- Slack & email alerts
- Priority email support
- Custom event tracking
Growth
For scaling teams with high traffic and compliance requirements.
- Unlimited sessions / month
- 90-day session retention
- Everything in Pro
- Unlimited sessions
- Up to 4 projects
- 20 team seats
- Role-based access control
- Custom data retention
- Priority support < 4h SLA
No credit card required to start on Free.
Need custom limits or an enterprise plan? Talk to us
How does session replay work without recording video?
BugsPulse captures structured JSON events — taps, navigations, crashes, network requests — instead of recording pixels. The dashboard reconstructs the session from these events: animating touch ripples at recorded coordinates, showing screen transitions, and overlaying network calls on a scrubber timeline. No video file is ever created, so passwords, messages, and sensitive screens are never at risk.
Is BugsPulse GDPR and CCPA compliant?
Yes. BugsPulse collects zero personally identifiable information by default. Session IDs are randomly generated and never linked to device advertising IDs or real user identities. You can further restrict capture via SDK configuration. A Data Processing Agreement (DPA) is available for teams that require one.
Which mobile frameworks do you support?
BugsPulse has native SDKs for React Native (Expo managed, Expo bare, and plain React Native) and Flutter (Dart). Both cover iOS and Android. There is no web SDK — BugsPulse is intentionally mobile-only so it can provide deeper platform integration.
How long does integration take?
Most developers are capturing sessions within 5 minutes. For Expo managed workflow it is two commands: install the package, add BugsPulse.init() to your app entry point. Bare React Native requires an additional pod install for iOS. Flutter integration is similar — add the package, register the NavigatorObserver, and add the Dio interceptor if you use Dio.
What happens when I exceed my 500 free sessions?
Once you hit the monthly limit, new sessions are silently dropped until the next billing period. Existing captured sessions remain accessible for the full 7-day retention window. You can upgrade at any time from the billing page to restore capture immediately — there is no data loss for sessions that were captured before the limit was hit.
Can I export my data?
All session data is accessible via the REST API, so you can build custom exports or pipe data to your data warehouse. You own your data — BugsPulse does not share it with third parties.
How does crash grouping work?
Crashes are fingerprinted by normalizing the stack trace — stripping memory addresses and line numbers that change between builds — and hashing the result. Two crashes with identical root causes but different stack addresses land in the same group. AI analysis is run once per group, not per occurrence, so you always have a fresh explanation without burning extra compute.
< 5 min
to first session captured
< 5 KB
SDK bundle overhead
Zero PII
collected by default
Stop guessing. Start debugging.
Every minute a bug stays unfixed is a minute users churn. BugsPulse gives you the full picture — session replay, crash context, and network traces — so you can ship the fix today, not next sprint.