Choose the API layer that matches your application. SharkSSL can run as a standalone TLS library, supply native cryptography, consume an external PSA Crypto provider, or supply its own PSA provider. These are separate build and integration choices.

Task	Guide
Find the right library, header, and API family	Choose a SharkSSL API
Configure a SharkSSL build	Configure SharkSSL for Your Build
Manage TLS objects, buffers, and errors	Manage a TLS Connection
Install identity certificates and trusted authorities	Certificate Management
Create and validate issued certificates	Create and Validate Certificates
Choose a PSA consumer or provider integration	Choose a PSA Integration
Review TLS features and session reuse	SharkSSL Features
Plan a device-to-service trust model	Certificate Management for IoT
Reduce flash and RAM use	Build for a Constrained Device
Select processor-specific cryptography	Ports
Run a complete application	SharkSSL Examples
Verify an OpenSSL ECDSA signature	Verify firmware signatures with SharkSSL

The reference exposes optional interfaces together so you can find them. Their presence in this manual does not mean they are enabled together in one supported build. Use the configuration and source requirements for that API, and compile against the actual headers for your selected backend.