Operational Considerations

Operationalize Modern On-prem Distribution

In order to be successful with Modern On-prem, vendors need to operationalize the process of delivering KOTS applications to enterprises.

Release Management

Making a SaaS application ready to run in a Modern On-prem environment usually requires developing some additional capabilities among delivery teams. These capabilities will enable teams to unify their SaaS and on-prem delivery efforts, and avoid bifurcating products or code bases in order to support on-prem.

Disconnected Troubleshooting

Whether delivering to an internet-connected cloud VPC or a fully-airgapped datacenter, it’s important to develop competency in disconnected troubleshooting.

Cross-Functional Competence

As software companies make the transition to embrace Modern On-prem, they’ll likely need to involve many different parts of their organization. Each org will have shifting responsibilities in this new world, so we try to cover how the move might impact them. For software vendors making the transition to deliver Modern On-prem as a KOTS application, there are several responsibilities that will need to be owned by various functions within the organization.


When delivering a commercial application to on-prem environments, there are some things to consider around licensing and protecting code and configuration. Because the vendor no longer controls the infrastructure running the application, they are necessarily sending application bits directly to the end customer. Depending on the level of trust, there are varying amounts of licensing protection that can be applied to application code.

Join the Community

If you’re interested in this topic (agree or disagree), we’d love to have you join the community.