Skip to content

How We Keep Mobile Session Replay 17x Cheaper Than PostHog

6.5 relevance
Score Breakdown
technical depth
7
novelty
6
actionability
8
community
5
strategic
5
personal
6

Scored daily by a customisable AI persona to surface the most relevant engineering leadership news.

Practical cost optimization for session replay, actionable.

2026-05-18 General dev.to
How We Keep Mobile Session Replay 17x Cheaper Than PostHog
Summary

Rejourney achieves 17-20x cost savings over PostHog for mobile session replay through a stack of engineering decisions: capturing at 1.25x scale (vs. native resolution), limiting to 1 FPS with run-loop-aware timers, background encoding with hard backpressure limits, on-device redaction before JPEG encoding, and binary frame bundles compressed with gzip level 9. These choices reduce pixel count by ~5.8x before compression, minimize upload bandwidth, and eliminate server-side blurring pipelines, making the economics sustainable at scale.

Key Takeaways
  • Apply aggressive client-side compression (e.g., lower resolution, lower FPS, on-device redaction) and backpressure to minimize data volume before it hits your infrastructure, compounding savings across bandwidth, storage, and compute.
Why it matters

For a senior engineer building scalable systems, these architectural patterns—aggressive client-side compression, throttling, and backpressure—directly reduce storage and egress costs, a critical consideration when designing data-intensive products.

Author

Mohammad R. Rashid