Deployment Manager is an alternative to MS Web Deploy, so it is not designed to work with it. There are a number of tools out there to do automated deployments, but Deployment Manager is designed to deploy websites with SQL Server databases. It also deploys .NET applications and can be customised with Powershell. In addition, it also gives you a dashboard view of which application versions are running on different machines. It also stores state- deployment logs of previous deployments, audit history etc.
It seems that deploy manager need its deploy agent and the packaging method.
If you are doing database deployments, Deployment Manager (DM) does not need
the agent installed on the target database machine. For other deployments, DM does need the agent installed.
During a deployment, we pull NuGet packages from a NuGet feed, so this gives you flexibility to have different packaging and publish methods. Some people automate it- they use our tools sqlCI.exe/rgpublish.exe and hook them into their build system to generate and publish packages whenever a build is triggered. We also have add-ins for Visual Studio and SSMS to build and publish web/database packages to a feed configured with Deployment Manager.
Does it support also ms web deploy packaging and deploy agent or not?
DM uses NuGet Packages for deployments. What does MS Web Deploy use for packaging? We do not support Web Deploy agents.