What's Happening to Catalyst and NPAWorks? Reading the Ensora Consolidation

Thousands of ABA practices run on software whose corporate story changed underneath them. This piece assembles what’s publicly documented about it — and is careful about the line between what we can observe and what we can’t. Nobody has written this up for the ABA market, so we did.

The documented timeline

Therapy Brands built an ABA portfolio by acquisition. Catalyst (originally DataFinch) became one of the longest-running dedicated data collection products in ABA; CodeMetro’s NPAWorks and WebABA served practice management. The portfolio even cross-pollinated — an integration between AlohaABA and Catalyst was announced in the Therapy Brands era, reflecting Catalyst’s role as the data layer practices paired with operations platforms.

In April 2025, Therapy Brands became Ensora Health — announced on their site and via press release as a rebrand and unification of the product family. Catalyst’s mobile app was renamed “Ensora Data Collection” in the app stores.

As of July 2026, the ABA products’ public trail has thinned. In checks we ran this week: CodeMetro’s NPAWorks product pages redirect to Ensora’s general site; the Catalyst product pages under the old Therapy Brands domain redirect the same way; and Ensora’s homepage currently centers its mental-health and rehab-therapy products (TheraNest, Fusion) with revenue-cycle, telehealth, and clearinghouse add-ons — with ABA not featured.

What this does and doesn’t mean

Here’s the honest part: a vanishing marketing page is not a vanishing product. Companies consolidate websites for many reasons — brand unification, sales-channel changes, product sunsets, or simple neglect of legacy URLs. We have no documented statement that Catalyst, NPAWorks, or WebABA are discontinued, and existing customers may be receiving continuity communications we can’t see. What we can say: a prospective buyer researching these products today will struggle to find current public information about them — and that itself is decision-relevant.

If you run on these products — or were about to buy

Ask your account contact, in writing: What is the product’s current name and status under Ensora? What does the roadmap look like for the next 24 months? What are the support and data-export commitments if the product line changes? (Our migration guide covers what moving would actually involve — including why testing your exports now, calmly, beats testing them during a forced transition.) If you’re mid-evaluation, the practical move is simpler: make the consolidation an explicit demo question, and weight vendor-stability risk the way you’d weight any other feature.

The bigger pattern

This isn’t an Ensora-only story. ABA software has entered its consolidation era — platforms absorbing point solutions, private equity assembling portfolios, and product names outliving their independent existence. For buyers, the durable lesson is contract-level: notice periods, data-export rights, and support commitments are the clauses that matter most precisely when a logo changes.

We’ve published this from public records, and our correction channel is open — to Ensora most of all. If you’re at Ensora and can clarify the status of the ABA line, we’ll update this piece and the affected listings the moment we can verify it: hello@theabaindex.com.