# Everframe > In-app bug reporting for mobile, web and TV apps. An SDK captures a > screenshot, console and network logs, a breadcrumb trail and (where > supported) a session replay, packages them into a typed, signed "envelope", > and delivers it by webhook to your own tools or an optional dashboard. > On most platforms, uncaught errors and crashes also become reports on their > own, in the same envelope. > Operated by Scriptx, UAB (Lithuania, EU/GDPR). Contact: support@everframe.dev ## Structure The docs are per-SDK, not per-concept. These 1 topics exist for every SDK at /docs/{react|web|react-native|flutter|kmp|ios|android|roku|vega-os}/{topic}/: - install Not available for every SDK: - /docs/react/configuration/ (React only) - /docs/react/screen-tracking/ (React only) - /docs/react/breadcrumbs/ (React only) - /docs/react/session-replay/ (React only) - /docs/react/console-network/ (React only) - /docs/react/network-bodies/ (React only) - /docs/react/crash/ (React only) - /docs/react/screenshot/ (React only) - /docs/react/sensitive/ (React only) - /docs/react/redaction/ (React only) - /docs/react/identity/ (React only) - /docs/react/replies/ (React only) - /docs/react/branding/ (React only) - /docs/react/playback-tracking/ (React only) - /docs/web/configuration/ (Web only) - /docs/web/screen-tracking/ (Web only) - /docs/web/breadcrumbs/ (Web only) - /docs/web/session-replay/ (Web only) - /docs/web/console-network/ (Web only) - /docs/web/network-bodies/ (Web only) - /docs/web/crash/ (Web only) - /docs/web/screenshot/ (Web only) - /docs/web/sensitive/ (Web only) - /docs/web/redaction/ (Web only) - /docs/web/identity/ (Web only) - /docs/web/replies/ (Web only) - /docs/web/branding/ (Web only) - /docs/web/playback-tracking/ (Web only) - /docs/react-native/expo/ (React Native only) - /docs/react-native/configuration/ (React Native only) - /docs/react-native/screen-tracking/ (React Native only) - /docs/react-native/breadcrumbs/ (React Native only) - /docs/react-native/session-replay/ (React Native only) - /docs/react-native/console-network/ (React Native only) - /docs/react-native/network-bodies/ (React Native only) - /docs/react-native/crash/ (React Native only) - /docs/react-native/screenshot/ (React Native only) - /docs/react-native/sensitive/ (React Native only) - /docs/react-native/redaction/ (React Native only) - /docs/react-native/identity/ (React Native only) - /docs/react-native/branding/ (React Native only) - /docs/flutter/configuration/ (Flutter only) - /docs/kmp/configuration/ (KMP only) - /docs/ios/configuration/ (iOS only) - /docs/ios/screen-tracking/ (iOS only) - /docs/ios/breadcrumbs/ (iOS only) - /docs/ios/session-replay/ (iOS only) - /docs/ios/console-network/ (iOS only) - /docs/ios/network-bodies/ (iOS only) - /docs/ios/crash/ (iOS only) - /docs/ios/screenshot/ (iOS only) - /docs/ios/sensitive/ (iOS only) - /docs/ios/redaction/ (iOS only) - /docs/ios/identity/ (iOS only) - /docs/ios/branding/ (iOS only) - /docs/ios/session-vitals/ (iOS only) - /docs/android/configuration/ (Android only) - /docs/android/screen-tracking/ (Android only) - /docs/android/breadcrumbs/ (Android only) - /docs/android/session-replay/ (Android only) - /docs/android/console-network/ (Android only) - /docs/android/network-bodies/ (Android only) - /docs/android/crash/ (Android only) - /docs/android/screenshot/ (Android only) - /docs/android/sensitive/ (Android only) - /docs/android/redaction/ (Android only) - /docs/android/identity/ (Android only) - /docs/android/branding/ (Android only) - /docs/android/session-vitals/ (Android only) - /docs/roku/configuration/ (Roku only) - /docs/roku/screen-tracking/ (Roku only) - /docs/roku/breadcrumbs/ (Roku only) - /docs/roku/crash/ (Roku only) - /docs/roku/instrumentation/ (Roku only) - /docs/roku/identity/ (Roku only) Server-side material is single-copy under Reference — it is where the numbers live (limits, retention windows, error codes), and the per-SDK pages link to it rather than restating it. ## Reference (single copy, not per-SDK) - [The AI-ready envelope](https://everframe.dev/docs/envelope/): The exact schema of an Everframe report — the typed, signed envelope your receiver gets: SDK info, reporter input, captures, breadcrumbs and context. - [HTTP APIs](https://everframe.dev/docs/api/): Everframe has two HTTP APIs — the ingest API that SDKs submit reports to, and the v1 ticket API your own automation uses. - [Ingest API](https://everframe.dev/docs/api/ingest/): The Everframe ingest endpoint — bearer authentication, the multipart body, size and rate limits, the response shape, and every error code. - [Ticket API](https://everframe.dev/docs/api/tickets/): The Everframe v1 ticket API — API token authentication, creating tickets from CI or scripts, idempotency, rate limits, and error codes. - [MCP server](https://everframe.dev/docs/mcp/): Connect Claude Code, Codex, Cursor, VS Code or Zed to Everframe over MCP — browser authorization, report and crash context, and optional ticket creation and editing. - [Webhooks](https://everframe.dev/docs/webhooks/): Receive Everframe reports as signed webhooks — headers, HMAC-SHA256 verification, attachment download, retries, dead-letter, and the delivery circuit breaker. - [Server config](https://everframe.dev/docs/server-config/): How GET /api/config drives SDK behaviour at runtime — the feature gates, their payloads, and the client-veto rule that governs all of them. - [Symbols & source maps](https://everframe.dev/docs/source-maps/): How Everframe maps crash frames with dSYMs, R8 mappings, native libraries, Hermes and web source maps, and the build tools that upload them. - [Try on device](https://everframe.dev/docs/try-on-device/): Reproduce a bug report or crash on a live iOS simulator, Android emulator, Apple TV, Android TV or Roku from the dashboard: upload a runnable build from CI, then start a session next to the reproduction steps. - [Quick capture on real devices](https://everframe.dev/docs/quick-capture-devices/): Link a phone, Android TV, Apple TV or Vega OS device to yourself or your team, then file a draft report with a screenshot, replay and logs by shaking the phone or holding a remote key. - [Error triage & releases](https://everframe.dev/docs/error-triage/): How errors group by mapped source, register release order, mark issues fixed, and send regression webhooks. - [Errors & limits](https://everframe.dev/docs/errors/): Every limit the Everframe SDKs and APIs enforce, and every error code they return, with what to do about each. ## Learn Long-form guides at /learn/{slug}/, written for AI-search citation rather than product docs. Browse by topic at /learn/topic/{bug-reporting|qa-process|mobile-development|sdk-integration}/. - [Flutter Bug Reports With a Masked Screenshot and 30 Seconds of Replay](https://everframe.dev/learn/flutter-bug-report-sdk/): We ran the new Everframe Flutter SDK on an Android emulator: a masked screenshot, session replay, a Dart error and a 503, as they arrive in the dashboard. - [Kotlin Multiplatform Bug Reporting: One Shared API, Native Capture on Each Host](https://everframe.dev/learn/kotlin-multiplatform-bug-reporting/): The Everframe KMP bridge shares reporting calls and leaves capture to the native SDK. We ran it in a Compose host: what shared Kotlin sends and what arrives. - [Roku Crash Logs: Capturing BrightScript Crashes After the Channel Is Gone](https://everframe.dev/learn/roku-crash-logs/): A crashed Roku channel cannot report anything. How to capture Roku crash logs on the next launch, with a stack, key presses and memory before an OOM kill. - [Android Bug Report: What It Captures and What It Misses](https://everframe.dev/learn/android-bug-report/): An Android bug report is a device diagnostic dump, not a user's account of the problem. What it covers, what Crashlytics adds, and the gap neither one fills. - [How to Run a Bug Bash That Produces Fixable Bugs](https://everframe.dev/learn/bug-bash/): A bug bash is a timeboxed session where a whole team hunts bugs in one area at once. How to scope, run and triage one — and what makes the reports usable. - [Bug Report Format: A Template That Gets Bugs Fixed](https://everframe.dev/learn/bug-report-template/): A bug report format you can copy, field by field, with a filled example — plus why a template is a workaround for context the report should carry itself. - [Bug Reporting Tools: The Split Nobody Mentions](https://everframe.dev/learn/bug-reporting-tools/): Most bug reporting tools are web-first browser extensions that cannot touch a native app. What each one actually captures, installs and costs to run. - [Jira Bug Report: Fields, Workflow and Getting Them Filed](https://everframe.dev/learn/bug-reports-in-jira/): How Jira models a bug report, the Resolution field that quietly decides what counts as fixed, and the options for filing reports without typing them by hand. - [Bug Triage: How to Run It Without It Becoming a Status Meeting](https://everframe.dev/learn/bug-triage/): Bug triage decides what gets fixed and what does not. How to run it, how severity and priority differ, and why most triage meetings quietly stop working. - [Session Replay Tool: Analytics Product or Debugging One?](https://everframe.dev/learn/session-replay-for-bug-reports/): Two different products share the name session replay tool. How to tell which one you are buying, what each costs, and which one fits bug reports. - [What Are Bug Reports, and What Makes One Actionable?](https://everframe.dev/learn/what-is-a-bug-report/): What are bug reports, what belongs in one, and why the fields people skip are the ones that decide whether anybody can reproduce the problem later. - [SDK for Mobile Apps: What One Is and What It Costs You](https://everframe.dev/learn/what-is-a-mobile-sdk/): An SDK for mobile apps is code you ship inside your binary. What that buys, what it costs in size and setup, and the deprecation risk nobody prices in. ## Product updates Dated posts about features as they shipped, at /updates/{slug}/. Version-by-version release notes are at /changelog/. - [Try Everframe on a Live Phone or TV in Your Browser](https://everframe.dev/updates/live-device-demo/) (2026-10-08): Everframe's demo streams a live iPhone, Android phone, Apple TV and Android TV into the dashboard. File a report from one, then open it in your project. ## SDKs - [Web SDK](https://everframe.dev/sdks/web/) — JavaScript · TypeScript; powers Web (any framework) - [React SDK](https://everframe.dev/sdks/react/) — React · TypeScript; powers Web (React apps) - [React Native SDK](https://everframe.dev/sdks/react-native/) — React Native · Hermes · New Architecture; powers iOS, Android, Web - [Flutter SDK](https://everframe.dev/sdks/flutter/) — Flutter · Dart · Android / iOS / web; powers iOS, Android, Web - [Kotlin Multiplatform SDK](https://everframe.dev/sdks/kmp/) — Kotlin Multiplatform · Android / iOS / web; powers Android, iOS, Web - [iOS SDK](https://everframe.dev/sdks/ios/) — Swift · iOS / iPadOS / tvOS; powers iOS, tvOS - [Android SDK](https://everframe.dev/sdks/android/) — Kotlin · Android; powers Android, Android TV, Fire TV - [Roku SDK](https://everframe.dev/sdks/roku/) — BrightScript · SceneGraph; powers Roku ## Platforms - [iOS](https://everframe.dev/platforms/ios/) — iOS SDK - [Android](https://everframe.dev/platforms/android/) — Android SDK - [Web](https://everframe.dev/platforms/web/) — Web SDK - [Android TV](https://everframe.dev/platforms/android-tv/) — Android SDK - [tvOS](https://everframe.dev/platforms/tvos/) — iOS SDK - [Fire TV](https://everframe.dev/platforms/fire-tv/) — Android SDK - [Vega OS](https://everframe.dev/platforms/vega-os/) — Vega OS SDK (preview: JavaScript errors only) - [Roku](https://everframe.dev/platforms/roku/) — Roku SDK (crash and error reports only) - [Tizen](https://everframe.dev/platforms/tizen/) — React SDK - [webOS](https://everframe.dev/platforms/webos/) — React SDK TV and connected-device coverage (7 of 10) is the unusual part: Android TV, Fire TV, Roku, Tizen, tvOS, Vega OS, webOS. ## Solutions Product-led pages for a named buyer segment, as opposed to the editorial explainers under Learn. - [Quality Assurance Tools for Manual Test Passes](https://everframe.dev/solutions/qa-tools/): Quality assurance tools for QA teams running manual passes on mobile and TV apps: what gets captured, what it costs per tester, and where it does not fit. ## Alternatives Comparisons with one named competitor each, at /alternatives/{competitor}/. Each states where the competitor is the better choice, and the date its competitor facts were verified. - [BugHerd Alternatives for Teams Shipping a Mobile App](https://everframe.dev/alternatives/bugherd/): Comparing BugHerd alternatives? BugHerd caps members per tier and just shipped AI features. Where Everframe fits, where it does not, and what each costs. - [Gleap Alternatives: Where a Narrower Tool Wins](https://everframe.dev/alternatives/gleap/): Weighing Gleap alternatives? Gleap is a broad AI support suite with SOC 2 Type II. Where a narrower bug-reporting tool beats it, and where it clearly does not. - [Instabug Alternatives After Self-Serve Pricing Closed](https://everframe.dev/alternatives/instabug/): Looking for Instabug alternatives? Instabug is now Luciq, public pricing is gone and self-serve is closed. What changed, and when to just book the demo. - [Usersnap Alternatives for Teams That Only File Bugs](https://everframe.dev/alternatives/usersnap/): Weighing Usersnap alternatives? Usersnap is a customer-feedback platform that also captures bugs. How to tell whether you need the whole platform or one part. ## Company - [Product](https://everframe.dev/product/): what a report contains, end to end. - [Pricing](https://everframe.dev/pricing/): free tier; unlimited seats and reports on every plan. - [Security](https://everframe.dev/security/): HMAC-SHA256 signed webhooks, TLS, key storage, retention windows. - [Privacy](https://everframe.dev/privacy/): GDPR roles, sub-processors, data rights. - [Changelog](https://everframe.dev/changelog/): dated release history. - [About](https://everframe.dev/about/) · [Contact](https://everframe.dev/contact/)