PinConsole
中 Request consultation
AGPL-3.0 self-hosted GDPR-ready 48h human reply

Self-Hosted Session Replay: Record and Replay on Your Infrastructure

Deploy open-source session replay on your own servers in 5 minutes. PinConsole records every visitor session using rrweb, stores events in your MinIO, and replays them through a standard rrweb player — with no data leaving your network.

PinConsole Competitor
Deployment Self-hosted (your servers) SaaS cloud
Data storage Your own MinIO / S3 storage Vendor's cloud
Retention control Configurable (default 30 days) Vendor plan limits
Recording engine rrweb (open source DOM capture) Proprietary
Selective screenshots 1fps WebP (canvas/WebGL/iframe) Full-page screenshots
Privacy controls GDPR consent + erasure + IP truncation Varies by vendor
Co-browsing included Yes (two-way) No (separate tool)
Real-time monitoring Yes (live DOM stream) Historical only
License AGPL-3.0 (open source) Proprietary
Pricing Free. Commercial license available. $30-100K+ per year

What is self-hosted session replay?

Session replay (also called session recording) captures every interaction a visitor makes on your website — mouse movements, clicks, scrolls, form inputs — and reconstructs them as a video-like playback. Self-hosted session replay means all this data is stored and processed on your own infrastructure, not a third-party analytics cloud. This is essential for companies that handle sensitive customer data under GDPR, HIPAA, SOC 2, or China's Personal Information Protection Law.

Why self-host instead of SaaS (FullStory, Hotjar, LogRocket)?

SaaS session replay tools like FullStory, Hotjar, and LogRocket charge based on monthly pageviews or recordings. At scale, costs grow into six figures annually. More importantly, they store your visitors' behavioral data on their servers — every click, scroll, and form input. For B2B SaaS companies serving finance, healthcare, or government clients, this creates an unacceptable data residency risk. Self-hosted session replay eliminates both the cost scaling and the data residency concern.

PinConsole: session replay + co-browsing in one self-hosted stack

Unlike FullStory or Hotjar which only offer historical analytics, PinConsole combines session replay with real-time co-browsing. You can watch a visitor live, then seamlessly transition into a co-browsing session to assist them — all without switching tools. Session data is stored in your own MinIO, with configurable retention (default 30 days), GDPR erasure support, and IP truncation.

Frequently Asked Questions

How does PinConsole's session replay compare to FullStory?

PinConsole uses rrweb for DOM capture, which provides pixel-perfect replay through a standard rrweb player. The main difference is deployment: PinConsole is self-hosted with your own storage, while FullStory is SaaS. PinConsole also includes co-browsing and visitor monitoring — features FullStory doesn't offer.

How much storage do I need for session recordings?

A typical session recording (rrweb event stream + selective screenshots) is approximately 100-500 KB per session. At 1,000 sessions/day, you would need roughly 3-15 GB/month of storage in your MinIO. Retention is configurable.

Can I export session data from PinConsole?

Session recordings are stored as standard rrweb event data in your own MinIO bucket. You can access, export, or backup them using any S3-compatible tool. The metadata (sessions, visitors) is in your PostgreSQL database.

Deploy self-hosted session replay in 5 minutes

No sign-up, no sales, no data leaving your servers.

Get started Talk to the maintainer