ProsperOps vs. VMware Cloud Director

Our firm spends the majority of its cloud budget on EC2 instances, Fargate deployments, and Lambda executions. Automated modifications to discount portfolios based on changes in workloads allow ProsperOops to handle our shifting workloads with ease. In order to meet our net cloud budget requirements, it always follows a high-quality SP (Savings Plan) Portfolio management strategy.

Incentivized

For a CSP it's the best choice. For internal uses, even in presence of different business units, it's not so easy and flexible to manage. It assures a high level of multitenancy, often not needed for internal purposes. But it could be used in this case, just not created for these purposes. Network management is great.

Incentivized

• The arbitrage strategy is effective. It's hard to believe how good the service is.
• It is a plug-and-forget approach for ProsperOps.
• It costs ProsperOps a percentage of the savings they make.

Incentivized

• Manages multi-tenancy very well. You can setup resource pools of compute, network, and storage that are independent of each other.
• Easy to create and manage multiple environments.
• Has lease management technology and can easily set leases and expire them based on pre-configured time frames.

Incentivized

• The inclusion of RDS and Elasticache in cost management is something I'd be all for.
• When it comes to EC2 capacity reservations, ProsperOps only includes reserved instances in the region where we are located.

Incentivized

• Logging, there is a lot of logging but is not always clear where to look for the right logging.
• The syncing of policy, you can't see if or what he did/didn't sync and the status of it.
• More integrations with VMware product (click like Availability)

Incentivized

To see the aggregated costs on AWS billings, we may purchase the service through AWS Marketplace instead of viewing it in ProsperOps' dashboard. Now that we're using it for AWS, we're talking with our clients about adding it to Microsoft Azure, too, so that we can make use of the tool's cloud cost control and visibility capabilities.

Incentivized

Another option was own scripting or maintaining the end users in the backend (vcenter). This costs to much time to maintain (scripting) and has a big change of a Security breach. It was not an option for us either way.

Incentivized

• Our Effective Savings Rate has risen since we started using ProsperOps.
• Our AWS bill savings will cover the cost of the service.
• As much as 95.4% of our compute on-demand costs are covered by ProsperOps, and all of the savings are put to good use.

Incentivized

• vCloud Director requires less IT administration. For example, there isn't a need to maintain esx host. or storage administration like creating luns.
• A negative impact is cost. vCloud Director has a monthly cost for storage, processor core, memory, and licensing.

Incentivized