No stored raw licence keys
Licence keys are returned once and protected server-side using keyed digests rather than persisted plaintext credentials.
Security architecture
PipKey's production controls are built around protected secrets, signed assertions, explicit trust boundaries, audit evidence and verified recovery.
Controls
The current 1.0.0 baseline protects licence credentials and privileged operations without treating documentation or configuration labels as proof on their own.
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.
Privileged and licence-affecting operations generate structured audit and outbox evidence without secret disclosure.
Local backups, isolated restore verification and encrypted independent offsite recovery are part of the production baseline.
Production operations
Production acceptance requires reviewed source, exact-head automation, package integrity, current recovery evidence, controlled deployment, running-image verification and documentation close-out.