Bright Data Governed Collection Architecture

Overview

Design collection as a policy-governed data pipeline, not a direct application call. Separate human approval and configuration from collection workers, then quarantine and validate all results before any trusted consumer or external destination receives them.

Prerequisites

• Approved purpose, targets, fields, products, retention, recipients, and owners
• Current proxy, Browser API, scraper, snapshot, and delivery requirements
• Platform identity, queue, storage, policy, and observability capabilities

Instructions

Step 1: Discover the existing planes

Read design and runtime files and Grep for Bright Data credentials, zones, API endpoints, browser sessions, queues, snapshot storage, and downstream destinations. Mark every trust transition and uncontrolled shortcut.

Step 2: Define the topology