BetterBandwidth lets you monitor and control individual, group, and system-wide bandwidth usage in multi-tenant Linux environments.
Guarantee each user’s fair share of bandwidth by linking traffic to specific Linux users. Then limit their bandwidth as groups or individuals with no need to assign individual IP addresses.
Better Profit Margins
Find and cap the uncontrolled use of the few who inflate your monthly bill without having to throttle everyone. More control also means more users per box and fewer customer support requests, which increases bottom-line revenue. Notably, our control methods also require no individual IP addresses. This reduces your need for increasingly scarce and expensive IPV4 IP address blocks and creates a valuable, resellable surplus of those you already have.
Easier System Administration
Binding each program to dedicated IPs is cumbersome, and some programs don’t even support it. BetterBandwidth, however, allows you to automatically force a specific user's traffic on a shared server to originate from a specified IP address. Finally, no more dedicated users’ traffic appearing to originate from your main shared IP.
Minimize the effects of bandwidth monopolizers to make available more bandwidth per user or make room for more users on the same amount of bandwidth.
Learn how much bandwidth each user and user’s application consumes over specifiable time intervals, as well as applications’ addresses, port destinations, and how much bandwidth flows through each socket. See also protocol (ip, tcp, etc.) and detailed packet info, including bytes used per pid. You can even create custom data summaries.
Define groups of Linux users and limit the number of inbound connections available per group member on any given port. We tie inbound traffic to specific Linux users, even when destined for generic users, like Apache’s “nobody” user. You can also prioritize port connections (e.g. give Apache more connections than MySQL).
Get connection data: type (local or internet), method (string, diagram, etc.), and per user/port maximums with each one’s current use data expressed in number and percent. See every configured connection (limited or not) and all in-use connections (configured or not), as well as a resettable connection denial counter.
Better Stability & Efficiency
Without per-user connection limits, any user can monopolize all connections and behave like a DOS attack. And if you limit the Apache user, for example, you risk unnecessarily cutting off legitimate traffic. But because you can now tie all traffic to specific Linux users, you can also limit inbound connections per user and minimize the impact of DOS attacks. Connections beyond the limit are simply shut down. Less severe connection inefficiencies also occur many times a day without administrators even knowing it, which per-user connection limiting also solves.