DI and direct classes

The facade is the recommended default, not the only way in. Crypto has three equivalent entry points, and all three run the same code:

• The Crypto facade — the shortest form, used throughout these docs.
• The manager, RoundlyConsulting\Crypto\CryptoManager — the facade root, injected through the constructor. Same API, an explicit dependency and no static calls.
• The classes the facade fronts — RsaKey, Jws, Token, Certificate and the rest — called directly. The core factories need no container, config or disk.

Inject the manager

CryptoManager is a final container singleton with no constructor arguments, so the injected instance is the exact object the facade calls:

use RoundlyConsulting\Crypto\CryptoManager;

final class IssueApiToken
{
    public function __construct(private CryptoManager $crypto) {}

    public function __invoke(): string
    {
        return $this->crypto->random()->token(48);
    }
}

// Or resolve it — a container singleton, the exact object the facade calls:
app(CryptoManager::class)->keys()->rsa()->generate(3072);

Call the classes directly

Each class works on its own — the form every feature section shows as the alternative to the facade:

use RoundlyConsulting\Crypto\Jose\Jws;
use RoundlyConsulting\Crypto\Random\Token;
use RoundlyConsulting\Crypto\Signature\Key\RsaKey;
use RoundlyConsulting\Crypto\X509\Certificate;

$key         = RsaKey::private($pem);        // core factories need no container, config or disk
$code        = Token::numeric(6);
$certificate = Certificate::fromDer($der);
$jws         = new Jws;

No action classes

Crypto has no action classes. It is stateless computation, so it exposes plain service objects rather than one action per method: the sub-accessors are final, hold no state, and every method forwards to one static factory. The table maps each facade method to the class it fronts: