New Release Announcement
Thales Sentinel EMS 7.0

Dear ala,

We are pleased to announce Thales Sentinel EMS (Entitlement Management System) 7.0. This release expands into two strategic growth areas of usage-based monetization and agentic AI, while continuing to advance security, integrations, and product packaging.

Usage-Based Monetization: Expansions and Enhancements

Usage-based pricing is increasingly popular, both for AI offerings and software in general.

Sentinel EMS 7.0 introduces Thales' next generation usage platform for the modern era. The new foundation for usage-based monetization includes third-party usage ingestion from 600+ sources, mediation and metering, committed usage with overage, and pay-as-you-go models.

Example
An AI provider could charge customers according to token consumption, while a SaaS vendor could include a committed level of API usage within a subscription and then charge for any overage above that allowance. Usage continues to be applied to pre- and post-paid subscriptions as well.

MCP Server

Thales Sentinel already provides a mature API foundation for licensing and entitlement management. The new Sentinel EMS MCP Server provides an agent-facing layer over EMS APIs, enabling authorized AI agents to execute multi-step Sentinel EMS workflows through a headless, standardized, permission-controlled interface. In doing so, it will power AI workflows across product launches, order fulfillment, license activations, and support, turning monetization from a bottleneck into a real-time, agent-driven growth engine.

Example
A Customer Support AI Agent handling a license-transfer request could validate the customer's entitlement, identify the affected license, update its state and coordinate activation on the replacement device.

Read Recent Blog

Sentinel Documentation Virtual Assistant

As AI becomes the default way users find information, products need to increasingly leverage AI chatbot-style help to allow users to ask questions in natural language and get immediate, contextual answers.

The new Thales Sentinel Virtual Assistant provides natural-language access to Sentinel information from key touchpoints including the Vendor Portal, Customer Portal and API documentation. This is designed to give customers faster access to answers, accelerate onboarding and reduce dependency on support for common questions.

Integration Improvements

One of Sentinel's advantages in the market is its integration capabilities. EMS 7.0 includes further enhancements for integrations via APIs or Webhooks:

OpenAPI Specification (OAS 3.x) Compliance
Vendors increasingly expect to use AI-assisted code generation to build integrations with Sentinel. To enable automated generation of client code, test scripts, and spec-based validation, Sentinel EMS REST APIs are now defined through a standards-compliant OpenAPI 3.x specification. These capabilities accelerate development, reduce integration friction, improve automation and help customers bring integrations online faster.

Webhook Evolution: Configurable Payloads
Vendors often prefer webhook payloads to include only the fields required for a given task or job. This reduces request size, lowers processing overhead, and improves overall efficiency. Sentinel EMS 7.0 offers this capability, making webhook-based integrations even more efficient.

Improved Security Posture

Sentinel 7.0 enables seamless synchronization of Users between Identity Providers (IDP) and the Entitlement System.

The platform adds SCIM (System for Cross-domain Identity Management) support for User Management, helping synchronize user creation, updates and deprovisioning between Identity Providers and EMS. It also introduces granular roles and scopes for OAuth clients, allowing API access to be restricted to the specific EMS entities and operations required rather than relying on broad Admin-level permissions. For example, if a User is provisioned in an IDP, that same user should automatically be created in Sentinel EMS. Similarly, if they are deprovisioned in an IDP, it will be reflected in Sentinel EMS.

Other Examples of Enhanced Security
- The system can notify administrators when a licensed user changes their email address, helping them quickly identify and report potentially unauthorized account changes.

- For user-based licensing specifically, the new user security controls provide greater protection for EMS accounts, including management of active sessions, automatic logout of stale concurrent sessions, and forced logout of active sessions following a password change.

Product Bundles Versioning for Portfolio Monetization

A Portfolio Monetization strategy allows you to offer all your software, services, and hardware together, bundled the way your customers want.

In EMS 7.0, product bundles continue to evolve with bundle versioning, fixed bundle quantities, discrete bundles (incremental deployment of bundle quantities), support for Services and LDK enforcement within packaged bundles, and entitlement split and transfer operations at the bundle boundary.

These enhancements make bundles more practical across their lifecycle and strengthen support for mixed portfolio, SaaS plans and ELA-style offers.

Example
A bundle can be versioned any time new products are added or removed from it. As well, packaged bundles can include a maintenance plan that follows the same homogeneous activation rules but is of a different enforcement/license model.

Learn More

Sentinel EMS 7.0 gives you AI-driven workflows, and even more advanced modern monetization capabilities, security, integrations, and operational simplification. To further explore Sentinel EMS 7.0 features, please read the Release Notes.

Enjoy seeing these new capabilities come to life in conversations with your customers and prospects!

Not yet a customer? Request a free trial or contact us today.

Thales Sentinel Software Monetization