u/16GB_of_ram

Rejourney started as an internal tool my team and I built for our own campus app serving University of Texas students. We were dealing with a large volume of user sessions and wanted more advanced behavioral and business analytics beyond Firebase.

That eventually became Rejourney in March 2026: A session replay and behavior analytics platform for indie developers, startups, and small teams that want FullStory like behavioral and business analytics without enterprise pricing.

Along with that, we also wanted to server developers, so we added the most common LogRocket features to the platform in a lightweight and simple dashboard.

So far, we’ve released SDKs for React Native, Swift, and Web.

Features include:

• Session replay (5k Replays Free/Mo)
• React Native, Swift, and Web SDKs
• Funnel analysis to understand where users drop off
• Behavioral analytics
• Event tracking for key actions like signups, purchases, onboarding steps, etc
• Searchable session replays, so replays feel more like a database than a folder of recordings
• Replay context including meta data such as device data, OS, Network strength, etc
• Native and JS Console Logs with each replay
• Geographic & Demographic Analytics
• A dashboard built for small teams serving large end-user apps
• Hosted in the EU 🇪🇺 + GDPR compliant [Hetzner and OVH]

The main idea is to combine the most used features in FullStory and LogRocket to make a two-in-one tool. We also benchmark our tool frequently, and it is more performant and lighter on your web and mobile apps than that of other major industry players.

Website: https://rejourney.co/

Live Demo: https://rejourney.co/demo/general

Open Source/Self Host: https://github.com/rejourneyco/rejourney

So far developers have recorded 1.6 million session replays with Rejourney, and we're excited for your feedback!

Rejourney started as an internal tool my classmates and I built for our own popular campus app that served University of Texas students. We were dealing with a massive volume of sessions and wanted full control over replay storage, filtering, and analytics because we didn't like how Clarity treated session replays as video rather than structured and highly queryable (is that word?) data. We were also a Mapbox mainly app, and all session replay tools handled that very poorly on both RN iOS and RN Android.

After using it internally for 1 month, we decided to open-source it on GitHub in March 2026, initially focused on React Native. Since then, we’ve expanded with browser (JS) and Swift SDKs, both currently in open beta.

Since launch, Rejourney has already processed over 1.6 million session replays across apps worldwide (counting only our hosted users).

One of our main goals was simplicity for all the common platforms, but a rich yet easy to understand analytics dashboard. That's why our current users love us over the other web-only light platforms like Plausible.

Integration takes only 3 lines for React Native and just a few more for the other SDKs.

We adopted table-like session replay page on our dashboard, where you can filter by row and column and even make clauses by selecting ribbons in the user journey. We treat replays as structured data, and thus users do not have to go one by one and watch based on a single filter they select (like what happens in the MS clarity dashboards).

Beyond just being more performant, we have a few unique engineering feats that no other provider has done. For example, when Rejourney was an internal tool, it was for a Mapbox heavy app. So, we had a lot of micro stutter issues that Clarity desipte the fact that it failed to even record maps at all. So we put in a new heuristic algorithm that captures frames when the map is idle to prevent stutters on pro motion displays. You can read about it in detail and how we did this with the Swift and Kotlin API interface here.

Furthermore, our self-hosting is dead easy with docs, and you can choose to self-host via a single docker file, or adopt the same exact K3s setup as our real-hosted platform. There are ZERO features missing from self-hosted that is included in hosted. We do not nerf our self-hosted version and will be free forever (no per seat enterprise stuff). Everything is open source via our one big and mighty monorepo.

Repo: https://github.com/rejourneyco/rejourney
Benchmarks: https://github.com/rejourneyco/rejourney#benchmarks

My app hit 4.5K users, and because users were opening it multiple times a day from push notifications, I was at 10K daily sessions. PostHog was charging me about $85 dollars if I wanted that volume in pure session replays and events.

For my indie app, that was not worth spending this much on analytics. So I looked for alternatives but LogRocket, FullStory, and Sentry were all pretty expensive. They also all were "enterprisey" by focus.

So I built my own. First for React Native, and now in open beta for Swift as we got more users.

Feats:

• Session Replay (100% sampling, up to 3FPS, BENCHMARKED)
• Crashes, ANRs, and Error tracking
• Business Analytics & custom events
• Console logs captured in session replays
• Geo analytics and Regional Sentiment
• GDPR compliance (EU hosted on Hetzner) & privacy API interface for the SDK

Progress in 3 months:

• 1.7 million session replays recorded globally
• ~17x cheaper than PostHog at equivalent usage
• Generous free tier specifically designed so indie devs with large DAUs don't get punished for their own growth
• NEW swift open beta

