No price list sits on this page, and that is deliberate. Every environment scopes differently, so a number without your inputs would be a guess.
Volume under management is the largest single factor. A department pilot and an enterprise-wide rollout differ by an order of magnitude, and the licence reflects that rather than charging both the same.
Each connected system adds to scope. Ten shares on one server is a different engagement from ten separate cloud services, each with its own credentials and access model.
Discovery and classification form the base. Masking, anonymization, the language model layer and the regulation content packs are chosen against what the environment needs.
On your own servers, in a cloud region you control, or as a hosted service. The deployment model changes what you operate and what is operated for you.
| Included in every licence |
|---|
| Discovery across connected sources |
| Prebuilt recognizers and dictionaries |
| Classification with editable classes |
| Group based access control |
| Product updates through the term |
| Support through your partner, with vendor escalation |
The base licence carries the working platform. Nobody pays extra to classify what discovery already found, or to add a user group.
Options exist where they represent genuinely separate work: content packs maintained against changing regulation, and the language model layer that runs alongside the index.
Published pricing on a page like this is usually a starting number that nobody ends up paying.
Data security licensing scales with the environment. A credit union with four systems and a health authority with sixty are not the same purchase, and quoting them from the same table would mean one of them subsidising the other.
Scoping takes one conversation. Tell us the systems, the rough volume and where it has to run, and a quote follows against those inputs.
| Can we start small | Yes. Most engagements begin with one department or one source, then extend once the output has been judged. |
|---|---|
| Does a pilot cost anything | A scoped demonstration on representative data does not. A production pilot is licensed. |
| What happens at renewal | The licence is reviewed against actual usage, so scope that grew or shrank is reflected. |
| Are there per user fees | Licensing follows the environment. Adding a user group is a configuration change. |
| Who do we buy from | Through the partner serving your region, which keeps implementation and support with the same team. |
| Can we move deployment later | Yes. Moving between on-premises, private cloud and hosted is a commercial and technical conversation, not a new purchase. |