Marsad

Why another one

Small teams end up paying for three products to answer one question — what is happening in my app: an error tracker, an analytics tool, and something for performance, each with its own SDK, pricing and idea of who a user is. Marsad carries all three signals out of one integration, priced flat rather than per seat.

Stack traces that survive the build

A minified stack trace is useless, and the usual fix — uploading source maps tagged with a release someone remembers to bump — fails quietly the moment they forget. Marsad stamps a debug ID into each build and matches it to the map automatically, so minified web frames and Hermes frames resolve to real files and lines with no release bookkeeping.

Every captured error also carries a short reference code a user can read out to support, so a complaint arrives attached to the exact issue.

The crashes that happen before JavaScript

A React Native app can die in ways JavaScript never sees: an iOS signal, an NSException, a Swift trap, a JVM crash, an Android ANR, or a C++ abort in a native module. These are captured natively and sent on the next launch — the only moment the process is alive to send them — from a persisted queue retried with backoff.

Counting people without following them

Analytics uses a rotating hash rather than an identifier stored on the device, so page views, referrers, campaigns, devices, countries and live visitors are available with nothing to consent to. Losing cross-day identity is the deliberate trade: it costs a cohort report and buys a product that is legal to ship in Europe without a cookie banner.

Debugging by conversation

Marsad ships a remote MCP server behind an OAuth 2.1 consent screen, so an AI assistant holds the same fourteen tools a developer would use — issues, events, stack traces, traces, releases, logs, affected users, and the actions to resolve, assign and comment. Access is read-only by default and revocable.