# How does Thales Sentinel enforce licensing rules across on-premises, cloud, embedded, and hybrid environments?

Thales Sentinel needs to enforce licensing consistently, whether a product runs on a customer's on-prem server, in the cloud, on an embedded device, or across some hybrid mix, and getting that wrong means either lost revenue from unenforced usage or friction for customers moving between deployment types. Sentinel's enforcement model actually adapts across these environments (node-locked vs. floating vs. cloud-connected licensing, offline/embedded constraints, etc.).

##### Post Metadata
- Posted at: 4 months ago
- Author title: Program Manager
- Net upvotes: 1


## Comments
### Comment 1

Sentinel separates the commercial definition of a license from the technical mechanisms used to enforce it. Product teams define what a customer is entitled to use, such as a product, module, feature, capacity level, user count, device count, or consumption allowance. The application then enforces those rights through Sentinel licensing APIs and runtime components.
At runtime, the application can request authorization for a particular feature or capability. Sentinel evaluates the request against the available license, including parameters such as license validity, expiration date, concurrency limits, device binding, feature permissions, and usage constraints. The application receives an authorization result and can enable, restrict, or disable the requested functionality.
Different credential types can be used depending on the deployment model. Hardware keys can provide a portable cryptographic root of trust for high-security or disconnected environments. Software-based licenses can be bound to device characteristics and stored locally. Cloud-connected licensing can centralize authorization and support users or devices that move between environments.
Sentinel also supports offline and intermittently connected use cases. License policies can define how long an application may operate without reconnecting, whether usage is cached locally, and what should happen if a license expires or a usage limit is reached.
This allows engineering teams to balance strict enforcement with operational requirements such as field deployments, air-gapped networks, embedded systems, and unreliable connectivity.


##### Comment Metadata
- Posted at: 4 months ago
- Author title: Program Manager




## Related Product
[Thales Sentinel Software Monetization Platform](https://www.g2.com/products/thales-sentinel-software-monetization-platform/reviews)

## Related Category
[Software Monetization Platform](https://www.g2.com/categories/software-monetization-platform)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4


