Internet optimization 
starts here.

Bequant uses DPI and subscriber-level data to make traffic management more precise while protecting customer privacy.

DPI is used to identify application categories and traffic behavior so the BQN Platform can apply application-aware policies. Subscriber-level data is used to map traffic to the correct service plan, enforce per-subscriber policies, identify congestion symptoms and help support teams troubleshoot performance issues faster.

From a privacy perspective, the platform stores only two pieces of information that require protection, and both are encrypted: the subscriber IP address and the subscriber identifier. Access to subscriber-level views is limited to authorized operational teams.

The BQN Platform can support networks from small and mid-size ISPs to large multi-site operators. It runs on standard Intel or AMD servers and can scale both vertically and horizontally.

For throughput, a single BQN server can process up to 400 Gbps, depending on the hardware configuration and deployment requirements. When more capacity or geographic distribution is needed, multiple BQN servers can be deployed as a centrally managed cluster. This allows an ISP to expand capacity by adding servers while keeping policy management, analytics and traffic optimization consistent across the network.

ISP customers describe Bequant as valuable because it improves real network performance, gives them better operational visibility and helps them get more from existing infrastructure.

In real deployments, customers report measurable gains such as lower latency, reduced packet loss and retransmissions, fewer support calls and better service consistency during peak traffic periods. For example, Cajun Broadband reported latency improvements and packet loss below 1%, InfoWest reported an 80% reduction in packet retransmissions, and Resound Networks reported a 35% drop in support calls related to network issues.

More customer examples can be found in Case Studies and Resound video testimonial.

Bequant has been in business for more than a decade and has been deployed successfully in more than 400 networks. We are a product company, 100% focused on improving our BQN traffic optimization platform and supporting our customers’ needs.

Bequant is licensed per server, with a monthly subscription based on the peak throughput processed. The subscription includes the right to use the software and access to support. Pricing is independent of the number of registered or concurrent subscribers.

Bequant integrates with existing billing and subscriber management systems by importing subscriber-plan information and using it to enforce per-subscriber traffic policies automatically.

The BQN Platform can receive subscriber data through RADIUS signaling, direct interaction with supported billing systems, or the Bequant REST API. This allows the platform to map each subscriber to the correct service plan without requiring engineers to configure queues manually on routers.

Bequant already supports integrations with multiple ISP billing platforms — currently 20 vendors and growing — including systems such as Powercode, Sonar, Splynx, UISP, Wisphub, Wispro and others.

The Bequant BQN Platform is deployed as an inline element on standard Intel or AMD servers. It is placed where it can see and manage subscriber traffic, usually between the subscriber access network and the upstream/core network.

It does not require replacing the ISP’s existing routers or redesigning the network architecture. In most deployments, Bequant complements the existing router infrastructure by offloading traffic optimization, subscriber policy enforcement and analytics from routers to a dedicated platform. This allows routers to focus on routing while BQN handles TCP optimization, active queue management, congestion mitigation, DPI-based policies and subscriber-level visibility.

The main network changes are normally limited to inserting the BQN server or cluster into the traffic path and integrating it with existing operational systems such as RADIUS and billing platforms when subscriber-specific policies are required. For multi-site or higher-capacity networks, multiple BQN servers can be clustered and centrally managed.

Yes. For many small and mid-size ISPs, a dedicated traffic optimization platform is worth the investment. The investment is easiest to justify when the ISP can connect the traffic optimization platform to measurable outcomes such as avoided capacity expansion, fewer support calls, lower churn risk, improved QoE, higher plan speeds or the ability to serve more subscribers with the same infrastructure. In that sense, the platform should be evaluated not as an extra network cost, but as a way to protect margins while improving customer experience.

The strongest business case is usually better use of existing infrastructure. If congestion, latency, packet loss or overloaded access links are limiting the customer experience, a platform such as Bequant can improve it without requiring large router upgrades or manual per-device tuning.

For smaller teams, the operational value is also important. A centralized platform can simplify subscriber policy enforcement, integrate with RADIUS or billing systems, reduce manual queue configuration and give support teams subscriber-level visibility. That means fewer recurring troubleshooting cycles and faster identification of problems before customers complain.

The most important evaluation criteria are:

• Active traffic optimization: the solution should improve network performance without manual intervention through TCP optimization, AI-driven congestion mitigation, active queue management and application-aware traffic prioritization.
• Network visibility: the solution should provide proactive insight into network behavior at multiple levels, including per-subscriber, per-subscriber-group, per-application and network-wide performance metrics.
• Scalability: the solution must scale with ISP traffic growth both vertically, through higher performance per server, and horizontally, by adding servers to a centrally managed cluster.
• Reliability: the solution should have a proven record of successful deployments with ISPs of similar size, technology and operational complexity.
• Deployment and integration: the solution should fit the existing network architecture with minimal router changes and integrate cleanly with RADIUS, billing systems, and operational workflows.
• Manageability: the solution should require little or no fine-tuning after deployment, and server clustering should allow occasional configuration changes to be made once and propagated across the cluster.
• Price: pricing should be proportional to the value delivered, including capacity savings, lower support workload, improved QoE and reduced churn risk.

The main differences between Bequant and Preseem are:

• TCP optimization accelerates TCP traffic and provides the rest of the Bequant features with accurate metrics for loss, latency and congestion. Preseem has no TCP optimization.
• Application awareness thanks to DPI. Preseem has no DPI feature.
• AQM with TCP-native speed control. Preseem AQM does not have TCP-native speed control and senders are slowed down by dropping packets.
• Up to 400 Gbps of throughput capacity per server. Preseem’s maximum capacity is 100 Gbps.
• Clustering several Bequant servers enables seamless management. Preseem has no clustering feature.

The Bequant BQN Platform is a traffic optimization product that improves subscriber QoE by reducing latency, packet loss and congestion. It also provides visibility by subscriber, subscriber group and application.

The main differences between Bequant and open-source QoS/router-based solutions are:

• TCP optimization accelerates TCP traffic and provides the rest of the Bequant features with accurate metrics for loss, latency and congestion.
• AI-based congestion mitigation per individual subscriber.
• AQM with per-flow queues and TCP-native speed control, for maximum latency isolation and minimum packet drops.
• Up to 400 Gbps of throughput capacity per server.
• Clustering of several Bequant servers for seamless management.

Open-source QoS and router-based solutions typically:

• Do not have TCP optimization.
• Do not have AI-based congestion mitigation.
• Their AQM does not have per-flow queues; instead, flows share the same queue based on classification, and TCP-native speed control is absent because senders are slowed down by dropping packets.
• Capacity is typically below 100 Gbps per device.
• Do not support clustering.