Published Oct 15, 2026
The vendor publishes release notes and community posts that indicate ongoing product releases. Buyers should request release cadence, long-term support timelines, and roadmap details relevant to their use cases during procurement.
Service description documents include operational requirements for onboarding and detailed AU matrices that can affect procurement and rollout planning. Buyers should review the service description documentation closely during procurement.
Recurring negative themes across review summaries and community feedback include:
Community posts on public forums contain strong negative anecdotes in some threads (for example, complaints about CI/CD integration and negative support experiences). These represent anecdotal, unverified experiences and should be treated as qualitative signals rather than representative measurements.
Reported reasons for choosing Fortify on Demand include:
Reported reasons for switching away or evaluating competitors include:
Public vendor materials for FoD emphasize product positioning, service descriptions, and release notes more than independently validated, detailed case studies with audited metrics.
Implication: procurement teams should request customer references in their industry, third-party validated outcome metrics if available, and documented measurement methodologies for before/after vulnerability trends.
Vendor community content and marketplace descriptions include claims such as rapid time-to-actionable results for certain scan profiles, support for multiple programming languages, and identification across a range of vulnerability categories. These operational and measurement claims require validation in a PoC or via customer references to confirm applicability to a buyer's environment and definitions.
Fit tends to be mid-market to enterprise organizations with formal AppSec ownership (typical review signals indicate organizations from mid-market to large enterprise with dedicated security or AppSec teams).
Good fit for industries with formal compliance and governance requirements, including financial services, government/public sector, healthcare, and regulated enterprise software providers.
Get a comprehensive analysis of OpenText Fortify on Demand including market position, competitive landscape, adoption trends, and peer benchmarks.
Download full report →G2 listing: a product listing showed ratings on the platform and included user comments noting ease of use and operational visibility, alongside mentions of UI complexity.
TrustRadius: a small number of vetted reviews described the product as a capable on-demand option for application testing and vulnerability management, with some reviewers citing integration ease in their contexts.
Gartner Peer Insights excerpts included mixed feedback; some reviewers described scan results as trustworthy while also reporting concerns such as false positives and slower turnaround compared with developer-centric tools.
OpenText Fortify on Demand (FoD) is a SaaS application security testing service within the OpenText Core Application Security (Fortify) portfolio. It provides multiple application security testing modalities—commonly categorized as SAST (static), DAST (dynamic), and mobile testing (MAST)—and includes workflow and reporting capabilities intended to support vulnerability management and DevSecOps processes.
OpenText describes Fortify on Demand as a cloud-based option to run security testing without maintaining on-premises scanner infrastructure, and as a means to accelerate or expand application security programs using prepaid "Assessment Units" (AUs).
Primary target: mid-market to large enterprises and regulated organizations running formal AppSec programs, especially those that:
Positioning themes observed in vendor materials include scale (many applications), DevOps integration, support for multiple testing methods, and availability of expert review services intended to reduce false positives.