Pricing posture
Priced by sites and endpoints. Never by user.
We are not going to pretend a rate card exists when it does not. What we will do is tell you exactly how the number is built, what can never appear on your invoice, and how to get a fixed figure for your estate.
Three SKUs, one control plane
Each is licensed on the same basis. You can start with one and add the next without a migration.
ControlIT Core
RMM + overlay
The encrypted outbound-only fabric plus full remote monitoring and management. This is the SKU that retires the VPN concentrator and the second remote-access tool in the same project.
ControlIT Identity
SSO / MFA + AD over the internet
Your existing Domain Controllers, reachable from home, plant, and branch. Domain logon and Group Policy across the fabric, with one sign-on and a one-time code in front of every application.
ControlIT Ops
Managed 24/7
Computer Port runs the platform for you. Monitoring, patch windows, incident response, and reporting handled by the engineers who already operate this stack across multi-site Indian estates.
What drives the number
Six inputs. Give us these at the readiness review and you get a fixed quote rather than a range.
- Number of sites and how many of them need their own control-plane presence
- Number of managed endpoints — desktops, laptops, and servers
- Which of the three SKUs you take, and whether identity is in scope on day one
- Whether you run it yourself or take ControlIT Ops and have us run it
- Expansion bundles, if you need SIEM/XDR or compliance document management
- Deployment effort, which depends on how many sites go live in the first phase
What never appears on the invoice
This is the part most identity and RMM vendors meter. We do not.
- Adding a user to Active Directory
- Enabling single sign-on for another person already in the directory
- Turning on MFA for a user — a second factor is not an upsell
- Data egress or bandwidth across the overlay
- Administrator or technician seats in the console
- Retaining your own audit logs on your own infrastructure
Pricing questions
Why is there no rate card on this page?
Because a per-endpoint number with no site count attached would mislead more people than it helped. A three-site manufacturer with 400 endpoints and a nine-site group with the same 400 endpoints are genuinely different deployments. What we can commit to publicly is the shape: per site and per endpoint, self-hosted, never per user. You get the actual figure at the readiness review, and it is a fixed quote, not a range.
What does "no per-user identity fee" actually mean?
Identity licensing in this market is usually metered per user per month, so every person you hire raises the bill and every leaver requires a licence reclamation exercise. ControlIT does not meter identity that way. 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.
Is it a subscription or a perpetual licence?
It is licensed as a self-hosted deployment on infrastructure you control, with support and updates on an annual term. Because the control plane runs on your hardware, your data and your directory stay on your side of the line regardless of the commercial arrangement.
Do we need all three SKUs?
No, and most customers do not start there. Core is the usual entry point because the VPN is the loudest problem. Identity is added when the directory or the Entra question comes up, and Ops when you would rather we ran it. Adding the next SKU is a configuration step on the same control plane, not another migration.
Is 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 tell you so during the review rather than sell you something you will resent in a year.
What about the pilot — is that priced separately?
The 14-day pilot has its own fixed, written scope and commercials agreed before day one. It is deliberately kept separate from the rollout quote so that neither one can quietly absorb the other.
Get a figure for your estate
Site count, endpoint count, and which of the three SKUs you are thinking about. That is enough for a fixed quote — and if the fit is wrong, we would rather find that out in the review than in the quote.