Library / SDK
open62541/open62541 avatar
open62541/open62541

open62541 patched three release lines in one evening, and its formal certification is a 2017 profile

Open source implementation of OPC UA (OPC Unified Architecture) aka IEC 62541 licensed under Mozilla Public License v2.0

3,282 stars1,484 forksCMPL-2.0

At a glance

What is it?
open62541 is a C implementation of OPC UA that most systems can build against nothing but the standard library. The release history, the directory layout and the quality gates tell you more about adopting it than the feature overview does.
Who is it for?
open62541 is a library, not an application, so it fits teams embedding OPC UA into a product or porting it to an embedded target, and it does nothing for someone who wants a client or server to install. Two things to check before you commit: which release line you are on, since v1.5.9, v1.4.21 and v1.3.22 were all published on 2026-10-04, and what your build pulls in, since encryption support changes the dependency set from the C standard library alone to mbedTLS or OpenSSL.
Can I use it commercially?
Yes, with conditions. MPL-2.0 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 1 day 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

  • open62541/open625413,282 ★ · +50
Star history
Repository2026-09-242026-11-15
open62541/open625413.2k3.3k

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

Editorial analysis

Three release lines were patched inside twenty minutes

The release history shows three separate version lines moving on the same evening. v1.3.22 was published at 19:11:09 on 2026-10-04, v1.4.21 at 19:20:04, and v1.5.9 at 19:33:26, twenty-two minutes from the first tag to the last. That is the shape of a project carrying more than one supported branch: the same fixes are cut for an older 1.3 line, a 1.4 line and the current 1.5 line, so choosing a version is choosing a line rather than picking the newest number. The default branch is master, and the README links its build documentation to a doc/master path, which is where you land for instructions on a branch rather than a tag. A CHANGES.md file sits at the repository root next to FEATURES.md, the features overview the README points at for full detail, so the change record for each line is meant to be read from the repository rather than from release notes.

The core library compiles against C99 headers alone

The dependency story starts narrower than most C projects of this size. The README states that on most systems a bare-bones open62541 requires the C standard library only, and that the core library in src has no dependencies besides the C99 standard headers. Encryption is the part that changes the picture: depending on the build configuration, the library depends on additional libraries such as mbedTLS or OpenSSL. In other words, encryption support is a build-time decision rather than a runtime one, and a build configured without it inherits the small footprint. Everything else that is bundled arrives through the deps directory, where additional libraries are included either as git submodules or internalized directly into the folder, which is why a .gitmodules file sits at the repository root. Their licenses are catalogued separately in deps/README.md, and that file, not the top-level LICENSE, is the one to read if your build switches crypto backends.

Platform code sits in the EventLoop plugin, not in the core

The README claims the library is platform independent because all platform-specific functionality is implemented through exchangeable plugins. The layout backs that up with an explicit split. Architecture support lives in arch, and it is implemented through the EventLoop plugin, which keeps architecture-specific code such as the use of POSIX APIs out of the core library, with ports to different embedded architectures provided there. Default plugin implementations live in plugins, covering integration points such as crypto primitives and storage of the information model, while the headers an application sees are in include and the headers a plugin author needs are in plugins/include. Keeping those two header sets apart is what makes an out-of-tree plugin possible without pulling application headers in. The examples directory shows the EventLoop interface being used directly, with eventloop_glib_minimal.c and eventloop_glib_server.c sitting alongside the standard client and server programs.

The single-file distribution carries whatever your options selected

For integration into existing software, the sources can be amalgamated into a single-file distribution, a pair of open62541.c and open62541.h files that can be dropped into a project. What makes this interesting is the sentence that follows: the functionality included in the single-file distribution depends on the current CMake configuration. The single file is therefore not a fixed artifact with a fixed feature set. Two teams can produce an open62541.c from the same version and get different libraries depending on which options they configured, and the amalgamation inherits whichever crypto backend, plugin set and generated nodeset definitions were active at the time. If you vendor that pair into a product, the file itself becomes the only record of what was included, and the CMake configuration that produced it is what you will need later. The README frames this as the standard source and binary forms plus this one extra form, with past releases of the library available from the project's releases page.

Code generation for the standard's XML runs on Python

The build environment is generated with CMake, and part of what CMake drives is code generation. The README states that some code is auto-generated from XML definitions that are part of the OPC UA standard, and that the code generation scripts use Python as part of the build process. So the toolchain for building from a fresh checkout is CMake plus Python plus a C compiler, even though the resulting library needs none of those to run. The generated material is not a small detail either: node definitions, types and their binary encodings come out of those XML files, which is why the nodeset, nodeset_loader and custom_datatype examples exist as separate directories in examples. The examples tree also carries dedicated directories for access_control, discovery, encryption, events, json_config, lws, pubsub and pubsub_realtime, alongside nine client programs covering asynchronous calls, connect loops, historical access, JSON configuration and subscription reconnect behaviour, plus ci_server.c for continuous integration use.

