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

Self-Hosted Co-Browsing: Secure Screen Sharing on Your Infrastructure

Deploy open-source co-browsing on your own servers in 5 minutes. PinConsole gives you two-way co-browsing, session replay, and real-time visitor monitoring — all under AGPL-3.0, with no data leaving your network.

PinConsole Competitor
Deployment Your own servers (Docker compose) SaaS cloud or enterprise on-prem
Data residency 100% on your infrastructure Third-party servers (unless on-prem)
Co-browsing Two-way: click, scroll, fill, navigate Varies by vendor
Session replay Included (rrweb-based) Often separate tool / add-on
Visitor monitoring Real-time DOM + 1fps screenshots Usually not included
License AGPL-3.0 (open source) Proprietary
Pricing Free. Commercial license available. $30-100K+ per year
Setup time 5 minutes (docker compose) SDK integration + vendor onboarding

What is self-hosted co-browsing?

Self-hosted co-browsing (also called co-navigation or collaborative browsing) lets support agents see and interact with a visitor's browser in real time — highlighting elements, clicking buttons, filling forms, and navigating pages — all running on the company's own infrastructure instead of a third-party cloud. This is critical for compliance with GDPR, HIPAA, SOC 2, China's Personal Information Protection Law, and other regulations that restrict where customer data can be processed and stored.

Why companies choose self-hosted over SaaS co-browsing

SaaS co-browsing tools (Upscope, Cobrowse.io, Surfly) are convenient, but they require customer screen data to pass through third-party servers. For finance, insurance, healthcare, and government, this is a dealbreaker. Self-hosted co-browsing solves this by running entirely on your network. PinConsole makes self-hosting practical with a single docker-compose command — no Kubernetes, no cloud services, no vendor dependencies.

PinConsole: open-source co-browsing with full feature parity

PinConsole is not a stripped-down "open core" version with limited features. The AGPL-3.0 version includes everything: two-way co-browsing (cursor sync, click forwarding, form filling, page navigation), session replay (record and replay any session), real-time visitor monitoring (watch every visitor's DOM changes), popup chat (proactive messaging), and anti-bot protection (rate limiting, UA blocking, behavior analysis, fingerprinting). All in a single self-hosted binary.

Frequently Asked Questions

What infrastructure do I need to self-host PinConsole?

You need Docker (or a Linux server with Go runtime), PostgreSQL 16+, Redis 7+, and MinIO (or S3-compatible storage). The docker-compose.yml file in the repo sets up all dependencies automatically.

Does self-hosted co-browsing work behind a firewall?

Yes. PinConsole is designed for air-gapped and internal network deployments. The visitor SDK connects to your server via WebSocket — if your website is accessible, co-browsing works. No external service calls are required.

Can I customize the co-browsing experience?

Since PinConsole is open-source (AGPL-3.0), you can customize anything. The codebase is a clean Go + TypeScript monorepo. Custom development services are available through consultation.

Deploy self-hosted co-browsing in 5 minutes

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

Get started Talk to the maintainer