Supply and commercial control
- ✓Upstream provider contracts and credentials
- ✓Products, packages, pricing, and limits
- ✓Brand, domain, content, and customer relationships
Latest updatev2.14.0Rust runtime in production
White-label proxy infrastructure for operators.
You bring the upstream providers. ProxyRequest turns that supply into a maintained backend, customer dashboard, routing engine, accounting, and API—under your own brand.
Software layer, not proxy supply.You keep the provider contracts, bandwidth economics, product pricing, and customer relationships.
CONNECT target.example:443
REQ-2841Response200 OKSelectedProvider AAccounting1.8 MB
DaysStandard launch path
14 presetsUpstream integrations
0% shareRevenue kept by you
Since 2020Production workloads
The operating model
Your supply enters. Your branded proxy product comes out.
ProxyRequest sits between upstream providers and your customers. It standardizes supply, applies your product rules, and exposes one stable commercial platform.
The maintained product layer
- ✓Provider pools, routing, sessions, and failover rules
- ✓Users, credentials, usage accounting, and analytics
- ✓Software updates, monitoring, and gateway deployment
One product under your brand
- ✓Stable proxy endpoints and credentials
- ✓Packages, orders, invoices, and usage visibility
- ✓Customer and reseller dashboard workflows
Standard deployment boundary
Every plan includes two managed gateway VPS instances. Choose EU, US, or Asia. Larger footprints, private integrations, and customer-provided infrastructure are scoped separately.
Who uses what
Two interfaces. One shared operating record.
Your team configures supply and commercial rules. Customers access the products you publish without seeing the upstream complexity behind them.
Operator dashboardYOUR TEAM
Configure and supervise the platform.
- 01Import providers and map locations, sessions, and protocols
- 02Build pools, packages, prices, limits, and routing rules
- 03Manage users, balances, orders, usage, and service health
- 04Operate reseller hierarchies and delivery workflows
Customer dashboardYOUR BRAND
Buy, access, and monitor proxy products.
- 01Browse the package catalog and complete order workflows
- 02Generate credentials and configure proxy access
- 03Inspect usage, balances, invoices, and request records
- 04Create and manage downstream reseller customers
Shared data backbone: both surfaces use the same users, packages, orders, proxy services, and usage records. Headless deployments expose that product layer through the API.
Build versus buy
Replace a recurring platform team—not just a codebase.
A production proxy product spans routing, accounting, customer workflows, releases, monitoring, and on-call support. ProxyRequest supplies the maintained product layer while you keep control of supply and pricing.
- ✓Keep providers, customers, and commercial economics.
- ✓Move routing decisions behind stable customer endpoints.
- ✓Use the complete dashboard or connect headlessly by API.
Illustrative monthly model
Internal build vs maintained platform
Lean internal team2–3frontend + backend developers
Developer cost$3k–$8kper developer, per month
Developer cost alone$6k–$24k+
ProxyRequest annual termfrom $600/mo
Illustrative comparison based on 2–3 developers at $3,000–$8,000 each per month. Recruiting, QA, DevOps, payroll overhead, and opportunity cost are not included.
One connected product
The operator and customer platform, already connected.
Explore real screens from the admin interface and the customer dashboard included with ProxyRequest.
Operator interface / 01
Admin dashboard
Monitor traffic, package usage, errors, provider health, and top domains from one operating view.
Operator interface / 02
Provider onboarding
Connect upstream contracts, then validate credentials, protocols, and endpoints through a guided import.
Operator interface / 03
Routing control
Control provider allocation, pools, gateway scope, quality, and cost basis without changing customer endpoints.
Operator interface / 04
Customer operations
Operate products, balances, sub-users, limits, and usage records from one control plane.
Customer interface / 01
Customer sign-in
Give customers a complete sign-in and account experience with your base brand styling on every plan.
Customer interface / 02
Usage dashboard
Customers can review traffic, requests, package consumption, account balance, and service status in one place.
Customer interface / 03
Package catalog
Publish proxy packages, allowances, billing periods, features, pricing, and coupons through the same backend catalog.
Customer interface / 04
Reseller customers
Resellers can create accounts, allocate packages, inspect usage, and issue credentials without another tool.
Upstream integrations / 14 presets
Start with a provider preset, not a custom adapter.
Prefill connection and targeting defaults, add your own credentials, review the mapping, and validate the provider through a guided import.
Provider Builder
Configure any compatible upstream.
Map addresses, credentials, sessions, geo/ASN/ISP/OS targeting, headers, and health checks for HTTP or SOCKS5 supply.
Review provider configurationGuided import previewREADY TO VALIDATE
PresetBright Data
Connectionbrightdata.gateway.example
ValidationAwaiting UI demo
HTTPS + SOCKS5Sticky sessionsHealth checks
Platform coverage
Five operating areas. One maintained platform.
Choose the complete white-label product or keep your existing frontend and connect the same routing and accounting engine through the API.
01 / Provider control
Change supply without migrating customers.
Pools, weights, locations, sessions, gateway scope, and failure behavior behind stable endpoints.
02 / Customer operations
Run account lifecycles from one system.
Accounts, packages, credentials, balances, reseller users, limits, and lifecycle workflows.
03 / Usage visibility
Know what every customer consumed.
Per-user ledgers, request records, run-out behavior, and connection policies.
04 / Branded sales
Sell through a dashboard under your brand.
Package catalog, orders, invoices, billing workflows, API access, and base brand styling.
05 / Automation
Connect workflows without owning the full stack.
REST API, webhooks, node deployment, monitoring, software updates, and platform maintenance.
Backend + customer dashboard
Use the maintained proxy backend and the included customer-facing product: authentication, catalog, purchasing, invoices, proxy delivery, analytics, reseller tools, and base brand styling.
Best when
You want to launch or replace the complete operator and customer experience without maintaining either interface.
Operating boundary
You own supply, brand, pricing, and customers. ProxyRequest operates the connected software and gateway layer.
Keep your UI and commercial layer
Your control plane remains authoritative for UI, users, payments, subscriptions, and billing. ProxyRequest handles routing, provisioning, accounting, analytics, and webhooks.
Best when
Your existing UI, user model, payments, and subscriptions already work and should remain authoritative.
Integration boundary
Your application orchestrates commercial workflows through the REST API while webhooks return platform events.
Fit check
Built for proxy businesses—not proxy end users.
The platform is a strong fit when proxy supply is an input to your business. It is not a storefront for purchasing traffic from ProxyRequest.
You operate or are launching a proxy business.
- ✓You have upstream provider relationships and want to combine them into sellable products.
- ✓You need residential, ISP, or datacenter workflows behind stable customer endpoints.
- ✓You want a complete white-label platform or an API backend for an existing application.
- ✓You want to retain control of pricing, margin, customers, and provider choice.
You only need ready-to-use proxy traffic.
- ×You are an end user looking to purchase a proxy plan for browsing, scraping, or a single project.
- ×You expect upstream bandwidth or provider contracts to be bundled into the software subscription.
- ×You need a consumer VPN, browser extension, or another end-user privacy application.
Need a non-standard deployment? Larger gateway footprints, private provider integrations, and customer-provided infrastructure can be scoped separately.
Production evidence
Proxy workloads in production since 2020.
Real deployment patterns with identifying information generalized to protect client confidentiality.
Multi-provider SaaS
One operating platform for multiple upstreams.
Routing, accounting, billing, and branded delivery brought into one configurable control plane.
READ CASE
Reseller automationFrom package to payment without manual handoffs.
Network controls, customer hierarchies, payment events, and reporting connected in one workflow.
READ CASE
B2B backendAn existing dashboard with a dedicated proxy backend.
The client kept its customer workflows while ProxyRequest supplied routing, APIs, analytics, and reliability.
READ CASE
Transparent software pricing
One software fee. Keep your bandwidth margin.
You contract upstream traffic directly. No revenue share, bandwidth markup, per-user fee, or provider markup.
ProxyRequest Platform
Backend + customer dashboard
Included in the software fee
InterfacesOperator + customer dashboards
Core platformRouting + usage accounting
AutomationREST API + webhooks
BrandBase brand styling
InfrastructureTwo managed gateway VPS
Gateway regionsYour choice of EU, US, or Asia
Not included: upstream bandwidth and provider invoices. Expanded gateway capacity, private integrations, customer-provided infrastructure, and unique workflows are scoped separately.
Evaluation & rollout
Validate the platform before launch or migration.
Your first evaluation is with the team that maintains the routing, accounting, and deployment stack—not a sales handoff.
- 01
Map supply and infrastructure
Review providers, proxy products, protocols, target locations, preferred gateway regions, and expected load.
- 02
Configure the operating model
Map customer accounts, packages, credentials, limits, billing, and the intended delivery mode.
- 03
Validate and plan rollout
Test the dashboard or API, routing, accounting, and integrations; then agree acceptance criteria and rollout sequence.
Clear operating boundary
Frequently asked questions.
Answers about product ownership, upstream supply, pricing boundaries, deployment, launch, and headless integration.
Explore documentationDoes ProxyRequest sell proxy traffic?
No. ProxyRequest provides the software, routing, accounting, dashboard, API, and managed gateway layer used to operate your own proxy products. Upstream supply remains contracted and paid for by you.
Do I need existing upstream providers?
Yes. ProxyRequest is the control and product layer. You continue to choose and pay for the upstream supply used by your products; the standard gateway infrastructure is included and managed by ProxyRequest.
Who controls products, pricing, and customers?
You do. You define the provider mix, packages, pricing, limits, brand, domain, and customer relationships. ProxyRequest does not take a revenue share or add a bandwidth, provider, or per-user markup.
Can one backend run multiple products?
Yes. Products can use different provider mixes, routing policies, geography, session behavior, credentials, and limits.
What is the difference between Full Platform and Headless?
Full Platform includes the connected operator and customer interfaces. In Headless mode your existing control plane remains authoritative for UI, users, payments, subscriptions, and billing while the REST API and webhooks connect it to ProxyRequest routing, provisioning, accounting, and analytics.
Is the customer dashboard included?
Yes. Every plan includes the customer dashboard with base brand styling, connected to the same users, packages, orders, usage records, and proxy services as the backend.
What is included in the software fee?
The maintained platform includes the operator and customer dashboards, routing, usage accounting, REST API and webhooks, base brand styling, and two managed gateway VPS instances. Upstream bandwidth and provider invoices remain separate.
Do I need to rent gateway servers?
No. Every plan includes two managed gateway VPS instances. Choose any combination of EU, US, or Asia; additional capacity and customer-provided infrastructure are scoped separately.
Can I change providers without migrating customers?
Yes. Provider pools, weights, locations, and failure behavior sit behind stable customer endpoints, so supply can change without exposing upstream-specific configuration to customers.
How quickly can the platform launch?
With providers, domains, content, and integration details ready, the standard platform can launch in a matter of days after setup. Custom development and external approvals extend the schedule.
Ready when your supply is