Buy the proxy route your workload actually needs

Compare Premium Residential, Residential Flex, Mobile, and Datacenter by network origin, controls, session behavior, and current payable order. There is no default winner, only the route that matches an authorized requirement.

Current catalogue

Reconcile the route with the order you will actually pay for

Every entry below comes from the current server catalogue: minimum orderable bandwidth, unit rate, payable total, traffic validity, product ID, and quantity. Checkout preserves the selected product, quantity, proxy type, and this page as the source.

No free trial. Entry price is not evidence of destination acceptance or cost per valid result; test the smallest suitable paid order against the authorized workload.

Residential Proxies

ISP-origin route

Premium Residential is a shared, rotating and bandwidth-billed ISP-origin pool, not a static ISP allocation, with more granular targeting than Flex.

Entry minimum
5 GB
Payable total
$13.75
Unit rate
$2.75/GB
Traffic validity
186 days

Catalogue capability receipt

  • Shared pool
  • Billed by bandwidth
  • One country, state, city, ZIP, coordinate, or ASN selector at a time; route availability varies
  • Connection-based rotation; a fresh IP is not guaranteed
  • Requested sticky sessions up to 120 minutes; continuity can end early
  • HTTP proxying, HTTPS CONNECT, and SOCKS5

The pool is shared and rotating, not a static ISP allocation. A network origin does not reproduce a household, device, account, or local resident.

Residential Flex

Residential route

Residential Flex is the budget shared, rotating and bandwidth-billed residential pool for country-or-continent targeting; Premium Residential offers more granular controls.

Entry minimum
25 GB
Payable total
$13.75
Unit rate
$0.55/GB
Traffic validity
31 days

Catalogue capability receipt

  • Shared pool
  • Billed by bandwidth
  • One country or continent selector at a time; route availability varies
  • Connection-based rotation; a fresh IP is not guaranteed
  • Requested sticky sessions up to 30 minutes; continuity can end early
  • HTTP proxying, HTTPS CONNECT, and SOCKS5

Flex has fewer location controls and a shorter requested sticky-session limit than Premium Residential. Routes remain shared and availability varies.

Mobile Proxies

Carrier-network route

Mobile is a shared, rotating and bandwidth-billed carrier-network pool, not a dedicated device, SIM, modem, or exclusive IP, with no carrier or radio-generation selector.

Entry minimum
5 GB
Payable total
$17.75
Unit rate
$3.55/GB
Traffic validity
31 days

Catalogue capability receipt

  • Shared pool
  • Billed by bandwidth
  • One country or continent selector at a time; route availability varies
  • Connection-based rotation; a fresh IP is not guaranteed
  • Requested sticky sessions up to 120 minutes; continuity can end early
  • HTTP proxying, HTTPS CONNECT, and SOCKS5

The pool is not a dedicated device, SIM, modem, subscriber, or exclusive IP, and it has no carrier or radio-generation selector.

Datacenter Proxies

Hosting-network route

Datacenter is a shared, rotating and bandwidth-billed hosting-network pool, not a dedicated or static allocation.

Entry minimum
10 GB
Payable total
$12.50
Unit rate
$1.25/GB
Traffic validity
31 days

Catalogue capability receipt

  • Shared pool
  • Billed by bandwidth
  • One country or continent selector at a time; route availability varies
  • Connection-based rotation; a fresh IP is not guaranteed
  • Requested sticky sessions up to 120 minutes; continuity can end early
  • HTTP proxying, HTTPS CONNECT, and SOCKS5

The pool is rotating and bandwidth-billed, not a dedicated or static address. Destination acceptance and workload results are not guaranteed.

Product decision

Compare all four products by origin and control

Start with network origin, then reconcile targeting, session behaviour, and the complete entry order. No product is presented as a universal winner.

Databay proxy product decision table
Entry order5 GB · $13.75 totalBandwidth order, not an IP leaseRoute contract
Targeting
One country, state, city, ZIP, coordinate, or ASN selector at a time; route availability varies
Session request
Requested sticky sessions up to 120 minutes; continuity can end early
Rotation
Connection-based rotation; a fresh IP is not guaranteed
Protocols
HTTP proxying, HTTPS CONNECT, and SOCKS5
Decision boundary

Choose Premium Residential when an authorized workflow needs an ISP-origin route or granular location selection.

The pool is shared and rotating, not a static ISP allocation. A network origin does not reproduce a household, device, account, or local resident.

Entry order25 GB · $13.75 totalBandwidth order, not an IP leaseRoute contract
Targeting
One country or continent selector at a time; route availability varies
Session request
Requested sticky sessions up to 30 minutes; continuity can end early
Rotation
Connection-based rotation; a fresh IP is not guaranteed
Protocols
HTTP proxying, HTTPS CONNECT, and SOCKS5
Decision boundary

