OpenText RightFax Review 2026: Pricing & How It Compares

Is OpenText Fax Worth It in 2026?

A Legacy Institution

OpenText Fax, the product the industry still calls RightFax, is the closest thing enterprise faxing has to a legacy institution. It launched in Tucson in 1992, passed through AVT and Captaris, and landed at OpenText in a 2008 acquisition worth about $131 million. Roughly 900 tracked installations still run it, close to 38 percent of them in healthcare, and nearly nine in ten in the United States.

The Pitch and the Problem

That institutional weight is both the pitch and the problem. The pitch: certified Epic and Veradigm connectors refined over decades, integrations reaching into SAP, Oracle, and even mainframe print queues, and control over where your fax data lives because it lives on your own servers. The problem: everything around that capability is heavy. Versions fall out of full support roughly every five years, the upgrade requires an active support contract purchased through a partner, and in spring 2026 the National Vulnerability Database published CVE-2025-15610, a flaw in a legacy Microsoft framework OpenText Fax uses, covered in detail in the security section below.

Two Products, Two Verdicts

There is a second complication, and it shows up in how OpenText itself splits the portfolio rather than in anything a buyer is told directly. OpenText Fax's own product page markets on-premises and hybrid deployment with deep ERP and EHR connectors. Core Fax has a separate page, a separate developer portal, and separate reseller SKUs, built for the multi-tenant cloud and API scenario a healthcare platform company would actually be shopping for. The two pages do not cross-link into one buying path, and developer.opentext.com publishes Core Fax's REST and SOAP APIs openly while OpenText Fax's own SDKs sit behind a partner download form and a support-portal login. So the honest 2026 verdict is really two verdicts: OpenText Fax remains defensible where on-premises control is a hard requirement, while Core Fax's own marketing targets the cloud and API buyer instead, at a price neither product will state without a quote.

When to Look Elsewhere

For organizations that do not need to own the server, a modern cloud fax service covers the same healthcare and API ground with published pricing instead of a quote process. Fax.Plus is the clearest example in this series: an Enterprise plan with a HIPAA BAA, EHR connectivity, a public API, live AI data extraction and text transcription, and a hosted MCP server for AI agent workflows, with every price on the page. Documo is another dedicated cloud option with published pricing. And for teams already buying a business phone system, RingCentral bundles faxing into its UCaaS platform at published per-user rates. OpenText makes sense when the Epic-era integration depth or on-premises control is the requirement itself.

About OpenText Fax

OpenText is a Canadian enterprise software company with a portfolio spanning content management, cybersecurity, and business networks. Fax entered the picture in November 2008, when OpenText acquired Captaris, the then-owner of RightFax, for roughly $131 million. RightFax itself is older than the web browser: it shipped from Tucson, Arizona in 1992 and built its reputation as the network fax server for hospitals, insurers, and government agencies through the 1990s and 2000s.

One Product, Five Names

Buyers researching this product will meet at least five labels: RightFax, OpenText Fax (the official name since the rebrand), RightFax Connect (the hybrid cloud transmission service), OpenText Fax Private Cloud (the managed hosting option), and OpenText Core Fax (a separate product entirely). The rebrand changed nothing technically; OpenText's own version chart states plainly that RightFax is now marketed as OpenText Fax. But the naming sprawl is real, and it matters, because one of those five names, Core Fax, is not another label for the same product. It is a different product entirely, and the next section explains why that distinction decides what you will actually be sold.

OpenText Fax Is Not Core Fax, and OpenText's Own Site Draws the Line

OpenText Core Fax is a multi-tenant cloud SaaS product with its own portal, its own APIs on developer.opentext.com, and its own pricing structure. It descends from the XMedius acquisition of 2020 and shares nothing operationally with the OpenText Fax server. OpenText's own site structure makes the split explicit: opentext.com/products/fax leads with "OpenText™ Fax (RightFax) is a secure, scalable, digital fax solution," describing on-premises, hybrid, and managed deployment, while opentext.com/products/core-fax is a fully separate page for the cloud SaaS line, describing multi-tenant scale, global data sovereignty, and its own certification stack. That structural separation, maintained on OpenText's own site, tells you more about where OpenText Fax sits in 2026 than any single sales conversation could: it is the product for organizations that need to own the server, and Core Fax is the answer built for everyone who does not.

