Software licensing by platform

Choose the environment that hosts your valuable work. Each guide separates customer entitlement from package distribution, management credentials and framework security, then points to the actual SDK or HTTP contract.

• Electron app licensing

  Electron licensing should enforce the entitlement in the part of your application that controls valuable work. The renderer can display license state, while a trusted application process coordinates validation, activation and storage. PermitCore provides a Node.js SDK; it does not make a customer-controlled desktop process tamper-proof.

• Python package licensing

  A Python package can check a license before enabling paid operations, but code distributed to a customer can be inspected or changed. Start by deciding which entitlement the customer buys and where you can enforce it. PermitCore provides a Python SDK for validation, activation and the documented license lifecycle.

• npm package licensing

  Commercial npm package licensing has two separate meanings: the legal terms for using the code and the technical entitlement your application checks. PermitCore helps with the latter through its Node.js SDK. A package license field is not a paid entitlement, and downloading a package does not activate a customer license.

• Tauri app licensing

  A Tauri app can integrate with the PermitCore HTTP API from its application layer or use a supported service boundary. PermitCore does not currently publish a Rust SDK. Choose a deliberate Rust command and webview boundary rather than assuming the Node.js SDK is a native Tauri integration.

• WordPress plugin licensing

  A commercial WordPress plugin can use PermitCore through the PHP SDK or documented HTTP API to check the customer entitlement. This is an integration pattern, not a ready-made PermitCore WordPress licensing plugin. Decide whether the purchase covers a site, deployment or another unit before wiring the checks.