StreamSec Tools is a self-contained, native cryptographic stack for Embarcadero Delphi ^TM: TLS 1.3, SSH/SFTP, X.509/PKIX, CMS and post-quantum algorithms, written entirely in Object Pascal with no required dependency on OpenSSL or the Windows CryptoAPI. That single decision - native, compiled-in cryptography - is what sets it apart from the two usual alternatives.

COMPARED TO...

• Linking OpenSSL — ship one executable with no libssl/libcrypto DLLs and no CVE-driven redeploy treadmill, no C bindings that lag OpenSSL's API changes, and a handshake you can debug in the IDE - while staying interop-compatible with OpenSSL.
• Windows Schannel — every customer runs exactly the TLS you built and tested, regardless of their Windows version or group policy, on older Windows and on Linux and macOS where Schannel does not exist, with the trust model under your control.

WHAT YOU GET EITHER WAY

• One coherent stack: TLS, X.509 / PKIX / CMS / OCSP, SSH and SFTP and the SNIF remoting framework - one API, one vendor, one audit surface.
• The same crypto on Win32/Win64, macOS, Android and iOS, from one codebase.
• Full Object Pascal source, built by your own compiler; the linker pulls in only what you use.
• Current with TLS 1.3 and post-quantum, interop-tested against OpenSSL and OpenSSH.

HARD TO MISCONFIGURE

A native design also prevents whole classes of TLS misconfiguration: you cannot connect without verifying the peer, the OS trust store is not silently inherited, and a certificate that is not a CA cannot sign one. Secure by construction »

PROVEN FOR OVER 25 YEARS

Longevity is a security property in its own right. StreamSec Tools has been under continuous development for more than 25 years and deployed in production systems around the world for nearly as long - shipped inside commercial Delphi applications and embedded in widely used third-party frameworks, exposed to real-world traffic the whole time.

Much of what is available elsewhere - including a great deal of open-source cryptography - is effectively a hobby project or abandonware that has never been tested at scale. StreamSec has. Among independent implementations, only a small number of high-profile open-source projects, such as OpenSSL and OpenSSH, can claim a longer or more proven track record - and StreamSec is continuously verified for interoperability against exactly those.

A frequent question from security teams: is StreamSec Tools FIPS 140 validated? The short answer is no - and the page explains exactly what that means and how to meet a FIPS requirement today.

See everything in StreamSec Tools 4.x, or download the trial.