Why we built it
Every network eventually has the same argument. The connection slows to a crawl at nine in the evening, and nobody can say which device is responsible. The router shows a list of connected devices and a single aggregate throughput number, which is exactly the information that does not help.
The available answers were poor. Consumer router QoS is opaque, differs on every model, and gives almost no visibility into what is actually happening. Enterprise network management is capable but priced and scoped for organisations with a dedicated networking team. There was very little in between for the person who just needs to see per-device usage and cap one machine.
Perimetery PRO is that middle ground. It runs on a single Windows machine already on the network, discovers every connected device with its manufacturer resolved, shows live upload and download per device, and lets you cap or block any of them from one screen.
What we believe
The network belongs to whoever runs it
Bandwidth decisions should sit with the person responsible for the network, not be buried three menus deep in router firmware that varies by vendor. Perimetery PRO puts every device and every limit on one screen.
Changes should be instant and reversible
A cap that takes a reboot to apply is a cap nobody uses. Every change takes effect in milliseconds and reverses just as quickly, so you can experiment without consequence.
No agents on client devices
Installing software on every phone, console and smart plug is not realistic. Perimetery PRO runs on one Windows machine and manages the rest at the network level.
Where the product is today
Perimetery PRO runs on Windows 10 and Windows 11. The devices it manages can run anything at all, because control happens at the network level rather than through software on each client. A macOS build is in development.
We are deliberate about what we claim. Scheduled rules, multi-subnet support and traffic history export are on the roadmap and are not in the product yet. If a capability is not listed on the features page, assume it does not exist rather than that we forgot to mention it.
Get in touch
Questions about whether it fits your network are usually answered fastest by just asking. Our contact page has the relevant addresses, and we read everything that arrives.