Real environments don't carry just one protocol
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.
One vService, every protocol
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.
One vService model — applied to every protocol
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.
Real protocol breadth
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.
vHost-driven auto-vService creation
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.
Bandwidth measured where your vService actually serves
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.
Visual flow management for every protocol
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.
What TR7 delivers for multi-protocol environments
Every listener type below uses the same vService configuration model and the same bandwidth meter.
HTTP / HTTPS
Full L7 web delivery with SSL/TLS termination, caching, compression, content rewriting and HTTP/2 + HTTP/3 termination.
HTTP/3 to the backend as well, not only at the edge
Terminating HTTP/3 at the edge and speaking HTTP/1.1 behind it gives away half the benefit: the loss recovery and head-of-line fixes that QUIC brings stop at the proxy. TR7 speaks QUIC to the backend too, and it is one switch — the alt-svc advertisement, the UDP rule and H3/H2/H1 on the same address are handled for you.
FIX and MQTT validated by content, not just carried by TCP
Trading and IoT traffic is usually handled as opaque TCP: the platform moves bytes and hopes. TR7 parses FIX messages and MQTT packets, so message type, topic and payload structure become conditions you can write policy against — a malformed order message or an unexpected topic is caught at the delivery layer, before it reaches the matching engine or the broker.
SCTP as a first-class L4 protocol, not a gap in the list
SCTP is selectable wherever TCP and UDP are — in the service definition and in firewall rules — and it is balanced by the same kernel-level L4 engine, with source-IP and connection persistence and the L4 protection set applied to it. That is the precondition telecom tenders actually test: Diameter over SCTP is load balanced with the same policy model, the same reporting and the same operator language as everything else on the appliance. Diameter Routing Agent behaviour at protocol level belongs to the 3GPP core-network category, not to an ADC.
Raw TCP
Transport-layer load balancing for database connections, custom application protocols, message brokers and other non-HTTP TCP services.
Raw UDP
L4 UDP load balancing for streaming, telemetry, gaming, voice transport and any service that doesn't run on TCP.
RTSP — a real health check, not a port ping
Camera and streaming estates are published as a protocol-agnostic service with source-IP persistence, and the health check speaks the protocol: TR7 opens the connection, sends an RTSP OPTIONS request and waits for a proper RTSP/1.0 200 OK, so a media server that still accepts connections but no longer answers is taken out of rotation. The scope is stated on purpose: TR7 carries and monitors RTSP, it does not parse the session to follow media channels negotiated on a separate path — a device that needs that is a media gateway, not a delivery controller.
ANY listener (catch-all)
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.
FTP relay
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.
UDP proxy
Stateful UDP proxying with per-flow tracking — beyond the basic stateless UDP virtual server pattern. Useful for protocols that need flow-aware handling.
Static hosting
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.
DNS acceleration, firewall and proxy
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 GSLB and global DNS topology, the DNS layer is paired with TR7's global traffic management.
Clientless RDP, SSH and VNC gateway
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.
vHost-based auto-vService
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.
Mixed protocols in one vService policy
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.
Health checks fitted to each protocol
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.
Where each protocol fits
A short map of which TR7 module owns the deeper functionality for each protocol family.
Web (HTTP / HTTPS)
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.
Transport (raw TCP / UDP / ANY)
TR7 ADC. Same vService model with TCP, UDP or ANY listeners. Algorithm choice (round-robin, least-conn, Fastest+) applies the same way.
DNS
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 GSLB, the DNS layer is paired with TR7's global traffic management.
File transfer (FTP)
First-class FTP relay listener handles passive-mode port negotiation correctly. No separate FTP gateway product required.
Remote access (RDP / SSH / VNC)
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.
Identity and auth protocols (RADIUS / LDAP / SAML / OAuth2 / OIDC)
Owned by TR7's access management layer. L4 transport delivery for RADIUS/LDAP servers themselves is handled by the same vService model when needed.
Static content
Serve HTML/JS/CSS/images directly from TR7 — no backend web server required.
Where this outcome shows up
Consolidating different protocols onto one platform
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.
DNS infrastructure modernization
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 GSLB when the topology spans regions.
Browser-based remote access (RDP / SSH / VNC)
Internal teams reach RDP, SSH and VNC targets through the browser. No VPN client install, no per-user native software, centrally audited sessions.
Static asset and maintenance page serving
Serve landing pages, error pages, JS/CSS/image assets and maintenance pages directly from TR7 — no separate web server required behind it.
vHost-based multi-tenant service exposure
Add new tenants or services by adding a hostname — TR7 creates an isolated vService automatically with its own certificates, rules and backend group.
Catch-all 'ANY' listener for unusual protocols
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.
Features that implement this solution
Capabilities referenced by this solution — the technical pieces that compose the controls described above.
Session Affinity
9 ways to keep a user on the same backend across requests — from source-IP to SAM, TR7's configurable cookie engine.
Per-vService Traffic Shaping and QoS
Apply per-vService, per-user or shared bandwidth limits and distribute traffic capacity in a controlled way at the application layer.
NTP Service
From upstream NTP pools to internal infrastructure — centralized, controlled and isolated time delivery.
Syslog Forwarding Proxy
Collect, classify, replicate and forward UDP and TCP syslog traffic in front of your SIEM.
DNS Firewall & Application Delivery Controller
Accelerate enterprise DNS traffic and block malicious queries — in a single layer.
Express Zone Acceleration
Authoritative DNS pulled from a hidden master, served from memory at line rate.
L4 Modes
TCP, UDP, DSR and IP tunnel — packet-level L4 load balancing on a single ADC.
Three Service Types
Pick the service type and TR7 shows only the right features — backend groups managed in the same model.
UDP Load Balancing
Manage DNS, RADIUS, SIP and NTP services with production-grade L4 load balancing, session affinity and health checks.
Common questions
Which protocols does TR7 deliver as first-class listener types?
Does TR7 support SIP, RTP or SCTP?
What is the 'ANY' virtual server type?
How does DNS work — is TR7 a DNS server?
How does remote access for RDP, SSH and VNC work?
Does the bandwidth model apply the same way to non-HTTP protocols?
Can I mix protocols in one vService?
One platform for every protocol
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.