How to estimate hosts, devices, and deployment scope before buying

A useful license estimate starts with the architecture, not with the number of employees in the company.

Count the Windows hosts first

A host is the Windows machine that already has the upstream network connection and runs NetConfiger. If two offices need independent exits, or two different Windows machines must stay online as separate entry points, treat them as separate hosts in your planning.

Then count the downstream workload

List the PCs, VMs, browsers, automation tools, or other applications that will use the host's HTTP/SOCKS5 listener. A single physical PC may run several applications, but what matters operationally is which devices and workloads need to be managed and supported.

Also mark any workload that does not support an explicit proxy. That workload may require a different networking method and should not be counted as if NetConfiger proxy mode automatically covers it.

Add operational requirements

Ask whether the deployment needs assisted setup, multiple administrators, stricter access control, audit records, or a larger number of managed devices. These requirements can matter as much as raw device count.

Avoid hard-coding old plan names into your architecture

Pricing and plan limits can change. Use the current NetConfiger pricing page or quotation as the source of truth for today's plan limits. This article is about estimating the shape of the deployment, not preserving a historical price table.

A simple worksheet

Before purchase, write down: number of Windows hosts, number of downstream devices, primary applications, required proxy protocol, expected network exit, whether remote setup is needed, and who owns the upstream network authorization.

With that information, the plan can be matched to the real deployment instead of guessing from labels such as “Personal,” “Team,” or “Business.”