Entitlements & support
Principle
Section titled “Principle”Commercial controls must not become a runtime dependency of customer applications.
Entitlement behavior
Section titled “Entitlement behavior”- Build-time enforcement only — signed, organization-scoped entitlements with product, version, and seat rights. Support local and offline CI validation.
- Do not add mandatory activation calls, license watermarks, or kill switches to shipped applications.
- Expiry / renewals — perpetual use of versions earned during a completed paid annual term; support and access to later releases end when the subscription ends. Trials/evaluations do not receive that fallback.
- Reproducible archives — entitled releases, symbols, package metadata, and license proofs available for reproducible builds.
- Customer portal — organizations, named seats, role-based admin, contractor assignment, invoices, POs, quote acceptance, renewal reminders, immutable entitlement audit events. Keep payment processing separate from package signing and release credentials.
Support boundaries
Section titled “Support boundaries”| Level | Service boundary |
|---|---|
| Community | Public issues/discussions and documentation. No contractual response target |
| Professional | Private SDK/framework troubleshooting. Target initial response within two business days during published support hours — not a fix-time guarantee |
| Enterprise base | Named contacts, triage/escalation path, and response targets specified in the order |
| Enterprise options | Price extended coverage, LTS windows, designated engineer time, and architecture work separately |
LTS is specific — name product branch, host/native toolchain matrix, patch scope, and end date.
Buyer checklist
Section titled “Buyer checklist”- Seat table and invites in the license portal
- Invoices / POs separate from package-signing credentials
- Professional: private support with a two-business-day initial-response target
- Enterprise: named contacts and response targets in the order; optional LTS priced separately
- Proof: Pulse on Ultra + Galaxy Watch before procurement commits
Privacy
Section titled “Privacy”No hidden data collection. License services do not need customer source code, signing secrets, or watch-user telemetry.