The CodeLibra License Explained

This guide provides a plain-language explanation of the CodeLibra License—what it allows, what it restricts, and what it means for you as a licensee. This is not legal advice; always refer to the full license text for authoritative terms.

What Is the CodeLibra License?

The CodeLibra License is a commercial software license that permits you to use open-source modules in proprietary software development. It's the "commercial" half of dual licensing on CodeLibra.

When you purchase a CodeLibra License, you receive rights to use the module without the obligations of the open-source license (such as AGPL's requirement to release your source code).

Key Rights Granted

Use Rights

You can:

• Execute and run the module in any environment
• Deploy in production systems
• Integrate into your proprietary applications
• Distribute as part of your products

Development Rights

You can:

• Create derivative works (modifications, enhancements, integrations)
• Build proprietary products incorporating the module
• Keep your code private (no copyleft restrictions)

Sublicensing Rights

You can:

• Distribute to your users who need the module to use your product
• Allow your Affiliates (subsidiaries, contractors) to use for your business purposes

What You Cannot Do

Sublicense Development Rights

You cannot grant your customers or third parties the right to:

• Modify the licensed module themselves
• Create their own derivative works based on the module
• Use the module independently (outside of using your product)

If your customers need to develop with the module, they need their own CodeLibra License. Or, if you're creating a product that others will develop with, see Bundled Licensing for how to enable that through CodeLibra.

Transfer the License

Licenses are tied to your organization and generally cannot be transferred to another entity without the developer's consent.

License Duration and Releases

Subscription vs. Perpetual

The CodeLibra License has both subscription and perpetual elements:

Subscription element:

• You can subscribe annually
• Active subscription gives access to new releases
• You can renew or let expire

Perpetual element:

• Releases published during your subscription are licensed perpetually
• You can use those versions forever, even after subscription ends
• Your existing products continue to work

What "Covered Releases" Means

When you subscribe:

• You're immediately licensed for the current release
• As the developer publishes new releases during your subscription, you're automatically licensed
• These licenses don't expire when your subscription does

After Subscription Expires

When subscription ends:

• Perpetual licenses continue for covered releases
• You cannot use releases published after expiration
• Renew anytime to get new releases

Derivative Works

What's a Derivative Work?

The CodeLibra License uses the copyright law definition: a derivative work is one that requires permission from the copyright holder to create. This includes:

• Modifications to the source code
• Translations or adaptations
• Works that incorporate substantial portions of the module

Your Derivative Works

You can create derivative works of a licensed module for your own proprietary products, and you can distribute those derivative works to users.

However:

• You cannot redistribute the original module separately
• Derivative works incorporating the licensed module have sublicensing restrictions
• Your customers get use rights, not development rights

Sublicensing Explained

Sublicensing is one of the more complex aspects of the license. Here's how it works:

What You Can Sublicense

Use rights: You can allow others to use your product, which necessarily involves using the licensed module.

Example: You build a SaaS application using a CodeLibra-licensed database module. Your customers use your SaaS, and the database module runs as part of it. This is permitted.

What You Cannot Sublicense

Development rights: You cannot allow others to modify the module or create their own derivative works.

Example: You cannot sell a "developer kit" that lets your customers build their own extensions using the licensed module, unless they each have their own license.

Bundled Licensing

If you need to enable downstream development, CodeLibra supports this through bundled licensing. See Bundled Licensing for details.

Patent Rights

The license includes a patent grant:

• If the developer has patents covering the module, you receive a license to those patents
• The patent license is non-exclusive and royalty-free
• It covers making, using, and distributing the module and derivatives

This protects you from patent claims by the developer related to the module.

Trademark Rights

The license does NOT grant trademark rights:

• You can identify the developer and module in factual, non-promotional ways
• You can reproduce copyright notices
• You cannot use the developer's trademarks for promotion without permission

Warranties and Liability

No Warranty

The module is provided "as is":

• No warranty of merchantability or fitness
• No guarantee of error-free operation
• Developer not liable for damages from use

Limitation of Liability

In most cases:

• Neither party liable for indirect, consequential, or punitive damages
• Developer's liability is typically limited to fees paid in the prior 12 months

What This Means

You use the module at your own risk. Evaluate thoroughly before incorporating into critical systems. This is standard for software licenses.

Termination

When the License Can Be Canceled

The CodeLibra License is perpetual and irrevocable by the Developer. Only CodeLibra, Inc. (not the Developer) retains the right to cancel the license under specific circumstances:

• License fee refund is authorized under the Account Terms
• Transaction was unauthorized, fraudulent, or illegal
• Licensee violated the CodeLibra Website Terms, Account Terms, or Acceptable Use Policy
• Licensee violated another binding agreement with CodeLibra, Inc.

Note: There is no cure period. The Developer cannot terminate or revoke the license.

After Cancellation by CodeLibra

If canceled by CodeLibra:

• License is null and void from its inception
• Must immediately cease all use under the CodeLibra License
• May continue using the module under its open source license (if applicable)

Effect on Sublicensees

If the license is canceled:

• Sublicenses for Use rights only may survive if properly granted before cancellation and the sublicensee wasn't involved in the conduct causing cancellation
• Third parties who received distributed products before cancellation may continue using them under their sublicense terms (same condition applies)

Survival

These sections survive cancellation or expiration: Attribution and Notices, Warranty Disclaimer, Limitation of Liability, and General Provisions.

Assignment and Transfer

Your Rights

You generally cannot assign or transfer the license without the developer's consent. This includes:

• Selling the license
• Transferring to another company
• Including in asset sales

Developer's Rights

The developer can assign their rights (e.g., if they sell their business). Your license continues with the new owner.

Acquisitions

If your company is acquired:

• The license's transferability depends on the terms
• Typically requires developer consent

Dispute Resolution

The CodeLibra License incorporates CodeLibra's dispute resolution procedures:

• Mandatory informal resolution first
• Binding arbitration for unresolved disputes
• Class action waiver
• See Website Terms for full details

Key Takeaways

1. You can use the module in proprietary software without copyleft restrictions

2. Your users can use your product (which includes the module)

3. You cannot grant development rights to your users—they need their own license for that

4. Perpetual for covered releases—what you license, you keep

5. Standard disclaimers apply—no warranties, limited liability

6. Read the full license—this summary helps understand concepts, but the full text governs

Common Questions

Can I use this in a commercial product? Yes, that's exactly what the commercial license enables.

Do my customers need their own licenses? Not if they're just using your product. Only if they need to develop with the module themselves.

What if I modify the module? You can modify it for your proprietary products. You can't redistribute your modifications as a standalone module.

Is the license perpetual? For releases covered during your subscription, yes. You need active subscription for new releases.

Next Steps

• Full CodeLibra License Text — The authoritative terms
• Sublicensing — Deeper dive on sublicensing rules
• Bundled Licensing — Enabling downstream development