OpenText Core Performance Engineering
LeaderInformation Reimagined
Est 1991|Valuation $6.3B|Raised $14.3B
Information Reimagined
Published Oct 15, 2026
| Starting Price | Not publicly listed (contact sales; usage-based models indicated) | Typically enterprise-quoted; pricing not always published | Public tiers: published entry and pro monthly tiers (vendor-published pricing available) |
| Best For | Enterprises requiring broad protocol coverage and continuity with LoadRunner artifacts; large-scale cloud test execution | Teams prioritizing CI/CD-native continuous performance testing and lower-code workflows (per vendor positioning) | Teams seeking self-serve SaaS with published tiers and strong JMeter compatibility |
| Key Strength | LoadRunner ecosystem continuity and broad protocol support (vendor lineage) | Emphasis on lower-code workflows and CI integration (vendor positioning) | Transparent entry pricing; cloud-based execution and JMeter compatibility |
| Key Weakness | Pricing opacity, reported learning curve, and support responsiveness issues reported by users | Migration messaging may emphasize advantages in ease-of-use; protocol breadth may differ from LoadRunner for some legacy protocols | Cost management considerations at high concurrency levels; plan constraints for heavy usage |
Where OpenText CPE's strengths are observed:
Where competitors often claim advantages (based on competitor messaging and review themes):
Customer community discussions compare LoadRunner/NeoLoad/BlazeMeter on cost and usability. Community anecdotes indicate that some teams find cloud execution and JMeter script imports straightforward on certain platforms; these are practitioner-level anecdotes and should be validated in procurement POCs.