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.
Keep the command surface small
Expose only the operations the webview needs, such as requesting license status or beginning the supported activation flow. Validate command inputs and limit filesystem and network capabilities. Do not offer arbitrary management requests from the webview, and never ship a platform administrator API key as a shortcut.
Implement the published response contract
When integrating directly over HTTP, follow the documented request fields, status handling and proof verification. Validate the expected key, signature and deadlines before trusting offline proof. Do not treat a JSON object with a success-like field as sufficient authority or convert an HTTP rejection into cached success.
Pick a licensing model first
Device activation fits a purchase tied to computers; a floating lease fits shared concurrent use. Hardware changes and virtual machines need a transfer policy. A browser checkout completion is not a new entitlement: Store fulfillment depends on verified provider evidence and license processing.
Own the platform verification
Test your Rust HTTP/crypto libraries, operating systems, packaged binaries and webview configuration. The existing eight SDK test suites do not certify a separate Rust implementation. Use API examples as a contract reference, then verify signature, malformed-response, denial, clock and network failure cases in your own integration. Keep verification code and the expected public-key configuration under release control. A development-only mock response must never authorize a packaged production build.
Common questions
Is there a dedicated integration for this platform?
Use the documented SDK or HTTP boundary described here. Platform packaging, plugin/update distribution and framework security remain part of your application.
Can I include a management API key in the shipped code?
No. Keep management credentials on a controlled backend; distributed client code is inspectable.
Which checkout provider can my Store use?
Each vendor chooses Stripe or Paddle for the whole Store. Existing purchases keep their original connection; checkout does not automatically switch providers.