*Problem* Most browser automation tools or workflow SaaS platforms require exposing internal systems or relying on third-party servers. This creates problems such as: - Data privacy concerns - Limited control over execution and environment - Difficulty scaling complex automated tasks - Challenges with custom triggers or internal services
Many developers end up writing brittle scripts or local hacks that are hard to maintain or integrate.
*Solution* Doppelganger lets you: - Run headless browser automation on your own servers or cloud instances - Trigger tasks programmatically via REST or WebSocket APIs - Orchestrate tasks with proper logging, error handling, and scheduling - Extend functionality with custom scripts or modules - Monitor tasks optionally via a lightweight UI while keeping automation headless
*Technical Details* - Node.js-based, modular architecture - Docker-ready for easy deployment - Full logging, error handling, and orchestration for production-grade automation - Open-source core with optional cloud SaaS layer for orchestration
*Why it matters* Doppelganger enables teams to automate complex browser tasks securely and reliably without relying on external SaaS. It’s ideal for: - Developers and teams behind firewalls - Internal tools that require automation but cannot leave private infrastructure - Anyone building repeatable browser automation with full control
*Feedback & discussion* I’d love to hear from the HN community: - How do you currently run browser automation on self-hosted infrastructure? - What are the biggest pain points with existing tools? - Any features you think are critical for self-hosted automation?
Full docs and setup: https://doppelgangerdev.com
Open to feedback, suggestions, and technical discussion. Thanks!