specification: FinOps Framework
specificationVersion: '1.0'
alignedWith:
  framework: FinOps Foundation Framework
  frameworkUrl: https://www.finops.org/framework/
  dataSpec: FOCUS
  dataSpecVersion: '1.3'
  dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/
provider: Bright Data
providerId: bright-data
publisherName: Bright Data
serviceCategory: WebData
created: '2026-05-25'
modified: '2026-05-25'
tags:
  - FinOps
  - Cost Management
  - Web Data
  - Proxy
description: |
  FinOps framework definition for the Bright Data API surface. Bright Data's chargeable units differ
  per product — Web Unlocker and SERP are billed per 1,000 successful results, Web Scraper is billed
  per 1,000 delivered records, proxy networks are billed per GB (residential, mobile) or per dedicated
  IP per month (ISP, datacenter), and Deep Lookup is billed per result row. This document maps those
  surfaces into FOCUS-compatible cost allocation, usage measurement, and unit-economics fields.
principles:
  - name: Visibility
    description: Make API consumption costs visible to engineering, product, and finance teams in near
      real-time via the Account Management API (/customer/balance, /zone/bw) and the control panel
      cost reports.
  - name: Allocation
    description: Tag every chargeable API call with the consuming team, environment, application,
      zone, and feature so cost can be allocated. Bright Data exposes per-zone bandwidth and request
      counters which align directly to FOCUS billing dimensions.
  - name: Optimization
    description: Continuously evaluate request patterns, zone routing, peer selection, and tier
      selection to reduce cost per useful unit of work. Move steady traffic onto committed Growth/Business/Premium
      tiers; reserve PAYG for spikes.
  - name: Accountability
    description: Establish budget owners per zone and chargeback or showback flows for each consuming
      team using the bandwidth/result counters exposed by /zone/bw.
domains:
  - name: Understand Usage and Cost
    capabilities:
      - name: Data Ingestion
        description: |
          Pull billing and usage data from `/customer/balance`, `/zone/bw`, and the cost-export endpoints
          into a FinOps lake or warehouse.
      - name: Allocation
        description: |
          Map each Bright Data zone to a FOCUS BillingAccount / ResourceGroup / SubAccount. Allocate
          per-request cost to the consuming application using internal tags propagated via the
          `client_id` request header or proxy username metadata.
      - name: Reporting and Analytics
        description: |
          Compute unit economics — cost per 1K results, cost per GB, cost per session-hour — and
          publish dashboards per team and per zone.
      - name: Anomaly Management
        description: |
          Alert on bandwidth and result spikes vs. baseline, and on threshold approach against the
          monthly quota of each commit tier.
  - name: Quantify Business Value
    capabilities:
      - name: Forecasting
        description: |
          Forecast monthly Bright Data spend from rolling 7/30-day result and bandwidth burn rates.
          Account for monthly commit reset cycles.
      - name: Budgeting
        description: |
          Set per-zone budgets aligned to commit tiers and overage thresholds.
      - name: Benchmarking
        description: |
          Compare cost per 1K results across zones (residential vs. ISP vs. unlocker) and against
          competitive providers (Oxylabs, Smartproxy, Apify).
      - name: Unit Economics
        description: |
          Track downstream business metric per Bright Data dollar (e.g. enriched leads per $, indexed
          SERPs per $, monitored prices per $).
  - name: Manage the FinOps Practice
    capabilities:
      - name: Policy and Governance
        description: |
          Enforce zone naming conventions, KYC compliance status, domain permissions, and rate-limit
          posture across all teams.
      - name: Education and Enablement
        description: |
          Train engineering teams on choosing Web Unlocker vs. Scraping Browser vs. raw proxies, and
          on consuming the MCP server inside agentic workflows.
chargeableUnits:
  - api: Bright Data Web Unlocker API
    unit: 1000 successful unlock responses
    currency: USD
    typical_unit_cost_range_usd: [1.00, 1.50]
  - api: Bright Data SERP API
    unit: 1000 successful SERP responses
    currency: USD
    typical_unit_cost_range_usd: [1.00, 1.50]
  - api: Bright Data Web Scraper API
    unit: 1000 successfully delivered records
    currency: USD
    typical_unit_cost_range_usd: [1.30, 1.50]
  - api: Bright Data Residential Proxies
    unit: 1 GB of residential bandwidth
    currency: USD
    typical_unit_cost_range_usd: [2.50, 4.00]
  - api: Bright Data ISP Proxies
    unit: 1 dedicated ISP IP per month
    currency: USD
    typical_unit_cost_range_usd: [1.30, 1.80]
  - api: Bright Data Datacenter Proxies
    unit: 1 dedicated datacenter IP per month
    currency: USD
    typical_unit_cost_range_usd: [0.90, 1.40]
  - api: Bright Data Deep Lookup API
    unit: 1 delivered result row
    currency: USD
    typical_unit_cost_range_usd: [0.02, 0.10]
  - api: Bright Data MCP Server
    unit: 1 MCP tool call (5,000/month free on hosted tier)
    currency: USD
focusMapping:
  BillingAccountId: Bright Data customer ID
  SubAccountId: Bright Data zone name
  ServiceCategory: WebData
  ServiceName: Bright Data
  ChargeCategory: Usage / Purchase
  ChargeFrequency: Recurring or OneTime
  PricingCategory: Usage / Commitment / Reservation
  CommitmentDiscountCategory: Commit-based (Growth, Business, Premium)
sources:
  - https://docs.brightdata.com
  - https://brightdata.com/pricing