What the Ansys Acquisition of C&R Technologies Means for CRTech Users
Updated
Ansys has acquired C&R Technologies (CRTech), the developer of Thermal Desktop and related heat transfer and fluid flow modeling software. For existing users, the practical takeaway is that CRTech's thermal-centric toolset is now part of Ansys's broader simulation portfolio. The acquisition itself is confirmed on CRTech's own site, but the page does not publish details about licensing changes, roadmap, or support transitions — so any specific impact on your license, pricing, or workflow should be verified with official Ansys or CRTech channels rather than assumed.
What the page confirms
The CRTech homepage carries a heading titled "Ansys Acquires C&R Technologies." That is the extent of the acquisition information available on the page. The rest of the page describes what CRTech's software does, not what changes after the acquisition.
From the same page, CRTech's product identity is:
- Heat transfer analysis — thermal modeling as the core focus
- Thermal radiation and environmental heating — orbital and environmental thermal loads
- Fluid flow design — including two-phase flow capabilities the company describes as a distinguishing feature
- Advanced Design Module — extends the software from producing analytical answers into a component and system design tool supporting parametric studies, design optimization, and model correlation
The page also references mission use cases, including the James Webb Space Telescope and the Phoenix CubeSat Mission, and points readers to a notice about "Changes to Thermal Desktop Technical Support."
What this likely means for users
Because the page does not state post-acquisition terms, the honest answer is: the direction is toward integration into Ansys, but the operational details are not published here. What you can reasonably do is separate what's confirmed from what needs checking.
| Question | What the page tells you | What to do |
|---|---|---|
| Who owns CRTech now | Ansys has acquired C&R Technologies | Confirmed on the page |
| Will Thermal Desktop keep working | Not addressed | Check with official support |
| Will licensing or pricing change | Not addressed | Check with official support |
| Will development continue | Not addressed | Watch official announcements |
| Is support changing | Page links to "Changes to Thermal Desktop Technical Support" | Read that notice directly |
Why the support notice matters more than the acquisition headline
The page explicitly directs readers to a notice about changes to Thermal Desktop technical support. For day-to-day users, support channels and response paths affect work more immediately than corporate ownership. If you rely on Thermal Desktop for active projects, that notice is the concrete item to read first — it concerns how you get help, not just who owns the product.
Practical steps for a current CRTech user
- Read the technical support notice linked from the CRTech site before assuming your current support arrangement is unchanged.
- Check your license terms with your vendor contact or Ansys representative if you need certainty about renewal, seat counts, or entitlements — the page does not cover this.
- Watch official Ansys and CRTech announcements for roadmap or product-integration news rather than relying on third-party speculation.
- Keep project documentation current — model files, version numbers, and any custom scripts — so a future version transition is easier to manage regardless of what changes.
What not to assume
The page does not say the software will be discontinued, renamed, folded into an Ansys product line, or made available under different pricing. It also does not say support will end. Those are common assumptions after an acquisition, but none are supported by the information on this page. Treat them as open questions until Ansys or CRTech publishes specifics.
If your decision depends on a detail — a renewal quote, a support SLA, a migration path — the only reliable source is the vendor. The acquisition is real and confirmed; the consequences for your specific setup are not stated here.