| name | brightdata-deploy-integration |
| description | Deploy Bright Data integrations to Vercel, Fly.io, and Cloud Run platforms.
Use when deploying Bright Data-powered applications to production,
configuring platform-specific secrets, or setting up deployment pipelines.
Trigger with phrases like "deploy brightdata", "brightdata Vercel",
"brightdata production deploy", "brightdata Cloud Run", "brightdata Fly.io".
|
| allowed-tools | Read, Write, Edit, Bash(vercel:*), Bash(fly:*), Bash(gcloud:*) |
| version | 1.6.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","scraping","data","brightdata"] |
| compatibility | Designed for Claude Code |
Bright Data Deploy Integration
Overview
Deploy Bright Data scraping applications to cloud platforms with proper secrets management. Key consideration: Bright Data proxy connections require outbound TCP to brd.superproxy.io on ports 33335 (proxy) and 9222 (Scraping Browser).
Prerequisites
- Bright Data production zone credentials
- Platform CLI installed (vercel, fly, or gcloud)
- Application tested in staging
Instructions
Step 1: Vercel Deployment (Serverless)
vercel env add BRIGHTDATA_CUSTOMER_ID production
vercel env add BRIGHTDATA_ZONE production
vercel env add BRIGHTDATA_ZONE_PASSWORD production
vercel env add BRIGHTDATA_API_TOKEN production
{
"functions": {
"api/scrape.ts": {
"maxDuration": 60
}
}
}
import type { VercelRequest, VercelResponse } from '@vercel/node';
import axios from 'axios';
import https from 'https';
export default async function handler(: , : ) {
{ url } = req.;
(!url) res.().({ : });
proxy = {
: ,
: ,
: {
: ,
: process..!,
},
};
{
response = axios.(url, {
proxy,
: https.({ : }),
: ,
});
res.({ : response., : response.. });
} (: ) {
res.().({ : error. });
}
}