I recently had a chance to speak with Chris Mellor at Block and Files about the emergence of Velero as the standard for Kubernetes data protection. I shared some ballpark estimates of market share across open source and commercial vendors to make my case. These numbers were obtained through diligent market research. They are estimates, but they are not imaginary.

Kubernetes has become the de facto standard for container orchestration and management, providing a powerful platform for deploying and managing containerized applications. One of the key benefits of Kubernetes is its support for namespaces, which allow users to isolate groups of resources within a cluster, providing a level of isolation and resource allocation for different applications or teams.

In the ongoing battle to protect corporate data, you can’t afford to miss a step. I’ve seen, first-hand, what can happen when organizations do miss steps. We are always happy to help them remediate going forward, but there’s a lingering wish that we’d met them sooner.

When we began developing CloudCasa, a Software as a Service (SaaS) platform, for protecting Kubernetes applications, we looked at the data protection landscape and focused on areas that we could improve upon and give back to the user community. We wanted to provide them with a quick and efficient way in which they could start protecting this infrastructure with minimal effort, overhead, and most importantly minimal cost.