Rejourney targets revenue leaks with open-source replay tools

Rejourney is pitching itself as an open-source way to catch conversion, retention, and revenue problems before they spread across a web or mobile app. The platform combines session replay, developer-defined business events, and technical signals such as request failures, crashes, and ANRs to flag patterns worth investigating.

It works by asking teams to instrument a small set of critical product events — for example, a completed signup, a subscription purchase, or a successful checkout. Rejourney then records the surrounding journey data, groups similar sessions into cohorts, and surfaces issue reports when a cohort shows a worrying trend around a key conversion event. If a team connects a GitHub repository, the platform can also add code context and suggest a code change.

The project supports a broad set of frameworks and platforms, including Next.js, React, React Native, Expo, Swift, Vue, Nuxt, Angular, SvelteKit, Remix, Gatsby, Shopify, and Hydrogen. On the client side, its SDKs collect session context, routes or screens, interactions, touches, scrolls, rage taps, and event sequences. When available, they also attach diagnostic data like API response times, status codes, errors, crash traces, and ANRs.

Rejourney says replay alone is not enough, so it pairs recordings with endpoint views, crash details, and project-level analytics such as version adoption, engagement, stability, retention, and custom events. If a revenue source is connected, teams can also inspect transactions, refunds, subscribers, and broader trends.

Recommended reading

Fake Books Flood Apple Books in Hours

Performance and integration details

The project includes a web benchmark comparing the Rejourney browser SDK with PostHog across local Next.js, SvelteKit, and Nuxt fixtures. In the published run, Rejourney reported lower upload size, task time, script time, and final heap use in all three frameworks:

• Next.js: 21.29 KiB upload vs 45.35 KiB for PostHog; 417.96 ms task time vs 449.91 ms
• SvelteKit: 8.38 KiB vs 24.99 KiB; 268.72 ms vs 304.03 ms
• Nuxt: 8.40 KiB vs 26.57 KiB; 305.51 ms vs 322.24 ms

The source notes that this measures SDK capture overhead, not issue-detection accuracy or any latency SLA. The run used Chromium at 1365×768, with three iterations per framework/mode.

For mobile, Rejourney compares package footprint with Sentry on Bundlephobia: @rejourneyco/react-native 1.0.17 is listed at 39.7 kB minified and 13.2 kB gzipped, versus @sentry/react-native 8.7.0 at 403 kB and 135.3 kB. A separate recorded capture test on an iPhone 15 Pro running iOS 26, Expo SDK 54, and the React Native New Architecture reported 12.4 ms average main-thread time for UIKit + Metal capture.

Rejourney supports web, React Native, and Swift integration. For iOS, it requires iOS 15.1 or later. The project also emphasizes privacy controls, including consent, masking, sampling, allowed domains, and short retention periods commonly set to seven days. After that window, it says recordings are quantized, fingerprints are anonymized, and retained data is aggregated into dashboard analytics.

Licensing is split: client-side components, including SDKs and CLIs, use Apache 2.0, while server-side components, including the backend and dashboard, use SSPL 1.0.