Skip to content
ControlIT

Priced by sites and endpoints. Never by user.

There is no rate card here because a per-endpoint number with no site count attached would mislead more people than it helped.

What we will publish is the shape of the number, what can never appear on your invoice, and how to get a fixed figure.

Get a figure for our estateBook the review

What drives the number.

Bring these to the readiness review and you get a fixed quote rather than a range.

Four inputs combine into one fixed quote: how many sites, how many endpoints, which modules, and who operates it.

What never appears on the invoice.

This is the part most identity and management vendors meter. We do not.

What other vendors meterOn your invoice
  • Adding a user to your directory

    There is no per-user identity fee.

    Not metered
  • Turning on multi-factor authentication

    A second factor is not an upsell.

    Not metered
  • Data across the overlay

    Egress and bandwidth are not metered.

    Not metered
  • Administrator or technician seats in the console
    Not metered
  • Keeping your own audit logs on your own infrastructure
    Not metered

Three ways to find out if it fits.

Pricing questions.

01Why there is no rate card

A three-site manufacturer with 400 endpoints and a nine-site group with the same 400 endpoints are genuinely different deployments. What we commit to publicly is the shape: per site and per endpoint, never per user. The figure comes out of the readiness review, and it is a fixed quote rather than a range.

02What no per-user identity fee actually means

Identity licensing in this market is usually metered per user per month, so every person you hire raises the bill and every leaver becomes a licence reclamation exercise. Single sign-on and MFA for everyone already in your directory are part of the platform, not a tier you climb into. Your headcount and your bill are not connected.

03Do we need every module

No, and most customers do not start there. Which module leads depends on the loudest problem: Secure Access for remote work, Web Gateway for internet control, AD Anywhere for the directory, or Core for endpoint operations. Adding another module is a configuration step on the same deployment, not another migration.

04Is there a minimum size

The product suits estates from roughly eighty endpoints upwards, and it fits best where there are two or more sites. Below that an overlay is usually more machinery than the problem deserves, and we will say so during the review rather than sell you something you will resent in a year.

05Is the pilot priced separately

Yes. The 14-day pilot has its own fixed, written scope and commercials agreed before day one, kept deliberately separate from the rollout quote so neither one can quietly absorb the other.

Where to go next

Get a figure for your estate.

Site count, endpoint count, and which modules you are thinking about. That is enough for a fixed quote, and if the fit is wrong we would rather find it in the review than in the invoice.

Get a figure for our estateSee the cost teardown