We're not using it full-blown; the plan is you have the developers to be able to develop an on-prem and then move it over to the cloud. That was a scenario. We stood up these environments so that it would be easier for us to control our internal costs for development so that we're not spitting up these cycles in the cloud and causing more cost versus just building an on-prem and then moving it to the cloud.

Rancher has two main versions which are completely different products. They have some similarities because they have a similar UI and similar concept but are different under the hood. The original Rancher was an orchestration platform for Docker containers based on Cattle and we used that solution for three years extensively for different products and on different projects. We're also now using the Rancher 2 on top of the Kubernetes to manage Docker containers for different customers, for projects, to seize logs, to seize mentorings, to downscale or upscale applications. They provide a great catalog of applications that can be created. We recently used Rancher two for another project that was hosted on top of AWS and on-premise servers. It provides and deploys infrastructures, providing UI for the dev team, the management team, QA team, and enables us to see everything that's going on.

We are using Rancher Labs' for the overall management of our Kubernetes cluster. For example, we manage the production and UAT environment of all our applications or containers.

Rancher Labs is used to deliver containerized applications over a containerized architecture.