What OpenText Fax Offers

The OpenText Fax server itself covers desktop faxing through the FaxUtil client and its web version, email faxing through Exchange and Microsoft 365, print-to-fax, MFP integration across Ricoh, Xerox, Konica Minolta, HP, and Canon fleets, OCR with handwriting detection, and workflow automation that routes inbound faxes into EHR and ERP systems. Recent releases added Windows Server 2025 support, a Salesforce connector, and Fax Aviator, an embedded AI assistant for routing, summaries, and data extraction. Version 25.4 was released in November 2025. The platform supports multi-tenant hosting, allowing a single server to serve up to 64 tenants, and can be deployed on-premises, in a hybrid setup through RightFax Connect, or as a fully managed service through Fax Private Cloud.

Everything below reflects what OpenText and third parties had published as of July 2026. Product details, advisories, and terms change, and we are glad to correct anything that has changed.

Getting a Price from OpenText Fax and Core Fax

Neither OpenText Fax nor OpenText Core Fax lists a price anywhere public. Getting one means starting a sales conversation, either directly with OpenText or with a certified reseller. Here is what that process looks like based on what is publicly documented, so you know what to expect before you start it.

What OpenText Publishes Without a Quote

OpenText publishes a credit-consumption data sheet for Core Fax that lists exactly how many credits each action costs: a set monthly credit cost for an inbound number, a higher monthly cost for a toll-free number, a flat credit cost per inbound page, and a higher cost per toll-free inbound page. What it does not publish is what a credit is worth in dollars; that rate is set with a reseller on the ordering document. Reseller marketplaces confirm the same gap from the other direction: according to publicly available listings, named Core Fax license SKUs show no displayed price, routing visitors to a quote request instead. SoftwareOne's own Core Fax listing describes software licensing, monthly subscription, and prepaid credit models side by side, again with no dollar figures attached. So a buyer can learn the shape of the pricing model, in credits, licenses, or subscriptions, without ever seeing what any of it costs in dollars.

What Shapes the On-Premises Cost Stack

OpenText Fax sells through certified resellers on a quote basis, and the cost stack goes far beyond the license itself: Windows Server and SQL licensing, SIP trunks or fax boards, high-availability licensing, disaster recovery testing, annual maintenance, and the administrator time to run it all. Expect the reseller conversation to walk through each of these separately rather than quote one bundled number. One prominent RightFax reseller advertises on its own site that reviewing license selections has cut client implementation costs by 10 to 20 percent, a sign from within the channel itself that a first quote is usually a starting point for negotiation rather than a final number.

Finding a Real Number Before You Start a Sales Process

Maintenance-only support alone can run into the tens of thousands of dollars a year, a figure you can confirm yourself with a search of public government procurement records, since public agencies disclose what they pay. DC's own government data catalog separately classifies its RightFax fax traffic as HIPAA-relevant, describing records of incoming and outgoing faxes between DC Health, the DC Health Benefit Exchange, and other health organizations, which at least confirms real-world deployment scale even where it does not confirm a price.

​

Every other fax service in this series, from the dedicated cloud providers to RingCentral's telecom bundle, publishes both an entry price and how many pages it buys you, so a buyer can see the per-page value without a sales call. OpenText publishes neither figure for either product, which is why this article describes the buying process rather than comparing a number that does not exist.

보안 및 규정 준수

The Certifications in Plain Language

• SOC 2 Type II: an independent auditor watched the company's security controls operate over several months and confirmed they work in practice, not just on paper.
• HITRUST CSF: a healthcare-oriented security framework audit, one of the most demanding in the industry, and effectively a trust shortcut for hospital procurement teams.
• HIPAA: the US law governing patient health information.
• BAA (Business Associate Agreement): the signed contract that makes a vendor legally responsible for protecting that information; without the signature, marketing claims mean nothing.
• PCI DSS: covers the safe handling of payment card data.
• ISO/IEC 27001: the international information security management standard.

What OpenText Documents for Core Fax

On the cloud side, OpenText's own materials describe real depth. Per Core Fax's own product page and a separate OpenText product overview:

• SOC 2 Type II, and SOC 2 plus HITRUST CSF
• HIPAA and PCI DSS support
• TLS 1.2 and AES-256 encryption, in transit and at rest
• ISO/IEC 27001-certified cloud hosting, stated on the separate product overview; the certifying body is not named on that page

