Potential licensing constraints when using PyPrimeMesh in another tool

Hi Mike, thanks again for the quick and helpful reply.

We’ve been looking into PyPrimeMesh, and it definitely seems promising. That said, we’re a bit concerned about potential licensing constraints, especially when it comes to using PyPrimeMesh inside a project like ours.

Specifically, we're building a lightweight FEA automation tool aimed at students and small teams. We'd love to use PyPrimeMesh for .cdb generation, but we’re unsure if it’s intended to be used only within the full Ansys ecosystem, or if there’s any way to use it externally (e.g., as part of a standalone conversion script) without running into redistribution or commercial usage issues.

Would you happen to know how Ansys handles this, or if there’s any flexibility for tools like ours?

_Originally posted by @AltoAuto in https://github.com/ansys/pymapdl/discussions/3888#discussioncomment-13017092_

Start with the licensing question in issue #1014 and the referenced PyMAPDL discussion. No repository file or test is identified; this is complete when the project provides a clear, authoritative answer about standalone use of PyPrimeMesh, redistribution, and commercial usage.

Written by the indexing model from the issue text.