AFAIK, most Common Lisp applications are deployed in a single binary, bundled with the lisp implementation. SBCL isn’t an exception, so if someone would deploy an SBCL app to end-users, one would build a self-contained application with the `sb-ext:save-lisp-and-die` function [0].
[0]: https://lispcookbook.github.io/cl-cookbook/scripting.html
Compared to emitting C or whatever where you need to include code to stitch the runtime state together.
Makes compiling standalone executables so easy [1] it feels like cheating.
CL was my preference many years back, but practical usage at the fringes required me to be a SBCL expert. Sadly, I am/was not :-( so now I am a Python Pleb.
[0] https://www.rigetti.com/forest