Choose Residential Flex when an authorized residential workflow only needs country-or-continent selection.

Flex has fewer location controls and a shorter requested sticky-session limit than Premium Residential. Routes remain shared and availability varies.

Entry order5 GB · $17.75 totalBandwidth order, not an IP leaseRoute contract
Targeting
One country or continent selector at a time; route availability varies
Session request
Requested sticky sessions up to 120 minutes; continuity can end early
Rotation
Connection-based rotation; a fresh IP is not guaranteed
Protocols
HTTP proxying, HTTPS CONNECT, and SOCKS5
Decision boundary

Choose Mobile only when an authorized test specifically requires a carrier-network route.

The pool is not a dedicated device, SIM, modem, subscriber, or exclusive IP, and it has no carrier or radio-generation selector.

Entry order10 GB · $12.50 totalBandwidth order, not an IP leaseRoute contract
Targeting
One country or continent selector at a time; route availability varies
Session request
Requested sticky sessions up to 120 minutes; continuity can end early
Rotation
Connection-based rotation; a fresh IP is not guaranteed
Protocols
HTTP proxying, HTTPS CONNECT, and SOCKS5
Decision boundary

Choose Datacenter when an authorized source permits a shared hosting-network route and consumer-network origin is unnecessary.

The pool is rotating and bandwidth-billed, not a dedicated or static address. Destination acceptance and workload results are not guaranteed.

Buying method

Make the routing decision before the pricing decision

The cheapest gigabyte can be the wrong purchase when the network origin, targeting, or session model does not match the requirement. Use the same four checks for every product.

  1. 01

    Write the workload contract

    Record the approved source, required fields and markets, request budget, retention rules, and stop conditions before selecting a proxy product.

  2. 02

    Choose the required network origin

    Select ISP-origin, residential, carrier-network, or hosting-network routing only when that origin answers a documented requirement.

  3. 03

    Check controls and session behavior

    Confirm the available location selector, protocol, rotation behavior, and requested sticky-session limit against the client and workflow.

  4. 04

    Reconcile the payable order

    Compare the current minimum quantity, unit price, payable total, and traffic validity, then test the smallest suitable order before scaling.

Connection model

Separate protocol, rotation, and route continuity

These are independent decisions. Validate all three with a destination you own or are authorized to test.

01 / transport

Choose the client protocol

HTTP proxying and HTTPS CONNECT suit HTTP-aware clients. SOCKS5 is a transport option for maintained clients that support it. Protocol choice does not change the selected product origin.

02 / rotation

Think in connections, not page requests

Rotating mode lets the gateway select an available exit on a new connection. Keep-alive, browser pools, and other persistent transports can reuse a route, so a fresh IP per request is not guaranteed.

03 / continuity

Use sticky mode only when needed

A requested session ID asks for temporary route continuity. It is not a static or dedicated IP, and upstream availability can end continuity before the requested limit.

Compare rotating and sticky sessions

Connection check

Run one safe route check before scaling

This rotating Premium Residential example keeps the password in an environment variable and checks the observed route. Change the zone only after choosing another product and confirming its current controls.

Connection manifest

One gateway · two session modes

Transport
Gatewaygw.databay.co:8888ProtocolsHTTP proxying, HTTPS CONNECT, and SOCKS5
Access boundary
Username/password or dashboard-configured source-IP allowlisting
Session identity
Rotating username fixtureUSERNAME-zone-residentialSticky username fixtureUSERNAME-zone-residential-sessionId-qa%2Dsession%2D01

Keep credentials out of source control and logs. Validate the observed route against a destination you own or are authorized to test before increasing traffic.

Both modes use the same gateway. Rotating omits sessionId; sticky adds the non-secret task fixture shown above. Either mode remains a route request, not proof of supply, a fresh exit, or uninterrupted continuity.

The generator never asks for a password. It measures deliberate client-selection and copy actions, not the generated configuration or secret value.

Three mock-tested rotating setup fixtures

Each client applies the same canonical product zone and bounded failure path differently.

cURLcURL 8.21.0 local mock trace
: "${DATABAY_PROXY_PASS:?Load DATABAY_PROXY_PASS from your secret store}"
# cURL URL-decodes --proxy-user once; %25 preserves literal % in routing values.
DATABAY_PROXY_USER='USERNAME-zone-residential'

curl --disable --silent --show-error --fail-with-body \
  --proxy 'http://gw.databay.co:8888' \
  --proxy-basic \
  --proxy-user "${DATABAY_PROXY_USER}:${DATABAY_PROXY_PASS}" \
  --connect-timeout 10 \
  --max-time 30 \
  'https://databay.com/what-is-my-ip/json'

cURL receives proxy credentials through --proxy-user and URL-decodes them once.

An HTTPS destination uses CONNECT through this HTTP proxy; it does not require an https:// proxy URL.

