Residential Flex · selectable bandwidth

Residential routing for country-level workloads

Choose Flex when a shared residential origin matters but Premium Residential’s granular controls do not. Select a current catalogue quantity and work within country-or-continent targeting and a shorter sticky window.

Review current plans

Current catalogue

25 GB minimum

The smallest current bandwidth order, shown before checkout.

Minimum order
25 GB
Payable total
$13.75
Unit rate
$0.55/GB
Traffic validity
31 days

Purchase unit: Bandwidth, not an IP lease.

No free trial. This checkout opens the smallest current catalogue order; review the terms before payment.

Workload fit

Choose Flex when the requirement is broad location, not granular identity

Flex is the budget residential option for authorized work that can operate with country-or-continent controls. It is most useful when bandwidth planning matters more than state, city, ZIP, coordinate, or ASN selection.

  1. Country-level experience checks

    Review public or owned web experiences from one supported country or continent context at a time.

  2. Budget-scoped collection

    Set an order quantity for permitted public-data work whose location requirement stops at country or continent.

  3. Early route qualification

    Validate whether a shared residential origin fits an integration before choosing the more granular Premium Residential product.

  4. Connection-based rotation

    Use new connections to request route rotation when the application does not depend on a guaranteed fresh IP.

Product decision

Compare the four products without a default winner

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

The workload needs state, city, ZIP, coordinate, or ASN control.

Shared and rotating; one selector at a time; 5 GB minimum order.

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

Country-or-continent residential targeting is enough and the order quantity should stay adjustable.

No granular location or ASN control; 30-minute maximum sticky request.

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

A carrier-network origin is a real workload requirement.

No carrier, radio-generation, device, SIM, or modem selection.

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

A shared hosting-network origin fits better than a residential route.

Not residential, mobile, dedicated, or static IP space.

Connection check

Start with country-level route verification

Create dashboard credentials, apply one country or continent selector, and choose rotating or requested sticky behavior. Test a permitted destination before committing more bandwidth.

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-residential_FLEXSticky username fixtureUSERNAME-zone-residential_FLEX-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_FLEX'

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_FLEX", 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_FLEX';
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.

Product boundary

Flex lowers control depth before it changes network origin

Flex and Premium Residential are both shared rotating residential products. Flex stops at country-or-continent targeting and a 30-minute sticky request; Premium Residential adds finer geographic and ASN controls with a longer requested sticky window. Datacenter and Mobile use different network origins.

Buyer FAQ

Questions buyers ask before ordering

How is Flex different from Premium Residential?

Flex targets one country or continent and supports requested sticky sessions up to 30 minutes. Premium Residential adds state, city, ZIP, coordinate, and ASN controls and supports a longer requested sticky window.

Is Residential Flex a static proxy product?

No. Flex is a shared rotating residential pool. It does not reserve a static or dedicated IP address for one buyer.

How much bandwidth can I order?

Use the live catalogue control to review the current minimum, maximum, per-GB rate, payable total, and validity. Those order facts are validated again at checkout.

Does Flex guarantee a new IP for every request?

No. Rotation happens on a new connection, and a fresh IP is not guaranteed for each connection or application request.

Can a sticky route last longer than 30 minutes?

No longer window is represented in the product catalogue. You may request up to 30 minutes, but continuity can still end earlier.

Which protocols can I use?

Flex supports HTTP proxying, HTTPS CONNECT, and SOCKS5 with dashboard-generated credentials.

What does the Flex entry commitment include?

The live entry panel states the minimum selectable bandwidth, per-GB rate, payable total, and validity. Checkout revalidates the product and quantity before payment.

Review the current residential flex order options

Choose a catalogue quantity only after the network origin, controls, validity, and limitations fit the workload.

Compare current plans