Course contentsShow
← Software Engineering
Lesson 1876 of 1,93354. Software Licensing and Intellectual PropertyFree lesson

Dual Licensing and License Exceptions

How projects use dual licensing to solve compatibility issues and grant specific compatibility exceptions.

Dual Licensing and License Exceptions

You'll learn how projects strategically use dual licensing and license exceptions to resolve compatibility conflicts and enable broader adoption.

The Challenge

Sometimes a project's chosen license creates barriers: a GPL library can't be embedded in proprietary software, or two copyleft licenses conflict with each other. Rather than force everyone down one path, projects can offer alternatives.

Dual Licensing

Dual licensing means offering the same code under two (or more) different licenses simultaneously. Users choose which license terms they'll follow.

Common pattern: GPL + Commercial license

  • Open source users: Use under GPL (free, but must share modifications)
  • Commercial users: Pay for a proprietary license (can keep code private)

This monetizes open source while keeping it available to the community. MySQL, Qt, and MongoDB have used this model.

License Exceptions

Sometimes you don't need a completely separate license—just a targeted exception that permits specific uses otherwise forbidden.

Example: The GCC Runtime Library Exception allows code compiled with GCC (a GPL tool) to be distributed under any license. Without this exception, every compiled program would technically need to be GPL too—absurd and unusable.

Another example: The Classpath Exception in OpenJDK allows linking GPL Java libraries into non-GPL applications, solving a major compatibility problem.

When to Use Each

  • Dual licensing: Business model requiring paid option, or bridging fundamentally incompatible user bases
  • Exceptions: Narrow compatibility fix without changing core license philosophy

Both approaches acknowledge that one-size-fits-all licensing doesn't work for every project or user.

Key Takeaway: Dual licensing offers multiple complete license options for the same code, while license exceptions carve out specific permitted uses within a single license—both solve compatibility problems that would otherwise limit a project's reach or viability.