That last point is worth flagging: some vendors publish an auditor name directly. Fax.Plus names EY CertifyPoint for both its ISO 27001 and SOC 2 Type II certifications, and RingCentral hosts its certificates on a public trust portal with downloadable documents.

HIPAA 및 BAA

OpenText's Core Fax marketing states the platform supports HIPAA compliance and is designed for regulated industries handling PHI such as patient records and insurance forms. OpenText's public materials do not spell out how the BAA itself is issued, whether it is bundled automatically, arranged through a reseller, or negotiated per contract, so a buyer evaluating this for a healthcare platform should get that specific commitment in writing rather than assume it from the marketing language alone. For comparison, Fax.Plus signs a BAA on its Enterprise plan, and Documo offers one on request.

The Fax-to-Email Trap

One nuance worth flagging for any healthcare buyer, regardless of vendor: receiving faxes as an email attachment is not automatically HIPAA compliant, because standard email may not provide the encryption, access controls, and transmission safeguards required for PHI unless the workflow is configured appropriately. Email faxing through Exchange or Microsoft 365 (the path OpenText Fax offers on-premises) inherits whatever encryption and access controls the customer's own email environment has, which puts the compliance burden on the customer's IT team rather than on a documented vendor safeguard. Fax.Plus addresses this directly on the cloud side: standard email-to-fax is explicitly labeled for non-PHI use, and HIPAA-compliant email delivery requires the Enterprise plan, Advanced Security Controls, a signed BAA, and a dedicated TLS-enforced address that encrypts every message in transit. It is a small feature with an outsized compliance consequence, and worth checking on any fax vendor before anyone emails a patient record.

The OpenText Fax Asterisk

The on-premises product carries a documented security concern. CVE-2025-15610, published in the National Vulnerability Database in spring 2026, describes a deserialization of untrusted data vulnerability involving the .NET Remoting framework used by OpenText Fax (RightFax). According to the NVD entry, it affects multiple OpenText Fax releases, including version branches from 16.6 through 25.4, and may be exploitable remotely without authentication when the relevant service is exposed to the network. At the time of writing, the public guidance we reviewed focused on restricting network exposure. OpenText may have issued updated guidance or a fix since then, so current and prospective customers should confirm the latest advisory status directly with OpenText. In plain language, .NET Remoting is a Microsoft communication framework that has been superseded by newer technologies, and the vulnerability concerns OpenText Fax's use of it. With an on-premises deployment, the customer bears substantial responsibility for securing the server, database, access controls, configuration, and audit environment. This is a very different model from relying on a cloud vendor's independently audited infrastructure.

Apps and Access

Neither OpenText product offers a trial or self-serve signup; a sales process comes before first contact with either product. Here is what exists on each side once you are a customer, per OpenText's own materials and marketplace listings.

Core Fax: Web, Email, Mobile, MFP

Core Fax covers faxing from a web client, from email, from desktop applications including Microsoft Teams and Webex, and from MFPs across Ricoh, Toshiba, Xerox, Lexmark, Sharp, Kyocera, and HP fleets, with secure MFP identity providers like PaperCut and uniFLOW supported. It ships free iOS and Android mobile apps, letting users send and view faxes from a phone or tablet, and inbound faxes can be delivered to an email inbox or viewed directly in the browser without downloading files. Admin features documented by OpenText include subtenant creation, per-tenant login URLs, role-based access, and SSO, SCIM, and Active Directory integration for automated user provisioning.

Independent reviews on G2 add texture the marketing does not: administrators describe successfully wiring the platform (branded there as XM Fax) into document management, database, and transaction-authorization systems, and note that it works smoothly once configured. The same review base flags a real friction point: prepaid subscription plans that expire after one, three, or five years force administrators to estimate page volume in advance, risking either wasted credits or running short before renewal. Another reviewer's advice to prospective buyers was blunt: once implemented, expect a large undertaking that pulls in multiple IT disciplines at once.

OpenText Fax: Desktop, Web, Email, No Native Mobile App

