AGPL-3.0 vs MIT: Why We Chose AGPL for Our Open Source Project
A honest look at why PinConsole chose the AGPL-3.0 license over MIT or Apache 2.0 — the strategic reasoning, the trade-offs, and how commercial licensing works for proprietary use.
Blog
Technical deep-dives, architecture decisions, and product updates
How We Built a Self-Hosted Session Replay Alternative to FullStory
A technical deep-dive into building PinConsole — Go backend, rrweb DOM capture, MinIO storage, and a single-binary deployment model.
Building Open-Source Co-Browsing: How We Made Two Browsers Share One Session
Inside PinConsole's bidirectional co-browsing — rrweb node ID selectors, 1:1 operator locking, hub-and-spoke WebSocket routing, and safety by design.
Privacy by Design in Open-Source Session Replay: Building GDPR-First Surveillance
Opt-in consent, selective masking, right-to-be-forgotten, and 30-day retention — building GDPR-first visitor surveillance that's self-hosted and auditable.
Defense in Depth for Session Replay: Building Anti-Bot Infrastructure in Go
Rate limiting, behavioral analysis, SDK fingerprinting, and WebSocket auth — the four-layer anti-bot defense behind PinConsole.
Building a Production WebSocket Hub for 500 Concurrent Connections
Goroutine-per-connection, non-blocking fan-out, Redis Stream batching, and MinIO flush patterns — the real-time architecture behind PinConsole.
Sustainable Open Source: AGPL-3.0 and Commercial Licensing at PinConsole
No licensing servers, no sales pipeline, no contributor agreements. A transparent look at the business model behind a self-hosted open source project.