Depo and TrafficSoft launch Atlas Tau appliance for load balancing and failover

On 13 October 2026, Depo Computers and TrafficSoft unveiled Depo Atlas Tau, a hardware-software appliance. The software side is TrafficSoft ADC, an application delivery controller. The hardware side is a Depo server platform. The appliance distributes incoming traffic across application servers and keeps the service running when individual nodes fail. Two Russian vendors have released a single product with a single point of responsibility.

What we know about the appliance

The announcement is short, and much is left undisclosed. Here is what can be stated from the available information:

• Name: Depo Atlas Tau.
• Format: hardware-software appliance.
• Software base: TrafficSoft ADC.
• Hardware: Depo Computers equipment.
• Purpose: load balancing and high availability for applications.
• Not disclosed: L4/L7 throughput, number and type of ports, TLS termination performance, price, delivery timelines.

Without these parameters, it is too early to compare the product with competitors. For a load balancer, the numbers decide everything: headroom in requests per second and in new TLS connections determines whether the device can handle peak load.

Why the market needs another ADC

An ADC (Application Delivery Controller) sits in front of a group of servers and does three things: it distributes requests across nodes, checks their health, and takes some of the load off the applications, such as traffic decryption. For a long time, Western products such as F5 BIG-IP and Citrix NetScaler dominated this class. After 2022, support and updates for Russian customers became a problem. Banks, the public sector and large internet services are looking for replacements, and they need ones that meet import-substitution requirements.

The appliance format simplifies procurement. The customer gets compatible software and hardware from partners instead of assembling a configuration themselves. Warranty, updates and certification are covered by a single contract. For organizations where every purchase goes through a committee, this saves noticeable time. The downside is the usual one for single-vendor appliances: lock-in to one platform and a limited choice of configurations.

Where it can be useful, including AI workloads

The classic use cases are web portals, API gateways and internal services with strict uptime requirements. But there is a newer one. Companies that run LLM-based inference services in-house face the same problems: several servers hosting models, uneven load, and the need to pull a failed node out of rotation without stopping the service. Here the balancer acts as a dispatcher in front of a pool of GPU servers, or of a gateway to them.

LLM traffic has its own quirks. Responses stream and can last tens of seconds, so timeouts and connection distribution policies need different settings than for ordinary web traffic. The announcement does not make clear whether TrafficSoft ADC supports the required modes. That is a question to put to the vendor directly.

What to check before buying

If you are considering the appliance for a real project, here is a list of questions for the supplier:

• Actual L4 and L7 throughput and new TLS connections per second on the specific configuration.
• Support for Russian cryptography (GOST) in TLS termination.
• Clustering modes: active-active or active-standby, and failover switchover time.
• Integration with Kubernetes and automation tools.
• Presence in the registry of domestic software and regulator certificates, if the industry requires them.
• Total cost of ownership compared with a virtual ADC on your own servers.

Until the vendors publish specifications, Atlas Tau remains a bid for a niche, not a ready choice. It should be evaluated through a pilot on your own workload.