# Endpoints & ports

## Production gateway

| Field                        | Value                           |
| ---------------------------- | ------------------------------- |
| Host                         | `gate.helodata.io`              |
| Port (HTTP / HTTPS / SOCKS5) | `7777`                          |
| Authentication port          | same — `7777` for all protocols |

A single host:port handles all three protocols. The protocol is auto-detected from the client handshake.

## Regional gateways (optional)

Latency-sensitive workloads can connect to a regional gateway that's closer to your servers. The pool of upstream IPs is identical; only the **first hop** changes.

| Region                   | Host                  |
| ------------------------ | --------------------- |
| Global anycast (default) | `gate.helodata.io`    |
| North America            | `na.gate.helodata.io` |
| Europe                   | `eu.gate.helodata.io` |
| Asia-Pacific             | `ap.gate.helodata.io` |

Use a regional gateway only when you measure a meaningful improvement; for most users the anycast host is faster because it routes to the nearest POP automatically.

## Ports for backwards compatibility

Migrations from other providers can also reach the gateway on:

| Port    | Original purpose                      |
| ------- | ------------------------------------- |
| `10000` | matches Smartproxy/Decodo legacy port |
| `8000`  | matches older helodata configurations |

Both alias to the same gateway. Prefer `7777` for new integrations.

## TLS

* Outbound TLS to the target site (HTTPS) is **always** end-to-end — helodata does not terminate it.
* Connecting to the gateway over TLS (wrapping the proxy hop itself) is supported on the same port `7777` — the gateway auto-detects plain vs TLS from the client handshake. Use it when your environment requires TLS-only egress.

## Connection limits

| Limit                               | Default   | Raise via              |
| ----------------------------------- | --------- | ---------------------- |
| Concurrent connections per sub-user | 600       | Dashboard plan upgrade |
| Requests per second per sub-user    | 1000      | Dashboard plan upgrade |
| Max request body                    | 100 MB    | Email support          |
| Max response body                   | unlimited | —                      |
| Idle timeout                        | 120 s     | —                      |

Trial accounts are capped at 25 concurrent connections.

## DNS

Resolve `gate.helodata.io` via your normal resolver. The record returns both IPv4 and IPv6; the gateway accepts either.

If your network blocks public DNS, the dashboard ships a static A/AAAA reference under **Settings → Network info**.

## Health check

A `GET /healthz` against the gateway returns `200 ok` and does **not** consume traffic credits:

```bash
curl https://gate.helodata.io:7777/healthz
```

Use it from monitoring jobs to verify the gateway is reachable without burning bandwidth.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.helodata.com/products/overview/endpoints-and-ports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.