Rejourney is fully open source including the server side so you can self-host the entire thing if you want zero vendor lock in and zero monthly cost (and also I don't do that enterprise self hosting mentality to charge if you grow per seat).

GitHub: github.com/rejourneyco/rejourney

Website: rejourney.co

Previous Post: https://www.reddit.com/r/UI_Design/comments/1susnr8/feedback_on_dashboard_ui_design/

About two weeks ago, I posted here in search of feedback. Since then, I learned a lot about accessibility, view hierarchy, and color selection.

I'm happy to report my progress :)

I have seen users read more into each of the KPI cards (cursor hovering over longer than before on KPI cards), and they don't just "skip" some cards anymore. I feel that you guys were correct -- with the last design it seemed like everything just blended in.

What do you guys think now?

After nearly 3 months of battle testing our React Native package, and recording over 1.5 million session replays from users all over the world, we now have public open beta for our Swift Package.

The package targets iOS 15.1+, requires Swift tools 5.9, and links only libz. There is no CocoaPods podspec, no JavaScript runtime, and no React Native dependency.

The Swift package follows a lot of the design decisions for React Native iOS as that was also built in Native Swift for performance.

Features include:
- Pixel Perfect Session Replay
- General Analytics (Like Firebase & Posthog do)

- Logs & API Analytics

- Crashes/ANRS/Errors (Like Sentry)

- SOON: MCP/CLI

The recorder, the ingest protocol, the session lifecycle semantics, and the privacy defaults are production-quality. They have been exercised through the React Native SDK at scale of the 1.5 million session replays we have recorded already. So this is why we are in beta for iOS:

• SwiftPM resolution behavior across real Xcode versions and enterprise CI caches.
• App extension edge cases, the shared UserDefaults, and Keychain access groups behave differently under extension sandboxing.
• SwiftUI navigation since SwiftUI has no UIKit viewDidAppear equivalent, we want to understand how teams prefer to wire trackScreen, .onAppear, NavigationStack path observation, or a custom modifier.
• Whether the PrivacyInfo.xcprivacy manifest is being picked up correctly by App Store submission pipelines.

Performance Benchmarks:
https://github.com/rejourneyco/rejourney#benchmarks

Website: https://rejourney.co/

Swift Docs: https://rejourney.co/docs/swift/overview

Github/SELFHOST: https://github.com/rejourneyco/rejourney

Let me know if you would like to test out our paid tiers for free I can give you a code, just promise to report bugs :)

AI disclosure: AI used in frontend UI Dashboard development. The dashboard's user interface was created by Claude Code.

After nearly 3 months of battle testing our React Native package, and recording over 1.5 million session replays from users all over the world, we now have public open beta for our Swift Package.

The package targets iOS 15.1+, requires Swift tools 5.9, and links only libz. There is no CocoaPods podspec, no JavaScript runtime, and no React Native dependency.

The Swift package follows a lot of the design decisions for React Native iOS as that was also built in Native Swift for performance.

Features include:
- Pixel Perfect Session Replay
- General Analytics (Like Firebase & Posthog)

- Crashes/ANRS/Errors (Like Sentry)

- SOON: MCP/CLI

The recorder, the ingest protocol, the session lifecycle semantics, and the privacy defaults are production-quality. They have been exercised through the React Native SDK at scale. What we are collecting signal on in this beta:

• SwiftPM resolution behavior across real Xcode versions and enterprise CI caches.
• App extension edge cases — the shared UserDefaults and Keychain access groups behave differently under extension sandboxing.
• SwiftUI navigation patterns: since SwiftUI has no UIKit viewDidAppear equivalent, we want to understand how teams prefer to wire trackScreen — .onAppear, NavigationStack path observation, or a custom modifier.
• Whether the PrivacyInfo.xcprivacy manifest is being picked up correctly by App Store submission pipelines.

Performance Benchmarks:
https://github.com/rejourneyco/rejourney#benchmarks

Website: https://rejourney.co/

Swift Docs: https://rejourney.co/docs/swift/overview

Github: https://github.com/rejourneyco/rejourney

Let me know if you would like to test out our paid tiers for free I can give you a code, just promise to report bugs :)

https://www.producthunt.com/products/rejourney?launch=rejourney-17x-cheaper-than-posthog

I had the problem with top funnel and important functions in my app causing users to lurk more than post and contribute, so I built a custom replay tool to help solve these issues:

1. Directly ask AI in the dashboard to build a query to find certain experiences user went through (try many prompts for different behaviors such as churn, failed to post, raged on post page, never came back more than 5 times, etc).

2. Look at the details -- what was the API response time? Did the app not respond in a certain area, were there OS quirks, dead taps, rage taps, etc.

3. Based on these, I would export the console logs, event timeline, and ask Claude Code to fix these issues, along with screenshotting areas of the Session Replay where users rage tapped and asked Claude to make it more accessible (MCP/CLI tool coming soon to make this part faster).

4. After shipping the update, within a week, we had 15% more posters. The small tweaks with not just the replays, but taking everything holistically softened and made the entire app easier to use and smoother for the user. It was the classic death by a thousand cuts -- PostHog couldn't really help me figure that out from their replay interface.

Website: https://rejourney.co/

Self Host: github.com/rejourneyco/rejourney