Evaluation
The pilot exists because we will not quote you a saving we cannot measure. You deploy to a slice of your fleet, your own monitoring produces the number, and you decide what it is worth.
An extension can count the requests it blocked — that number is exact, and the product shows it. What it cannot do is know how many bytes those requests would have transferred, because Chrome exposes no such API to extensions in a production build. Every byte figure the product displays is labelled an estimate for that reason.
Your netflow, proxy logs or carrier reporting measure real egress. That is a better instrument than anything we could build, and it is already deployed.
Pick one metric, usually web egress per device per working day. Write down the number that would make this worth buying. Deciding afterwards is how pilots turn into arguments.
No deployment yet. Record the metric across the pilot group so there is something to compare against, over a period long enough to include a normal working pattern.
Force-install the extension and push a policy file. We supply one tailored to your environment — typically ads and images blocked, video left alone, and any internal applications exempted so nothing breaks on day one.
Collect the same metric. Keep a note of anything users report as broken; the per-site rules exist precisely to fix those without weakening the policy everywhere.
Against the threshold agreed in step one. If it is not met, that is a real answer and the pilot cost you a policy push and a rollback.
Web browsing is only part of your egress. Video conferencing, software updates, backups and cloud sync are untouched by this and can easily dominate a total. Filter to web traffic if your tooling allows it; if it does not, expect the headline reduction to look smaller than the effect on browsing itself.
Seasonality and population drift. A baseline over a holiday period, or a pilot group that changes size, will move the number for reasons that have nothing to do with the extension.
Video platforms ship unblocked by default. Streaming sites are exempt out of the box because blocking them breaks them rather than saving anyone a surprise. If your goal is to suppress streaming specifically, that is a policy change to make deliberately at step three.
The pilot is free, and there is no obligation at the end of it. We are looking for the first deployments as much as you are looking for the saving — that is an honest description of where this product is, and it is why the terms are what they are.
Tell us roughly how many devices and what you can measure, and we will send a policy file for your environment.
Start a pilot