Modern infrastructures speak many protocols. Web apps over HTTP and HTTPS. Database connections over raw TCP. Telemetry and streaming over UDP. DNS over UDP, TCP, sometimes TLS or HTTPS. Internal access through RDP, SSH or VNC. Legacy partners still using FTP. Static assets that don't need a backend to serve them at all.
The classic answer is to assemble a separate appliance — or a separate cloud service — for each: one for HTTP load balancing, one for raw TCP/UDP, one for DNS, a gateway product for RDP and SSH, an FTP proxy somewhere else. Each piece has its own license, its own configuration, its own behavior under load. Your operations team has to know all of them. Your security policy has to be enforced in all of them.
TR7 collapses this into one model. The same vService configuration object that delivers your web traffic also delivers your DNS, your transport-layer services, your gateway protocols. One platform, one place to set policy, one bandwidth meter.
TR7 treats every protocol as a first-class citizen of the same delivery model. Drop a vService on a frontend, pick the listener type, point it at a backend group. The rest — health checks, algorithm, visibility, security — is identical across protocols.
Frontend listener, traffic rules, health checks, backend group and bandwidth metering all live as one configuration object — whether the protocol is HTTP, raw TCP, UDP, DNS, FTP or a gateway protocol. Learn one model, apply it everywhere.
HTTP and HTTPS for web. Raw TCP and UDP for non-web. ANY listener (catch-all) for unusual or mixed-protocol services. FTP relay for legacy transfers. UDP proxy for stateful UDP. Static hosting to serve content without a backend. DNS acceleration, firewall and proxy in front of your DNS infrastructure. Clientless RDP, SSH and VNC gateway access through the browser.
Add a hostname to an IP and port and TR7 creates an isolated vService automatically. Each vService gets its own WAAP rules, SSL certificates, rate limits and backend pool — without you allocating a separate IP for each service or hand-stitching host-header routing rules.
The same vService-boundary measurement applies to every protocol. Combined RX and TX at the client-facing edge counts; pre-vService network blocks (firewall, L3/L4 DDoS) and the internal pass-through to your application servers stay out of scope — so the licensed tier you pick matches real serving capacity.
Traffic rules, listener configuration, content switching — built in the same visual flow builder for HTTP, TCP, UDP, DNS, FTP and gateway protocols. No protocol-specific scripting language to learn.
Every listener type below uses the same vService configuration model and the same bandwidth meter.
Full L7 web delivery with SSL/TLS termination, caching, compression, content rewriting and HTTP/2 + HTTP/3 termination.
Transport-layer load balancing for database connections, custom application protocols, message brokers and other non-HTTP TCP services.
L4 UDP load balancing for streaming, telemetry, gaming, voice transport and any service that doesn't run on TCP.
A vService that accepts any IP protocol on the configured listener IP and port — useful when you need to forward unusual or mixed-protocol traffic without specifying the protocol in advance.
First-class FTP listener that handles both the control channel and the data channel correctly, including passive-mode port negotiation. No need for a separate FTP gateway.
Stateful UDP proxying with per-flow tracking — beyond the basic stateless UDP virtual server pattern. Useful for protocols that need flow-aware handling.
Serve static content — HTML, JS, CSS, images, downloads — directly from TR7 without a backend web server. Useful for landing pages, maintenance pages, marketing assets and edge caching scenarios.
Place TR7 in front of your authoritative or recursive DNS servers. Cache, rate-limit, filter and protect DNS traffic with the same vService model and visibility as your web traffic. For full GSADC and global DNS topology, the DNS layer is paired with TR7's global traffic management.
Browser-based access to RDP, SSH and VNC backends through an HTML5 canvas. No native client install on user devices; protocols are tunneled and centrally audited.
Add a hostname to an IP and port — TR7 creates an isolated vService for it automatically, with its own SSL certificates, WAAP rules, rate limits and backend group.
A single vService can route mixed protocol traffic to the right backend group based on listener rules — instead of duplicating configuration across multiple per-protocol virtual servers.
Active probes available for every listener type — TCP, UDP, ICMP, HTTP-status, and custom check scripts when standard probes do not match what 'healthy' means for the application.
A short map of which TR7 module owns the deeper functionality for each protocol family.
TR7 ADC. Full L4-L7 stack with vService, SSL/TLS termination, caching, optimization. Pair with the Application Delivery solution page for the full feature set.
TR7 ADC. Same vService model with TCP, UDP or ANY listeners. Algorithm choice (round-robin, least-conn, Fastest+) applies the same way.
TR7 sits in front of authoritative or recursive DNS servers as an acceleration, firewall and proxy layer. For global health-based DNS routing across regions and full GSADC, the DNS layer is paired with TR7's global traffic management.
First-class FTP relay listener handles passive-mode port negotiation correctly. No separate FTP gateway product required.
Clientless gateway delivered through TR7's access management layer. Users connect via the browser using an HTML5 canvas; the protocol is tunneled and centrally audited.
Owned by TR7's access management layer. L4 transport delivery for RADIUS/LDAP servers themselves is handled by the same vService model when needed.
Serve HTML/JS/CSS/images directly from TR7 — no backend web server required.
Web traffic alongside TCP database connections, UDP services, FTP transfers and internal RDP access. One TR7 platform delivers the whole mix — no separate appliance per protocol.
Place TR7 in front of authoritative or recursive DNS servers for caching, rate limiting and firewalling. Layer in global health-based DNS routing and full GSADC when the topology spans regions.
Internal teams reach RDP, SSH and VNC targets through the browser. No VPN client install, no per-user native software, centrally audited sessions.
Serve landing pages, error pages, JS/CSS/image assets and maintenance pages directly from TR7 — no separate web server required behind it.
Add new tenants or services by adding a hostname — TR7 creates an isolated vService automatically with its own certificates, rules and backend group.
A vService with the ANY listener accepts any IP protocol on the configured IP and port — useful for legacy or in-house protocols that don't fit a named listener type.
Capabilities referenced by this solution — the technical pieces that compose the controls described above.
9 ways to keep a user on the same backend across requests — from source-IP to SAM, TR7's configurable cookie engine.
Apply per-vService, per-user or shared bandwidth limits and distribute traffic capacity in a controlled way at the application layer.
From upstream NTP pools to internal infrastructure — centralized, controlled and isolated time delivery.
Collect, classify, replicate and forward UDP and TCP syslog traffic in front of your SIEM.
Accelerate enterprise DNS traffic and block malicious queries — in a single layer.
Authoritative DNS pulled from a hidden master, served from memory at line rate.
TCP, UDP, DSR and IP tunnel — kernel-level L4 load balancing on a single ADC.
Pick the service type and TR7 shows only the right features — backend groups managed in the same model.
Manage DNS, RADIUS, SIP and NTP services with production-grade L4 load balancing, session affinity and health checks.
Request a live demo of TR7 with your protocol mix — web, transport, DNS, FTP, gateway. We will configure and verify each on your hardware in one session.