Licence authority
Products, plans, customers and licences are governed centrally with lifecycle state enforced by PipKey.
Software licensing authority
PipKey is PluginPip's API-first licensing, entitlement, activation and secure product-delivery platform for software, services and connected products.
Current production release
PipKey 1.0.0 is a modular TypeScript/Fastify platform backed by PostgreSQL. It keeps licence state, activations, delivery eligibility and service credentials authoritative in one controlled system.
What PipKey controls
Integrating products call stable APIs. PipKey keeps the decision boundary central, auditable and independent of the product website.
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.
Decision flow
A product does not become the licensing authority. It asks PipKey for a decision and acts on the result.
Product or service authenticates with the correct live/test boundary.
PipKey resolves customer, product, plan and licence state.
Activation limit, installation binding and lifecycle policy are evaluated.
A signed result or bounded offline assertion is returned.
Audit/outbox evidence captures the licence-affecting decision.
Security by design
PipKey treats credentials, release eligibility and licence decisions as privileged infrastructure. The production baseline is deliberately fail-closed and recovery-aware.
Licence keys are returned once and protected server-side using keyed digests rather than persisted plaintext credentials.
Ed25519 signing protects offline entitlement assertions and product-delivery metadata.
Administrator and service access is constrained by explicit scopes, audience and environment boundaries.
Production schema changes use versioned, checksum-controlled migration history with compatibility and recovery review.
Final technical production acceptance was recorded on 16 August 2026.
Talk to PluginPip about controlled access to the PipKey platform.