OpenText Cloud Management

What differentiates OpenText Cloud Management from other similar products?

The primary differentiator is the design-once, run-anywhere approach. Unlike some competitors that require different templates for AWS, Azure, and on-premises, OpenText uses 'agnostic blueprints.' These blueprints allow you to orchestrate the entire lifecycle—from initial provisioning to scaling and retirement—across heterogeneous environments using a single visual designer.

What is your favorite aspect of this product?

My favorite aspect is the Governance and Cost Control module. It offers a granular 'showback' and 'chargeback' feature that actually maps cloud spending to specific business units or projects. The ability to set automated guardrails such as automatically shutting down non-production environments after business hours has significantly reduced our monthly cloud wastage without requiring manual intervention from the IT team.

What do you dislike most about this product?

The initial setup and learning curve are the biggest hurdles. While the codeless configuration is powerful, the platform itself is quite heavy and requires a sophisticated understanding of infrastructure architecture to implement correctly. For smaller teams or those looking for a simple SaaS tool, this might feel overly complex. Additionally, the user interface, while functional, can feel a bit dated compared to some of the newer, more modern cloud-native startups

What recommendations would you give to someone considering this product?

First, ensure your organization has a clear hybrid cloud strategy; this tool provides the most value when you are managing both on-premises legacy systems and multiple public clouds. Second, invest in training or professional services for the initial blueprinting phase. If you set up your blueprints correctly at the start, the automation will save you thousands of hours, but a rushed implementation can lead to technical debt. Lastly, leverage the integration capabilities early—plug in your existing Terraform or Ansible playbooks rather than trying to rebuild everything from scratch within the tool

What differentiates OpenText Cloud Management from other similar products?

Open Text Hybrid Cloud Management distinguishes itself from other similar products through serval unique features and capabilities like the AI and Automatic, its enhanced security features and also its customizable solutions enable the organization to tailor the platform to our unique and business needs. Opentext add value through content-centric workflows that streamline collaboration and knowledge management. Opentext incorporates tools for Data Loss Protection (DLP), encryption and advanced access control that ensures end-to-end data protection. Open text compatibility with leading cloud platforms such as Azure, AWS and Google cloud.

What is your favorite aspect of this product?

My favorite aspect of this product, the Opentext is it’s seamless integration of content management and its IT operations.

What do you dislike most about this product?

One of the dislike of the product would be it’s complexity and steep learning curves for new users or organizations at large, without prior knowledge and experience

What recommendations would you give to someone considering this product?

A recommendation I would give to someone would be about its seamless content and IT resources management. Also it’s great for complex IT infrastructures, this products gives the flexibility and the integration multi -cloud and hybrid environment needs to dealing with the product.