It's an easy setup process. It’s one of the easiest ones to set up. I’d rate it five out of five in terms of the ease of deployment.

It will take hardly two to five days. It depends on the customer and the sources which are needed. We can have one VMware instance or any number of instances where we can deploy the appliance. Then we need to activate those appliances and integrate them with this as a portal already on the cloud. Later, we will need to take a customer’s inventory or network. Based on that, we need to do some OP alpha testing or beta testing. If everything is fine, we can also start the scanning process.

The ease of the process depends on the people. If people understand the setup, it’s easy. If they don’t know it, they need to follow the SOP and then the guidelines. If they are technical, it won’t be hard for them to follow the steps.

I've done multiple implementations. I know the ins and outs of the implementation.

The product was handed over to us with pre-installed configurations. We just mounted our server in the rack and enabled the connectivity. The initial setup was quite easy to manage. We are using a private cloud to optimize our hospital management system. We have discussed with the vendor the solution's scalability from private to public cloud for our future needs. All the infrastructure was installed within 15 days.

We don't install CloudSphere, we have an application running from their environment, and we just use the URL. Using it is kind of tricky at the start when you have to integrate the cloud environments. After that, it's easy. Everything is well labeled with descriptive headlines. The initial integration required some training from the software team so that all environments could be configured into one.

The initial setup for CloudSphere was straightforward, but it required more steps. You need to onboard the customer's infrastructure. You have to create the user account, then the tenant account, and then you have to integrate the subscription with CloudSphere. Setting up the solution requires multiple steps, though the onboarding isn't that complex.

The complexity of the set up is subjective. The initial setup is a matter of the end-user preference, and it's a matter of what the security protocols and what the policy is for a particular company. For example, if you're in Europe or outside the United States, you're subjected to data governance that falls under the GDPR regulations. It's a straightforward protocol for setting up and then providing access to end-users, making sure that whatever it is they access is on a need-to-know basis, least privilege as far as that's concerned. So it's site-specific and it's customer-specific as far as the complexity or the simplicity of it altogether.