Close
By default, session replays are stored in PostHog’s cloud (or your self-hosted instance) and viewed in their UI. Making them "portable" implies:
Unlike tools that force you to stream replays only to their cloud, PostHog’s open-source core lets you self-host the entire stack. Your session replays (DOM snapshots, console logs, network activity) live on . No vendor lock-in: migrate them to another system, archive them in your data lake, or delete them programmatically—all with full control. posthog session replay portable
Replay player is functional but lacks FullStory’s “rage clicks” auto-detection, friction scores, or advanced search by DOM attributes. By default, session replays are stored in PostHog’s
PostHog achieves portability through two primary mechanisms: local exports and integrated sharing. No vendor lock-in: migrate them to another system,
| Feature | Hotjar / FullStory | LogRocket | | | :--- | :--- | :--- | :--- | | Data Format | Proprietary Binary / Video | Proprietary Binary | Open JSON (DOM Snapshots) | | Self-Hosting | No | Limited (Enterprise only) | Yes (MIT Open Source) | | Export to Warehouse | Rows (aggregated) | API limits | Real-time Stream (All raw data) | | Delete via API | Partial | Yes | Full CRUD access | | Run ML on data | Not possible (no raw access) | Very difficult | Native (Export to Colab/Jupyter) |
