Open-source project
Open-Cascade-SAS/OCCT avatar
Open-Cascade-SAS/OCCT

Open CASCADE: two licences, three packages, and an expectation you rebuild it

Open CASCADE Technology (OCCT) is an open-source software development platform for 3D CAD, CAM, CAE.

3,175 stars764 forksC++LGPL-2.1

At a glance

What is it?
A C++ platform for 3D modelling, data exchange and visualisation offered under LGPL 2.1 with a special exception file or under a commercial licence, distributed in three package shapes of which only one is usable immediately, documented three different ways including Markdown inside the tree, versioned from a CMake file, and with its newest release named with dots and tagged with underscores.
Who is it for?
Open CASCADE is the right foundation when you need real 3D geometry rather than a mesh library, and the page is unusually direct about the work that implies. Budget for a build: in most cases you compile it yourself for your platform and compiler, so the platform binaries are a convenience for evaluation rather than a deployment.
Can I use it commercially?
Yes, with conditions. LGPL-2.1 is a weak copyleft licence: you can use it inside commercial and closed-source software, but if you distribute changes to its own files, you must publish those changes under the same licence.
Is it still maintained?
Yes. The repository last received commits 4 days ago.
What is it written in?
Mainly C++, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • Open-Cascade-SAS/OCCT3,175 ★ · +259
Star history
Repository2026-09-252026-11-15
Open-Cascade-SAS/OCCT2.9k3.2k

259 Stars in the last 51 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Two ways to licence it and an exception file that matters

The licence section offers a choice and then a warning. The free path is the GNU Lesser General Public License version 2.1, but with a special exception defined in its own file, and the full licence text in a second file named for that version rather than for the word licence. The alternative is the Open CASCADE commercial licence or a contractual agreement. So the answer to whether it is free is yes, with a caveat that the caveat is a separate document you have to find and read, since an LGPL without an exception and an LGPL with one are very different things for a commercial product. The metadata records the LGPL designation and the tree has no file simply named as a licence, only those two specific ones. The closing paragraph is the usual one and worth quoting in spirit: the software comes as is, without warranty of any kind, and the entire risk of using it is on you.

In most cases you are expected to rebuild it

The building section is four sentences and the operative one is the second. In most cases, you need to rebuild OCCT on your platform and compiler before using it in your project, in order to ensure binary compatibility. That is the single most important operational fact on the page, and it reframes everything else about distribution. The platform-specific binary package exists so you can try the library immediately after installation, not so you can link it into a shipped product on a different compiler. The reason is structural rather than cautious: the binary package bundles OCCT together with third-party libraries built on one platform, so what you get is a self-contained set that was compiled as a unit somewhere else. Nothing in the page promises ABI compatibility across compilers, so a project that links the binaries and then switches compiler version inherits the problem.

Three package shapes and only one is immediately usable

The packaging section defines three things you can receive and the differences are not cosmetic. A snapshot of the Git repository contains the C++ headers and sources, the documentation sources, the build scripts and the CMake project files. A complete source archive adds generated documentation in HTML and PDF, plus ready-to-use projects for building on every officially supported platform. A platform-specific binary package adds to that archive binaries of OCCT and of third-party libraries, compiled on one platform, and that is the one described as allowing immediate use after installation. The three are distributed from two places, the project's own release site and its GitHub releases, and both are described as carrying certified versions. The word certified is doing quiet work in the rest of the page, because it implies other versions exist that carry no such claim.

A package from a third party may not be the same thing

One paragraph exists purely to warn you away from convenient installs. You can find OCCT pre-installed on your system, or install it from a package provided by a third party, and the page says plainly that the packaging and functionality of such versions can be different from certified releases, and that you should consult the documentation accompanying your version for details. That is an unusually direct admission that a distribution package is not merely an older build of the same thing. It also means the documentation you should be reading is whichever one shipped with the build you actually have, not the online documentation for the current release. For a library whose API surface is large and versioned by major release, reading the wrong documentation is a slow way to lose an afternoon, so this paragraph is worth more than it looks.

Three ways to read the documentation, one of them Markdown