Read the cURL setup guide
Python RequestsRequests 2.34.2 pinned local mock fixture
import os
import sys
from urllib.parse import quote
import requests

username = quote("USERNAME-zone-residential", safe="")
password = quote(os.environ["DATABAY_PROXY_PASS"], safe="")
proxy_url = f"http://{username}:{password}@gw.databay.co:8888"
proxies = {"http": proxy_url, "https": proxy_url}

try:
    response = requests.get(
        "https://databay.com/what-is-my-ip/json",
        proxies=proxies,
        timeout=(10, 20),
    )
    response.raise_for_status()
    print(response.json())
except requests.exceptions.Timeout:
    print("Proxy check timed out within the configured request budget.", file=sys.stderr)
    raise SystemExit(1)
except requests.exceptions.RequestException:
    print("Proxy check failed; verify credentials, route availability, and destination permission.", file=sys.stderr)
    raise SystemExit(1)

Requests proxy authentication lives in a percent-encoded proxy URL assembled at runtime.

The mapping keys select destination schemes. Both can use the same HTTP proxy URL; the read timeout is an inactivity limit, not a total download deadline.

Read the Python Requests setup guide
Node.js / UndiciNode 24.14.0 with installed Undici 8.9.0 local mock trace
import { fetch, ProxyAgent } from 'undici';

const password = process.env.DATABAY_PROXY_PASS;
if (!password) throw new Error('DATABAY_PROXY_PASS is required');

const username = 'USERNAME-zone-residential';
const dispatcher = new ProxyAgent({
  uri: 'http://gw.databay.co:8888',
  token: `Basic ${Buffer.from(`${username}:${password}`).toString('base64')}`,
});

try {
  const response = await fetch('https://databay.com/what-is-my-ip/json', {
    dispatcher,
    signal: AbortSignal.timeout(30_000),
  });
  if (!response.ok) throw new Error(`Unexpected HTTP status ${response.status}`);
  console.log(await response.json());
} catch (error) {
  const message = error instanceof Error && error.name === 'TimeoutError'
    ? 'Proxy check exceeded the 30 second deadline.'
    : 'Proxy check failed; verify credentials, route availability, and destination permission.';
  console.error(message);
  process.exitCode = 1;
} finally {
  await dispatcher.close();
}

ProxyAgent receives a Basic token assembled in memory; the proxy URL contains no credential.

Use fetch and ProxyAgent from the same pinned Undici package; built-in Node fetch may expose a different Undici version.

Read the Node.js / Undici setup guide

Local mocks verify authentication, request shape, status failure, and timeout behavior. A real Databay credential and an authorized live preflight are still required to verify current route availability.

Evidence and terms

Verify the contract around the route

Product facts answer what can be ordered. These sources answer how to integrate it and what rules apply.

  • Trust Center

    Review company, network-sourcing, security, and abuse-response information.

  • Acceptable Use Policy

    Confirm the workload and destination are allowed before routing traffic.

  • Refund Policy

    Understand the purchase and refund terms before payment.

  • Setup documentation

    Use the maintained gateway and authentication guidance when integrating a client.

A proxy changes the network path; it does not create permission, reproduce a person or device, or guarantee how a destination responds. Prefer official APIs, feeds, exports, and licensed access where available, and stop or back off when a source refuses access.

Buyer FAQ

Questions to resolve before buying proxy bandwidth

Which Databay proxy product should I buy?

Start with network origin. Premium Residential fits approved work that needs an ISP-origin route or granular location controls. Residential Flex fits country-or-continent residential routing. Mobile is for a documented carrier-network requirement. Datacenter is for approved work where a shared hosting-network origin is acceptable.

What does rotating mean on these products?

The gateway can select an available exit on a new connection. It does not promise a different IP for every application request, because persistent connections may reuse a route. A requested sticky session is temporary continuity, not a static or dedicated IP.

What is the minimum Residential or Mobile order?

Premium Residential and Mobile each have a 5 GB minimum order. The current catalogue cards show the payable total, per-GB rate, traffic validity, and the entry quantities for Residential Flex and Datacenter.

Does Databay offer a free trial?

No. Databay does not offer a free trial. Use the smallest current paid order only after the product origin, controls, traffic validity, and terms fit the workload.

Do the products support HTTP and SOCKS5 clients?

The current catalogue capability row identifies HTTP proxying, HTTPS CONNECT, and SOCKS5 support for each product. Use dashboard-generated credentials, keep secrets out of source control, and verify the observed route before increasing traffic.

Does buying a proxy create permission to access a destination?

No. A proxy changes the network route; it does not create authorization. Prefer official APIs, feeds, exports, or licensed access, and honor destination restrictions, rate limits, and stop signals.

Decision checkpoint

Choose the origin first, then reconcile the current order

Return to the four catalogue receipts for direct checkout, or review workload guidance before choosing a product. No free trial is offered.