The area they need to focus most on is the capability of assessment and the landing zones. It’s lacking right now.

Cloud transformation has four to five cases, including planning, discovery, assessment, and the MVC, which is called the minimal viable cloud. That comes with the architecture design or landing zone creation, where we will create resources on the cloud which we are provisioning. If we are moving onto the cloud platform, AWS, or zero GCP, we need an account. We need resources to be able to compute the network. Most organizations have their landing zone process and know how to create the resources account, compute the network layer and the security layer. However, this landing zone creation is not there in CloudSphere as a feature. It cannot create any of the cloud providers' accounts or their network security computing as a part of the orchestration layer. That orchestration layer is missing in this product.

It will not discover all the applications, although they also have the catalog. They are constantly announcing their catalog to identify applications based on the service which we are discovering. 50% of the time, the application will discover automatically. However, for the other 50%, we need to find the application based on its running process. That's the automation method that we need to follow and that they call blueprint. We need to create those blueprints and then we need to tag those applications. That is the one process that takes time when we do the discovery. One of the cons of this product is that it will not discover all the applications running.

It will not discover SAP or some kinds of applications that are running on those inside the application of the servers as well.

When we start the scanning of, for example, 500 servers, it will not handle the scan. We need to differentiate the jobs - for example, one job for 100 servers, a second job for another 100 servers, et cetera. We cannot scan the 1,000 servers together. That causes it to take time.

There’s a graph missing. It shows where all the servers have interdependencies; however, when we do actual work, it will not work properly in terms of what we present to the customer.

The solution must have a single management console for the resources and VMs. There should be one portal.

We've had some problems and have been working with the development team to improve multiple issues. The cloud is improving but we're getting errors regularly. The cloud is sometimes very lazy and does not work in certain conditions for some services. They need to improve their development team. CloudSphere is not keeping up with the pace of the cloud and there are a number of services that can't be deployed using CloudSphere. They're things you can deploy from Azure or AWS because they have their own portals. But when you do the same thing from CloudSphere, it's not possible.

The main issue I experienced from CloudSphere was recently resolved, but an area for improvement in the solution is that it lacks the functionality of migrating resources from one public cloud to another. If CloudSphere could provide that functionality, that would be very beneficial to users and companies.