As well as compiled in code from Astrometry.net, PHD2 and indi, ZWO use these deb packages:
asiair_armhf.deb
indi-y_armhf.deb
libgphoto2-6_2.5.27-1_armhf.deb
libgphoto2-port12-2.5.27-1_armhf.deb
nginx_1.11.8_armhf.deb
indi_eqmod-y_armhf.deb
indi_starbook-y_armhf.deb
indi_stargo-y_armhf.deb
python3-ephem_3.7.6.0-7+b1_armhf.deb
libntfs-3g883_2017.3.23AR.3-3_armhf.deb
ntfs-3g_2017.3.23AR.3-3_armhf.deb
libfuse2_2.9.9-1_armhf.deb
fuse_2.9.9-1_armhf.deb
exfat-fuse_1.3.0-1_armhf.deb
ffmpeg_7%3a4.1.4-1+rpt1deb10u1_armhf.deb
libavdevice58_7%3a4.1.4-1+rpt1deb10u1_armhf.deb
libsdl2-2.0-0_2.0.9+dfsg1-1+rpt1_armhf.deb
libxss1_1%3a1.2.3-1_armhf.deb
libcdio-paranoia2_10.2+0.94+2-4_armhf.deb
libcdio-cdda2_10.2+0.94+2-4_armhf.deb
All except for the first would come with licensing requirements.
For example, FFmpeg's first requirement for closed source commercial use is:
Compile FFmpeg without "--enable-gpl" and without "--enable-nonfree"
This will automatically disable any codec whose code license is incompatible with a closed-source binary release.
I checked the FFmpeg build used by ZWO and it has --enable-gpl set, in violation of the license agreement.
I object to a company using 100's of thousands of man hours of other peoples work, without respecting the licenses or recognizing their contributions.
From the FFmpeg FAQ:
Q: Is it perfectly alright to incorporate the whole FFmpeg core into my own commercial product?
A: You might have a problem here. There have been cases where companies have used FFmpeg in their products. These companies found out that once you start trying to make money from patented technologies, the owners of the patents will come after their licensing fees. Notably, MPEG LA is vigilant and diligent about collecting for MPEG-related technologies.