Static native

A dedicated route. A defined resource.

Choose static native resources for authorized tasks with specific network identity needs. Start with the region, route specification and term.

View pricing Explore configuration

Product preview · Purchasing and live connections are not open.

Dedicated native routeProduct concept illustration

Product & workflow

Start with the connection you need.

01 / Dedicated native route

Assess the actual route specification; no unverified anonymity rating is promised.

02 / Region & quantity selection

Combine region, quantity and term, with inventory subject to supply.

03 / HTTP connections at launch

Plan longer workflows around explicit expiry and renewal conditions.

Billing & validity

Static native prices depend on region, quantity and term and match PuraRoute retail for the same specification. Unverified prices and inventory combinations are not shown.

View plans & prices

Usage boundaries

HTTP is the planned launch protocol. Network identity and availability depend on verified product specifications. Purchasing is not open yet.

Read acceptable use

Integration examples

Familiar tools. Clear parameters.

These standard proxy examples need an actual endpoint and credentials. They do not provide a currently usable account.

Read documentation

curl --proxy "http://${PROXY_HOST}:${PROXY_PORT}" \
  --proxy-user "${PROXY_USERNAME}:${PROXY_PASSWORD}" \
  --max-time 30 --fail --silent --show-error \
  "https://httpbin.org/ip"

Explore further

Compare your connection options.

Dynamic residential

Traffic-based access with rotating or sticky sessions. Designed for cross-market public data tasks.

View product

Static residential

Fixed residential exits, selected by quantity and term, for workflows that need a consistent connection.

View product