The OpenText Fax server's client surfaces are the FaxUtil desktop application, FaxUtil Web in the browser, email faxing through Exchange and Microsoft 365, and print-to-fax. There is no native mobile app on this product line; mobile access runs through the web client or email. Public administrator guides for OpenText Fax run to hundreds of pages covering WorkServer configuration, dialing rules, conversion engine debugging, and channel licensing, the kind of documentation depth that signals a genuinely admin-heavy product rather than a plug-and-play one. Gartner Peer Insights reviews echo this from the buyer side: some administrators call the product intuitive once set up, while a recurring theme is that Fax over IP still carries real telephony-management overhead compared with typical data networking, regardless of vendor.

How Access Compares

The clearest contrast in this series is with a modern cloud service. Fax.Plus ships native iOS and Android apps rated 4.8/5 and 4.7/5, alongside desktop apps for Windows and macOS, a web app, email-to-fax, MFP support, a public REST API, and integrations with Google Workspace, Microsoft Word, and Zapier, all reachable from a self-serve signup in minutes. Documo connects existing fax machines and MFPs into its cloud platform, and RingCentral's fax lives inside its phone-system apps. On the OpenText side, Core Fax's mobile apps are a real capability, but every path to any OpenText product, mobile app or not, still starts with a sales conversation rather than a signup form.

Support, Contracts, and the Version Clock

The Support Model

Support for OpenText Fax runs primarily through certified resellers and Advantage Service Providers (ASPs) rather than a single OpenText-run help desk. Firms like Advantage Technologies publish their own extended-hours support handbooks, hardware replacement warranties, and professional services packages specifically for RightFax customers, layered on top of OpenText's own Customer Support Portal, which requires an active support contract to reach patches, downloads, and support tickets. That structure means the support experience a buyer gets depends partly on which reseller or ASP they are routed through, not on OpenText alone.

What Buyers Report

We are not going to characterize any single organization's experience with OpenText support here. The more useful thing is to look at the public review record yourself, because the split is the point. Gartner Peer Insights hosts reviews from long-time RightFax administrators, some with decades of deployments across multiple organizations, who describe the product as intuitive to run once configured and praise responsive account teams; one reviewer who has supported RightFax since 1998 calls it the de facto standard for organizational fax needs. Other reviews on the same platform describe a knowledge base that is difficult to use and a first-line contact gate before reaching an actual technician. We are not asserting that either experience is typical; we are pointing you to where the pattern is visible, from different reviewers, across different years, so you can weigh it yourself before signing a multi-year reseller contract.

The Version Clock

Each OpenText Fax version gets about five years of full support, then falls into sustaining maintenance: best-effort support only, no new patches, no security fixes, and no support requests for that version. Upgrading out requires an active support contract, typically arranged through a partner. Version 21.2 was approaching that point around the time of this review. Neither OpenText Fax nor Core Fax publishes a self-serve cancellation flow or a published SLA; both are sold on negotiated reseller terms, so exit terms, notice periods, and porting mechanics are contract-specific rather than posted anywhere a prospective buyer can check in advance. For contrast, Fax.Plus offers self-serve cancellation and number porting both ways, with the terms on its site; RingCentral sits closer to OpenText's end with multi-year telecom terms, though its terms of service are at least published.

데이터 보관 위치 및 보존 기간

OpenText Fax keeps data on infrastructure controlled by the customer, so residency depends on where the organization chooses to deploy and operate its servers. That level of control is one reason the product has remained common in parts of government and healthcare for decades. Core Fax uses a different model, offering regional cloud hosting in the US, Canada, the EU, and Australia to support data sovereignty requirements. For Core Fax customers, the selected hosting region determines where fax data is stored; for on-premises customers, residency remains under the organization's control.

OpenText publishes some retention details for Core Fax, though not enough to answer every compliance question. Its data sheet states that 90 days of fax retention are included by default. Longer retention is available through a separate Fax Retention Plan at reseller-quoted rates, while customers can request a shorter retention period through the service helpdesk. This provides a clear default and a documented way to adjust it, but compliance teams may still want the exact terms confirmed in writing before signing.

The main gaps are around choice and deletion. The materials we reviewed list no hosting regions beyond the US, Canada, the EU, and Australia. OpenText also does not publicly detail what happens to customer data after termination, including deletion timelines, backup handling, or whether it provides certification of destruction. Organizations with strict residency or data-disposal requirements should have those points written into the contract.

How OpenText Data Residency Compares

