VeliKey documentation

Use build-specific cryptographic support and explicit policy review to manage TLS changes. The support reference identifies the signed v0.5.5 native Linux release, with ARM64 as the primary build and AMD64 as a separately named alternate. Each catalog retains its exact source, target, and digest.

Start with support and scope

• Executable crypto support: generated options, profiles, exact build identity, and machine-readable JSON.
• Policy management: drafts, exact targets, reviewed apply, observed canary progression, and acknowledged rollback.
• Aegis: gateway TLS and standalone primitive contexts.
• Cryptographic disclosures: operation encodings and verification limits.
• Messenger support: client protocols, inbound retention, outbound prerequisites, and separate library implementations.

Deployment and operations

• Installation
• Gateway guide
• Service-mesh adapter coverage
• Monitoring
• Troubleshooting

A library algorithm, cloud template, or compliance label does not establish support for a deployed protocol. Check the exact implementation and release before choosing an option. New implementations require releases; policy changes select installed options and affect new TLS handshakes.