The zero-issue gates are scoped to the supported features

The README frames code quality as a list of zero targets, and the scoping matters more than the zeroes. Compliance is measured by the Compliance Testing Tool of the OPC Foundation for the supported features, so the claim is bounded by what the project implements rather than by the whole standard. The rest of the list is tooling breadth: zero compiler warnings from GCC, Clang and MSVC with very strict compilation flags, zero unit test issues against a target of more than 80% code coverage, zero issues from clang-analyzer, clang-tidy, cpp-check and Codacy, and zero unresolved issues from fuzzing the library in Google's oss-fuzz infrastructure. Memory checking is covered by Valgrind on Linux, DrMemory on Windows and Clang AddressSanitizer and MemorySanitizer. The last of these bullets stops mid-word after unit te, so the remainder of that line is not written in this file. The badges at the top of the README point at the same gates: a CodeQL workflow, the oss-fuzz issue list, codecov and a Coverity scan, with a .clang-tidy configuration file at the repository root.

The certification on record is a 2017 profile built on v1.4

One sentence in the README carries the project's conformance claim: an example server built with open62541 v1.4 was certified for the Standard Server 2017 Profile by the OPC Foundation, with details at the certification page on the project's site. Two things follow from that sentence. The profile is the 2017 one, and the version it was built on is the 1.4 line, while the current line is 1.5. The 1.4 and 1.5 lines were both patched on 2026-10-04, so the certificate describes something close to the code in the 1.4 branch today, not the 1.5 branch. For an evaluator who needs a document, the README hands off to the website rather than hosting the certificate here, and the same is true of the general introduction to OPC UA and the library documentation, both of which live at open62541.org. Support is likewise split: the community handles public requests on GitHub and the mailing list, with the issue tracker and pull requests as the two named channels.

MPLv2 for the library, CC0 for the plugins and examples

The licensing is spelled out in more detail than most C libraries bother with, and the split is the useful part. open62541 itself is under the Mozilla Public License v2.0, which allows the library to be combined and distributed with any proprietary software, including as a static binary, and only changes to open62541's own files need to be published under the MPLv2 when copied and distributed. Separately, some plugins and examples are in the public domain under CC0, and those can be reused under any license without publishing changes. The repository root carries both LICENSE and LICENSE-CC0 so the two sets can be told apart, and the commercial use section repeats the point about private development in separate files. One clause is worth reading before contributing: the project states that contributors retain their individual copyright, which it presents as the reason future relicensing under different license terms is prevented. o6 Automation GmbH employs the core contributors and sells commercial support around the library.

Editorial conclusion

open62541 is a library, not an application, so it fits teams embedding OPC UA into a product or porting it to an embedded target, and it does nothing for someone who wants a client or server to install. Two things to check before you commit: which release line you are on, since v1.5.9, v1.4.21 and v1.3.22 were all published on 2026-10-04, and what your build pulls in, since encryption support changes the dependency set from the C standard library alone to mbedTLS or OpenSSL. For a conformance argument, the only certificate in this repository is a Standard Server 2017 Profile built on v1.4, and the compliance target is scoped to the features the project supports.

Frequently asked questions

How do I install open62541?

The README does not spell out install steps; it points to the build documentation on open62541.org and to the releases page for past versions. The build environment is generated with CMake, code generation uses Python, and some code is auto-generated from XML definitions of the OPC UA standard.

Is open62541 better than freeopcua?

The repository makes no comparison with freeopcua, so there is nothing to weigh here. What it states about itself: a C implementation of OPC UA under MPLv2 whose core library needs nothing beyond C99 standard headers, with platform specifics behind exchangeable EventLoop plugins.

What license is open62541 under?

The library is MPLv2, which lets it be combined and distributed with proprietary software; only changes to open62541's own files must stay under MPLv2. Some plugins and examples are CC0 and can be reused under any license, and the root holds both LICENSE and LICENSE-CC0.

Does open62541 need any external libraries?

On most systems a bare-bones build needs the C standard library only, since the core library in src has no dependencies beyond C99 headers. Encryption changes that: depending on the build configuration it depends on mbedTLS or OpenSSL. Bundled third-party libraries live in deps, with licenses catalogued in deps/README.md.

Has open62541 been certified for OPC UA conformance?

An example server built with open62541 v1.4 was certified for the Standard Server 2017 Profile by the OPC Foundation. The details are hosted at open62541.org/certification rather than in the repository, and the compliance target in the README is scoped to the features the project supports.

Who provides commercial support for open62541?

o6 Automation GmbH employs the core contributors and offers commercial support services. The project stays open to outside contributions, and contributors retain their individual copyright, which the README presents as the reason future relicensing is prevented.

Official sources

  1. License: MPL-2.0
  2. open62541/open62541 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/open62541-open62541.svg)](https://hysenlabs.com/projects/open62541-open62541)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/open62541-open62541.svg)](https://hysenlabs.com/projects/open62541-open62541)

Was this useful?