CloudBolt vs. ProsperOps

Creates dynamic groups and flexible Active Directory configurations. Improves our automation capabilities. Helps us to automate a part of our Active Directory administration process. Helps us to automate the process of registration and cleaning the computer accounts with Active Directory. Helps us to improve the reliability of registration to mitigate failures like retry logic and post validation checks.

Incentivized

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

• Create configuration with Microsoft endpoints.
• Support complex globally distributed multi-domains.
• Create and remove dynamic OU.
• Allows for static text in combination with dynamic content.

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

• Support could be improved on a >tier 1 level
• Logging could be more descriptive/specific
• Stability of the actual server

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

We honestly haven't looked into much. We've been using CloudBolt [Software] for a long, long time. I think we briefly looked into Morpheus but figured it was too much effort to lift everything, communicate it, etc. We selected CloudBolt [Software] because, at the time (and still do), they served our very specific case. We also liked the ability to customize certain aspects of the deployments - that enabled our "power users" to really tweak things just right for their departmental tasks.

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

• We have invested countless man hours to troubleshooting and being support's QA.
• Most of our teams have saved an invaluable amount of time by being able to automate their deployments.
• After the initial time you spend [understanding] all the nuances, the configuring of groups, permissions, etc., does make administering it easier.

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