Owned-service integration checks
Test software you control through a hosting-network route using the same protocol and authentication path planned for production.
Datacenter · shared hosting-network pool
Use a shared hosting-network origin when residential or carrier provenance is unnecessary. Plans are billed by bandwidth, routes rotate by connection, and the product does not assign a static or dedicated IP.
Review current plansCurrent catalogue
The smallest current bandwidth order, shown before checkout.
Purchase unit: Bandwidth, not an IP lease.
The lowest listed rate is $0.50/GB only at 1,024 GB ($512.00 total).
No free trial. This checkout opens the smallest current catalogue order; review the terms before payment.
Workload fit
This product fits authorized workflows that need a proxy route but do not require residential or mobile network origin. Evaluate the destination’s access rules and your need for route continuity before buying.
Test software you control through a hosting-network route using the same protocol and authentication path planned for production.
Collect allowed public information when a shared datacenter origin is suitable and the workload respects destination limits.
Inspect an authorized destination from one supported country or continent context at a time.
Exercise applications that can open a new connection for rotation and recover when route continuity ends.
Product decision
Start with network origin, then reconcile targeting, session behaviour, and the complete entry order. No product is presented as a universal winner.
| Network product | Entry order | Route contract | Decision boundary |
|---|---|---|---|
Residential ProxiesISP-origin networkPricing and checkout | Entry order5 GB · $13.75 totalBandwidth order, not an IP lease | Route contract
| Decision boundary Granular ISP-origin targeting is required for the authorized workload. Shared and rotating; one selector at a time; 5 GB minimum order. |
Residential FlexResidential networkPricing and checkout | Entry order25 GB · $13.75 totalBandwidth order, not an IP lease | Route contract
| Decision boundary Country-or-continent residential targeting is enough. Less granular controls and a 30-minute maximum sticky request. |
Mobile ProxiesCarrier-network originPricing and checkout | Entry order5 GB · $17.75 totalBandwidth order, not an IP lease | Route contract
| Decision boundary The workload requires a carrier-network origin. No carrier, radio-generation, device, SIM, or modem selection. |
Datacenter ProxiesHosting-network originPricing and checkout | Entry order10 GB · $12.50 totalBandwidth order, not an IP lease | Route contract
| Decision boundary A shared hosting-network route fits the destination and workload. No dedicated or static allocation; country-or-continent targeting only. |
Hosting-route qualification
Datacenter is a shared hosting-network pool, not a dedicated country allocation. Open the guide first: an empty product row means do not infer a route or proceed to purchase.
Connection check
Generate dashboard credentials, select one country or continent if needed, and choose rotating or requested sticky behavior. Verify the route and application recovery path before increasing traffic.
Connection manifest
One gateway · two session modes
gw.databay.co:8888ProtocolsHTTP proxying, HTTPS CONNECT, and SOCKS5USERNAME-zone-datacenterSticky username fixtureUSERNAME-zone-datacenter-sessionId-qa%2Dsession%2D01Keep 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.
: "${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-datacenter'
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 guideimport os
import sys
from urllib.parse import quote
import requests
username = quote("USERNAME-zone-datacenter", 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 guideimport { 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-datacenter';
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 guideLocal 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
Datacenter traffic comes from a hosting-network pool. Premium Residential and Flex use residential origins; Mobile uses a carrier-network origin. If a destination or workflow requires one of those origins, a lower datacenter entry total does not make this product interchangeable.
Buyer FAQ
No. Datacenter is a shared rotating hosting-network pool. It does not reserve a dedicated or static IP address for one buyer.
You can request one country or continent selector at a time. Every request remains subject to live route availability.
No. A new connection can rotate the route, but the catalogue does not guarantee a fresh IP for each connection or application request.
You can request up to 120 minutes. Continuity can end earlier, so the application should be able to reconnect.
Plans are billed by bandwidth. The live catalogue shows each current quantity, per-GB rate, payable total, and validity before checkout.
The product supports HTTP proxying, HTTPS CONNECT, and SOCKS5 with dashboard-generated credentials.
The live entry panel identifies the smallest current catalogue allowance, payable total, per-GB rate, and validity. Checkout revalidates that commitment before payment.
Choose a catalogue quantity only after the network origin, controls, validity, and limitations fit the workload.