Core concepts
BypassData is a gateway. Clients connect to one of its proxy ports; for every connection it decides whether the traffic should go out directly (from your server’s IP) or through an upstream proxy. A few ideas make everything else click:
Direct vs. proxied
Direct traffic leaves from your own server. Proxied traffic is forwarded to an upstream proxy you configured. Routing rules choose between the two.
Never-bypass guard
A protected list of domains that must always be proxied and never go direct. It is checked before every other rule, so those domains can never leak your real IP.
Auto-bypass
An optional engine that watches live bandwidth and moves heavy traffic onto a proxy pool once it passes a threshold you set.
Resource proxy pools
A named group of upstream proxies. Ports and rules send proxied traffic to a pool rather than to a single fixed proxy.
The control panel
Everything is managed from the built-in web panel. Log in as admin (change the initial password right away). The dashboard shows active ports, live throughput, and the direct-vs-proxy split at a glance.
- Dashboard — real-time traffic, active ports, and recent activity.
- Ports — create and configure proxy ports and their authentication.
- Routing — manage bypass lists, proxy lists, and the never-bypass guard.
- Pools — define resource proxy pools and auto-bypass thresholds.
- Audit log — a record of every sensitive change.
Proxy ports & authentication
A proxy port is what your clients actually connect to. Each port has its own authentication and its own routing behaviour. You can run hundreds of them.
Authentication modes
- IP whitelist — only listed client IPs may connect.
- Username / password — clients must supply valid credentials.
- Whitelist + username/password — both conditions must pass.
- Open — no authentication. Strongly discouraged on any public address; the panel warns you.
Routing rules
Routing rules decide, per domain, whether a connection goes direct or through a proxy. They are evaluated in a fixed order:
The never-bypass guard runs first. If the destination matches, it is always proxied.
Then your domain rules apply — a bypass list (go direct) or a proxy list (go through a proxy), depending on the mode you chose.
If auto-bypass is enabled, live-load logic can move heavy traffic to a pool.
Bypass list vs. proxy list
In bypass-list mode, everything is proxied except the domains you list as direct. In proxy-list mode, everything is direct except the domains you list as proxied. Choose whichever matches how much of your traffic should be proxied by default.
Proxy pools & auto-bypass
A resource proxy pool is a named set of upstream proxies. Rules and ports target a pool, so you can change the underlying proxies without touching every rule.
Auto-bypass
Set a bandwidth threshold and a target pool. When live traffic on a port crosses the threshold, BypassData shifts it onto the pool automatically — useful for keeping heavy downloads off a metered proxy, or the reverse.
Pointing your clients at a port
To use a port, point your application or device at it as a proxy, using the port’s address and (if set) its credentials. Anything the client sends is then subject to your routing rules.
Monitoring & audit log
The dashboard streams live throughput per port and the overall direct-vs-proxy ratio, so you can always see where traffic is going. Separately, the audit log records sensitive changes — who changed what, and when — for later review.
Best practices
A few habits that keep a deployment safe and predictable:
- Never leave a port on open auth if BypassData listens on a public address.
- Put anything that must never reveal your real IP on the never-bypass guard.
- Keep the admin panel local — reach it over an SSH tunnel, not exposed on a public address.
- Change the initial admin password immediately, and back up your data folder.