The documentation section is the longest part of the page and it is structured as a fallback chain. First, two hosted links: the latest version and a version-pinned one for 8.0. Second, if your package includes documentation, open a specific HTML entry file inside it. Third, if it does not, three options. You can generate it from the sources, which needs Tcl and a documentation generator at version 1.8.4 or above available on your path, and which you trigger with a batch file on Windows or a shell script on Linux or OS X. You can generate it alongside the sources instead, which needs CMake and the same generator, and which requires you to enable a specific CMake parameter and point a variable at the generator's executable before building either everything or just the overview target. Or you can read the documentation as plain Markdown that is already in the tree, in a subfolder, or on the project wiki.

The version is a CMake file and the newest tag is underscored

Finding the version number is a one-line section, and the answer is a file rather than a header or a build tool's own metadata: the current version lives in a CMake file under the administration directory. The release list shows why that matters. The three most recent releases are named with a mixture of conventions. Two of them, the 8.0.0 release and its patch, carry the same string as their tag. The newest, version 8.0.1, is displayed with dots while its tag replaces them with underscores. So anything that parses the release name and anything that parses the tag will disagree about that one release, and the version-pinned documentation link points at 8.0.0, one patch behind the newest release. Three releases inside three months is a fast cadence for a library of this size, and the naming is not keeping up with it. The three platforms named as officially supported are Linux, Windows and macOS, which is also the set the source archive's ready-to-use projects are generated for, so a target outside that set means assembling the build yourself from the repository snapshot.

Two bug trackers, two forums and two domains

Development is spread across more places than one would expect, and the doubling is systematic. Bugs can go to GitHub issues or to a dedicated tracker on the project's own site, and either is offered without saying which is authoritative. Discussion can happen on the project's forums or on GitHub discussions, same again. Documentation, the development portal and the tracker all live on one subdomain, while the project's public site is on a completely different domain, so a reader arriving from a search result has to cross a domain boundary to reach anything else. The root of the repository adds two more signals about how the code is managed: a configuration file for a specific third-party review tool, and a list of revisions that should be ignored when the repository assigns blame, which is how a formatting sweep is kept out of the history. The samples directory holds a single readme.

Editorial conclusion

Open CASCADE is the right foundation when you need real 3D geometry rather than a mesh library, and the page is unusually direct about the work that implies. Budget for a build: in most cases you compile it yourself for your platform and compiler, so the platform binaries are a convenience for evaluation rather than a deployment. Read the licence exception file before you ship anything, because the library is offered two ways and the exception file is what makes the free path usable. Ignore any OCCT your distribution packages unless you are prepared for its documentation to differ from the certified releases. And take the version from the CMake file rather than from the release name, since the newest release is displayed with dots and tagged with underscores.

Frequently asked questions

What is an open cascade?

Open CASCADE Technology is a software development platform providing services for 3D surface and solid modelling, CAD data exchange and visualisation. Most of its functionality is available in the form of C++ libraries, and it is aimed at software dealing with 3D modelling, manufacturing and measurement, or numerical simulation.

Is Opencascade free?

Yes. It is free software under the GNU Lesser General Public License version 2.1, with a special exception defined in a separate file in the distribution. Alternatively it may be used under the Open CASCADE commercial licence or a contractual agreement. It is provided as is, without warranty of any kind.

Do I have to build Open CASCADE from source?

In most cases, yes. The page says you need to rebuild it on your platform and compiler before using it in your project to ensure binary compatibility. A platform-specific binary package exists and bundles OCCT with third-party libraries compiled on one platform, which allows immediate use after installation.

Which Open CASCADE packages can I download?

Three shapes: a snapshot of the Git repository with headers, sources, documentation sources, build scripts and CMake project files; a complete source archive that adds generated HTML and PDF documentation and ready-to-use projects; and a platform-specific binary package that adds compiled libraries. Certified versions are offered through the project's release site and through its GitHub releases.

Where is the Open CASCADE version number stored?

In a CMake file under the administration directory, according to the page. The newest published release is 8.0.1, dated 2026-07-30, and its tag replaces the dots in the release name with underscores, while the two preceding releases use the same string for name and tag.

Official sources

  1. License: LGPL-2.1
  2. Open-Cascade-SAS/OCCT on GitHub
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/open-cascade-sas-occt.svg)](https://hysenlabs.com/projects/open-cascade-sas-occt)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/open-cascade-sas-occt.svg)](https://hysenlabs.com/projects/open-cascade-sas-occt)

Was this useful?