OpenText Static Application Security Testing
LeaderInformation Reimagined
Est 1991|Valuation $6.1B|Raised $14.3B
Information Reimagined
Published Oct 15, 2026
| Starting Price | Published pricing available from the vendor; typically quote‑based for enterprise customers | Published pricing available from the vendor; typically quote‑based for enterprise customers | Published pricing available from the vendor; often packaged with GitHub plans or available as an add‑on |
| Typical fit | Large enterprises requiring broad language support, governance, and flexible deployment (including on‑prem) | Enterprises seeking an AST platform with emphasis on developer workflows and enterprise features | Organizations standardized on GitHub that require native code scanning and policy enforcement in PRs |
| Key strengths | Mature SAST capability with broad language coverage and centralized program management | Developer workflow integration, end‑to‑end AppSec workflow focus | Tight integration with GitHub workflows and PR‑level scanning |
| Key weaknesses | Cost, operational complexity, and reported triage workload in some environments | Enterprise pricing and platform adoption challenges for some customers | Less suitable for non‑GitHub ecosystems and some legacy build systems |
Areas where OpenText is commonly selected:
Areas where competitors may be selected instead:
Pricing and value comparisons across vendors are context dependent and vary by negotiation, package, and service level; community price references are anecdotal and should be verified directly with vendors.
Market share signals from analyst summaries place OpenText among other established vendors; interpretations depend on market definitions and vendor mapping.