IP and ASN reputation
Targets score the history, carrier class, and observed behavior of the route, not just the country code.
Product / Proxies
Proxy egress is a control plane.
Undetect treats routing as policy: choose the right route for the endpoint, keep egress aligned with the browser identity, and measure cost by successful session instead of raw bandwidth or retry volume.
route policy plane
Policy
Per-URL route selection
Identity
Geo, locale, and session aligned
Economics
Cost per successful session
Controlled
Routing policy
Per-URL
Risk allocation
Coherent
Identity alignment
Measured
Cost per success
Egress risk
The right country is not enough.
Even with strong browser evasion and coherent fingerprints, network egress remains a source of variance. Reputation, density, endpoint sensitivity, and route history can change outcomes quickly.
Identity and egress mismatch
Timezone, language, account history, device class, and network geography need to tell the same story.
Concurrency density
Too many similar sessions from the same subnet can create variance even when the browser profile is sound.
Retry amplification
Blind retries can multiply cost and reinforce bad routes instead of separating network failure from target drift.
Route control loop
Declare, resolve, inspect, rotate, and measure.
The docs are strongest where they stop treating proxy as a string. Undetect can derive fingerprint fields from outbound IP, bind provider sessions to the active fingerprint, reflect route reputation, reload bad peers, and record bandwidth by domain.
proxy operating loop
UD_PROXY_SERVER
Declare the route
Set the browser proxy with credentials in the launch config instead of handling authentication inside automation code.
{COUNTRY} / {SESSION}
Bind route to identity
Populate provider-specific country and session variables from the active fingerprint so the route follows the device profile.
UD_RESOLVE_ALL
Resolve route facts before launch
Align country, timezone, languages, public IP, and related fingerprint properties to the effective outbound IP.
Undetect.reflectIp
Inspect reputation and geography
Return ASN, ISP, geolocation, VPN, proxy, datacenter, and search robot flags for the current route.
Undetect.reloadProxy
Rotate the session deliberately
Renew the proxy peer by changing the session id when reputation, geography, or provider state is unacceptable.
UD_PROXY_BYPASS_LIST
Keep waste out of premium egress
Bypass static assets, low-risk domains, and path patterns so proxy spend is reserved for requests that influence outcome.
Policy routing
Reserve premium routes for the endpoints that need them.
Many targets concentrate scrutiny around a small set of actions. Per-URL routing lets teams protect those paths without sending every asset, page, and low-risk request through expensive egress.
per-url routing table
Endpoint
Login and authentication
Premium persistent route
Protect the surfaces where account risk and challenge escalation concentrate.
Endpoint
Anti-abuse checkpoints
Stable high-reputation egress
Keep route history, device identity, and challenge behavior aligned.
Endpoint
Sensitive submissions
Audited policy route
Make routing deterministic for actions where failure is expensive or hard to replay.
Endpoint
Low-risk assets and pages
Cost-optimized route
Reserve expensive bandwidth for endpoints where it changes the outcome.
Provider model
Use ours, yours, or both.
Undetect operates a volume-priced proxy panel, but enterprises can bring approved providers and existing network controls. Many teams mix both so proxy savings and route coverage offset a meaningful portion of the platform cost.
Undetect proxy panel
Use volume-priced coverage when you need broad region access, fewer vendors, and a single support path.
Bring your own providers
Keep approved vendors, fixed egress controls, negotiated contracts, and existing compliance posture.
Mixed routing
Use Undetect coverage for breadth and experimentation while keeping tightly controlled production routes on BYO infrastructure.
Visibility
Measure the unit that matters: completed sessions.
Proxy cost usually grows because teams cannot tell whether failures come from route quality, target drift, application logic, or silent partial coverage.
Bottleneck identification
See degradation by target, route, and endpoint class. Distinguish proxy issues from application issues from target changes.
Retry amplification control
Understand when retries are helping vs. multiplying cost. Route around degraded paths instead of hammering them.
Cost per success
Track true unit economics: not cost per request, but cost per successful, complete session with full data extraction.
Undetect.getProxyServer
Resolved proxy string
Inspect the final provider string after country/session variables and hostname resolution have been applied.
UD_PROXY_BANDWIDTH_FILE
Domain-level bandwidth record
Write upload and download usage by domain after the browser closes, then use it to tune bypass rules.
Undetect.getBandwidthUsage
Runtime usage check
Read current proxy manager bandwidth during a session when investigating a live cost anomaly.
Undetect.getProxyRelayServer
Same-IP service access
Issue a temporary relay for external services that need the same browser egress without exposing provider credentials.
Map your access routes before adding more proxy volume.
Bring your target mix, endpoint classes, current providers, and cost profile. Evaluation starts by separating route policy problems from browser, identity, and application issues.