The sharpest contrast here is with Fax.Plus, where residency is an account setting rather than a platform fact: US data stays in the US by default for US customers, and account admins can choose among more than 20 regions worldwide, including EU, Swiss, Canadian, Japanese, and Australian locations, and move data between them from the dashboard. That matters the moment an organization needs a specific country beyond OpenText's four. Documo documents a US-and-Canada footprint, and RingCentral's global infrastructure is not exposed to the fax customer as a choice. OpenText's four-region footprint with a published 90-day retention default is more documented than most, less controllable than the best.

Enterprise, API 및 의료 분야 자동화

The API, on the Right Product

The developer story depends on which product you mean. The OpenText Fax server offers C and C++ APIs, a COM interface, a REST web API, and file-drop integration modules, installed against your own server, with documentation behind partner download forms and a support portal login.

Core Fax has public documentation: a REST API reference and a separate Management API reference sit on developer.opentext.com, alongside a quick start guide on OpenText's developer forums. We could not find Core Fax specific throughput numbers published anywhere, so buyers planning high volume should confirm capacity directly with OpenText. Webhook-based status callbacks are also discussed on OpenText's developer forums, including customer questions about combining webhook and email delivery for status updates.

의료

OpenText's own product overview states Core Fax is Epic, Cerner, and Veradigm certified, on top of decades of on-premises Epic Community Connect experience on the RightFax side. Connectors for athenahealth and eClinicalWorks are referenced in OpenText's broader marketing but not detailed or priced in the materials we reviewed. Real-time, page-by-page fax delivery is not documented publicly for either product.

AI and Agent Workflows

OpenText markets Fax Aviator, an embedded AI assistant for routing, summaries, and data extraction, on the OpenText Fax product line. We found no equivalent AI feature documented publicly for Core Fax, and no MCP server (the open standard that lets AI agents like Claude operate software directly) listed on OpenText's developer portal for either fax product. Fax.Plus, by comparison, already ships AI Data Extraction and AI Text Transcript live on its Enterprise plan: structured field extraction with up to 20 custom fields, JSON export, and optional automatic processing on incoming or outgoing faxes, billed through a page-based credit system. Fax.Plus's extraction and transcription are live today rather than positioned as a future capability.

How OpenText Enterprise Automation Compares

The connector catalog and Epic depth put OpenText at the top of this series for traditional healthcare integration, and the Core Fax API behind it is public: reference documentation, a management API, and forum-hosted guides. The modern counterpart is Fax.Plus, which pairs a public REST API with published Node.js and Python SDKs, and was the first dedicated fax provider to ship a hosted MCP server, exposing faxing as natural-language actions for AI agents on its Enterprise plan, together with EHR connectivity (Epic, Cerner, athenahealth, NextGen, Kipu EMR) and Fax Streaming, which delivers fax content page by page as it arrives. Buyers choosing between OpenText and a cloud-native platform are picking between incumbent EHR depth and an agent-ready service, and OpenText's remaining gaps (unpriced connectors, an AI feature confined to one product line, no MCP path) are the reasons that choice is worth making carefully.

Alternatives to OpenText Fax

Fax.Plus: Best overall OpenText Fax alternative

A modern cloud fax service covering the workflows OpenText still handles with servers and resellers. Cloud faxing starts at $6.99 per month with a free tier to test, scaling to an Enterprise plan at $79.99 per month with unlimited users, every price published. HIPAA workflows with a signed BAA are available on Enterprise, backed by ISO 27001 and SOC 2 Type II certifications from a named auditor, EY CertifyPoint. Enterprise also brings an advanced fax API with public SDKs, EHR connectivity, Fax Streaming, live AI data extraction, a hosted MCP server for AI agents, and data residency across more than 20 regions.

Best for: Organizations leaving the fax server behind that want audited certifications, a real API, and transparent pricing without a five-year commitment or a quote process.

Documo: Another dedicated cloud fax option

A dedicated fax product with a BAA available and document automation on its upper tiers. The entry Solo plan is sold on annual billing only, a $300 up-front commitment; there is no Android app.

Best for: Teams that want a second dedicated cloud option to compare against.

RingCentral: Fax inside a full phone system

A UCaaS vendor whose faxing is sold either as a fax-only plan or bundled into its phone system, at published per-user rates. Its contracts may be multi-year and include auto-renewal, so read the terms before signing.

Best for: Teams that want faxing inside a business phone system they were buying anyway.