Licence authority
Products, plans, customers and licences are governed centrally with lifecycle state enforced by PipKey.
PipKey 1.0.0
PipKey keeps commercial entitlement decisions separate from application code, website availability and payment-provider state.
Production capabilities
The current release covers the core lifecycle needed to issue, activate, validate, deliver and revoke software access securely.
Products, plans, customers and licences are governed centrally with lifecycle state enforced by PipKey.
Transactional activation limits and installation binding prevent concurrent requests silently bypassing policy.
Ed25519-signed, time-bounded licence assertions support controlled offline operation without making offline permanent.
Live/test machine credentials support scope, audience, expiry, CIDR and optional customer, product or licence linkage.
PipCMS delivery provides release metadata, signed manifests, staged-rollout metadata, download grants and self-service endpoints.
Tamper-evident audit evidence, idempotency and transactional outbox support make licence-affecting operations traceable.
Authority boundary
WooCommerce and Square signed ingestion boundaries exist, but payment providers do not become authoritative for licensing without reviewed mapping and processing logic.
Authoritative for licence state, activations, machine credential entitlement and release eligibility.
External checkout and payment systems may provide order or payment events when separately configured.
Controlled release storage provides package bytes while PipKey governs eligibility and signed metadata.
Integrating products may own customer-facing UI without owning the licensing authority.
WordPress, desktop, mobile, SaaS, server and API products can all integrate against the same licensing authority.