I looked at KID when it came out and was not impressed. I opted using a combination of Microsoft Deployment Tools and WDS for network deployments, its FREE and very versatile.
The main reason I gave up on KID was that in my opinion it was still a beta product when they released it for sale and when I compared the features and cost of KID with MDT/WDS, MDT/WDS won hands down. Microsoft also has a full training and certification path for using their deployment tools, Kaseya only had what was in my opinion a vague installation and user guide. Other requirements included that the KID server at the customer end could not be a Virtual machine or a virtual host and direct external HTTP/HTTPS access to your VSA which did not work in my VSA setup.
Sure you don't have a central Kaseya managed console access for it for all of your customers, but I have figured out how I can use it with Kaseya Agent Procedures to capture images, deploy images and rerun post imaging tasks if they fail. I also now have a "universal" configuration that I build up on over time and that I use for all my deployment servers.
The main benefit with MDT is that you build your reference images on a virtual machine and all the drivers are installed post imaging meaning you could have a single image for all your hardware types (Acer, ASUS, HP, IBM, DELL workstation/laptops) as long as you have the driver sets for them. Microsoft's WIM can also so store multiple deduped images saving you disk space on your deployment server.
And with MDT you can restore captures of larger disks to smaller ones as long as you have enough disk space on small one as it uses the same technology as what they use for Microsoft's installation media. The downside of MDT is you can't deploy Linux but you could do that with WDS if you know how to compile Linux kernels.