Download BrowserMesh for Any Platform
Choose your operating system below to orchestrate distributed browser automations with local hardware execution and zero cloud data leaks.
Windows Desktop App
Android Mobile Node
Linux Daemon / CLI
Cloud Web Console
One-Command Headless Server Setup
Deploy background worker nodes on VPS (AWS, DigitalOcean, Hetzner) or local terminals.
Hardware Specifications & System Requirements
BrowserMesh runs as a self-contained execution daemon on your physical or virtual hardware. Review minimum and recommended environment configurations before orchestrating high-concurrency browser automation jobs.
- Operating System: Windows 10 (Build 19041+) or Windows 11 64-bit.
- Processor: Intel Core i3 / AMD Ryzen 3 or higher.
- System Memory: 4 GB RAM minimum (8 GB recommended for 5+ concurrent tabs).
- Disk Storage: 500 MB free space for runtime and local SQLite storage.
- Runtime: Bundled self-hosted Chromium, no external runtime dependencies.
- Distributions: Ubuntu 20.04+, Debian 11+, Fedora 38+, Arch Linux.
- Architecture: x86_64 or ARM64 (AWS Graviton, Raspberry Pi 4/5).
- Memory Footprint: 1 GB RAM for headless worker daemon (2 GB recommended).
- Service Integration: Native systemd unit file and PM2 process supervisor support.
- Virtualization: Compatible with Docker, LXC, Proxmox, and AWS EC2 / Hetzner VPS.
- Android Version: Android 9.0 (Pie / API 28) or higher.
- Architecture: 64-bit ARM (arm64-v8a).
- Battery Configuration: Must allow Unrestricted Background Execution.
- Network Benefit: Emits genuine residential 4G/5G mobile carrier IP addresses.
- Execution Engine: Headless WebView with hardware sandboxing and memory safety.
Cryptographic Binary Integrity & Verification
BrowserMesh ensures end-to-end supply chain integrity for every client binary and daemon script. All production packages are cryptographically signed and published alongside SHA-256 checksums to safeguard your automation infrastructure against tampering.
Before executing installer packages in production or enterprise environments, verify checksum validity using native command line hashing utilities.
How does BrowserMesh maintain complete data sovereignty across downloaded nodes?
Unlike legacy cloud scraping proxies that intercept and store your extracted data payloads on third-party servers, BrowserMesh maintains a strict local-first data architecture. All execution binaries, automation scripts, and parsed datasets remain entirely on your local hardware without external transmission risks.
Why is local-first architecture safer than centralized cloud proxies?
Raw scraped records, authentication session cookies, and downloaded assets are saved directly into your local embedded SQLite database. No data payloads are ever transmitted to or retained on BrowserMesh cloud orchestration servers, eliminating corporate data leaks and cloud vendor lock-in completely.
How do distributed nodes communicate securely with the orchestration mesh?
Your nodes connect to the orchestration mesh through outbound-only TLS 1.3 encrypted WebSockets. No inbound firewall ports or public IP addresses are exposed, preventing external intrusion vectors and ensuring tamper-proof workflow distribution across all participating machines.
Next Steps with BrowserMesh
Once your node is connected, explore pre-built automation workflows, review transparent pricing tiers, or read detailed developer guides.