Most Frequently Asked Questions (FAQ)

Product Overview

What makes KDDM unique compared to DevOps build pipeline or any free open-source tools on the market?
Three major differentiators of KDDM:

Config Data Transfer: 

Many config entities are hard to transfer (product catalog, portals, business units etc.) Our approach is a 3-level config process: 

  • Entity (filter, update or create) 

  • Attribute (Static, Ignore, Environment Specific, Hierarchical, Hierarchical MultipleRoot,  AutoResolve) 

  • Entity Specific behavior (document templates: Adjust ETC for .docx etc, adx_*, …) 

 Data Maintenance

Large Datasets are difficult to fix after field type changes etc. (Timeouts, Trigger of Workflows) 

Things like setting global filter for server side sync or sync of view states etc. ,can be fully automated with a few clicks. 

Compliance Restrictions:

Custom scripts are often not prepared for enterprise requirements (Proxies, No plain connection string / PW etc.) 
We fully support proxy auth., Service Principles, Release Note generation, deep components versioning (JS, C# Assemblies,...) out of the box. 
Generally speaking, you can meet all requirements with custom scripts additional software (toolbox etc.) for manually post deployment tasks. 

The question is just is it worth it to pay for a tool to do it all without manually interaction.  

Why should we use your tool for our projects?  (Business values)

Our product is perfect for large-scale enterprise projects with complex requirements & compliance restrictions.
Also, if you are a consulting company who are running short of DevOps skills and resources, the tool is a perfect productivity solution.

  • Advance Error Analysis  

  • Automate deployment process (no-code require) 

  • We use Service Principles as preferred authentication method, as the whole process run the clients infrastructure no data is exchanged with our servers.

  • User Access Management to avoid miscommunication mistakes 

What’s in it for you in the end:

  • Effort & Time-saving (up to 70% initial automation effort)

  • Experience CI/CD seamlessly

  • Eliminate failed deployment

=> Increase your efficiency toward release management process which can result in more profitability for your business

What are the benefits of this tool vs dev can just open browser and deploy solutions manually? 

It is easier for everyone to execute the deployment from one centralized location without any post deployment activities.

Azure DevOps Integration

Can the tool be used in Azure Devops pipelines, I only deploy solutions automatically?
Yes. We do support Azure pipeline & release pipeline. 

Does it integrate with Azure DevOps, etc.?

Is it easy to integrate the tool with Azure DevOps?

Yes, the setup time is less than 30 minuntes.

Do you have integration process where deployment can be done automatically?

Yes, different Build Server like Azure DevOps are supported.


From your documentation, it requires installation, do you consider SaaS model? 
Yes, a lightweight client must be installed for the initial configuration. 
The whole execution will be done within Azure Pipelines for example. During the runtime there are no dependencies to any local machine. 

Sometimes it is useful for development purposes to execute a partial deployment/hotfix locally without running a whole azure pipeline. Depends on different use cases. 

Is a solution to manage release from local but also have an option to use cloud ? 
Basically we integrate in any existing SAAS infrastructure with the optional possibility to operation locally for certain tasks. 
(Example: You can configure & run a whole deployment locally and then push the same configuration to DevOps) 

Need help? Contact support