Distributed Browser Automation Architecture & Local Storage
Discover how BrowserMesh separates cloud orchestration from local node execution, giving you 100% data sovereignty and zero cloud vendor lock-in.
BrowserMesh rethinks modern browser automation by decoupling orchestration control from browser runtime execution. Traditional cloud automation providers force all browser sessions to run inside shared datacenter virtual machines, resulting in exorbitant compute markups, severe IP reputation degradation, and external data leakage.
In contrast, BrowserMesh implements a decentralized architecture: a lightweight cloud coordination plane coordinates tasks, while execution occurs locally across your own physical desktops, cloud VPS instances, and mobile hardware.
1. The Cloud Control Plane (Orchestrator)
The web interface hosted at BrowserMesh Studio functions exclusively as a central orchestration dashboard. It manages scheduling, workflow templates, and fleet monitoring without ever handling your target webpage data payloads:
- Workflow Scheduling & Distribution: Dispatches recurring cron jobs or on-demand tasks to the most suitable connected node based on hardware availability and network latency.
- Plugin Marketplace: Distributes 250+ declarative automation templates covering e-commerce monitoring, dynamic SPA scraping, and regression testing.
- Quota & License Management: Tracks execution metrics against your active Pricing Plan (Free ₹0 or Pro ₹299/mo).
- Fleet Telemetry Monitoring: Surfaces real-time CPU utilization, available system RAM, and node connection health without ingesting scraped data.
How Do Local Automation Nodes Execute at the Edge?
The physical muscle of BrowserMesh is the local node companion daemon, compatible with Windows Desktop, Linux VPS Servers, and Android Mobile Devices. Each node connects through outbound TLS 1.3 WebSockets, consumes scheduled automation tasks, coordinates headless Chromium execution, and writes records directly to local SQLite databases.
When a local node launches, it executes a streamlined 4-stage processing pipeline:
- Secure Outbound Tunneling: The node initializes an outbound-only TLS 1.3 WebSocket connection (
wss://mesh.browsermesh.in/socket) to the cloud orchestrator. Because connections are outbound, you do not need to configure port forwarding, dynamic DNS, or expose public firewall holes. - Job Queue Consumption: The node continuously listens for incoming workflow instructions. Tasks specify the target URL, extraction selectors, and execution timeouts.
- Sandboxed Chromium Execution: The node commands an isolated Chromium instance through the internal
BrowserPool. It activates AutomationEngine to normalize canvas noise, randomize audio context, and simulate realistic human mouse bezier trajectories. - Local Data Persistence: Extracted datasets write immediately to a local embedded SQLite database utilizing Write-Ahead Logging (WAL) for high-throughput concurrency. Scraped records never pass through or touch BrowserMesh cloud servers.
Compare Cloud Scrapers vs BrowserMesh Distributed Architecture
Comparing traditional cloud scraping providers with BrowserMesh reveals fundamental architectural differences in compute cost, data sovereignty, and anti-bot resilience. While cloud scrapers incur expensive hourly virtual machine surcharges and expose customer data to vendor breaches, BrowserMesh executes entirely on user-controlled hardware with zero data leaks.
Local Storage & Data Privacy Model
Data sovereignty is a foundational architectural principle of BrowserMesh. Scraping sensitive data, proprietary lead lists, or internal company workflows requires zero-trust security guarantees.
- Embedded SQLite Database: All structured tables are created within
%USERPROFILE%\browsermesh-node\data(Windows) or~/.browsermesh/data(Linux). - Zero Cloud Telemetry of Payloads: The orchestrator only receives job completion status (
exitCode: 0,durationMs: 3420), never the extracted payload content. - Offline Resiliency: If internet access is interrupted during an automation run, the local node caches scraped records locally and syncs task completion status when connectivity recovers.
Next Steps & Platform Resources
- Deploy Your First Node: Official Download Center (
/download) - Step-by-Step Deployment: Getting Started Guide (
/docs/getting-started) - Explore Engine Features: AutomationEngine Architecture (
/features) - Browse Pre-Built Workflows: Marketplace Catalog (
/marketplace) - Review Subscription Plans: Transparent Pricing (
/pricing) - API Documentation: REST API Reference (
/docs/api-reference)