Getting Started

CodeLibra makes dual licensing simple. Whether you're a developer wanting to monetize your open-source work or an organization needing commercial licenses, the entire process takes just a few minutes.

For Developers

Prerequisites

Before you begin, you'll need:

• A GitHub account (other repository hosts coming soon)
• An open-source project you have the right to license
• A CodeLibra account (free to create)

Step 1: Create Your Account

1. Visit codelibra.com and click Sign Up
2. Sign up with your email or connect directly with GitHub
3. Complete account setup with your display name, organization name, and contact information

Your account is free. CodeLibra only charges commission on license revenue—there are no setup fees or monthly charges.

Step 2: Connect Your Repository

1. From your dashboard, click Onboard Module
2. Select GitHub as your repository host
3. Authorize CodeLibra to access your GitHub account
4. Select the repository you want to dual-license

CodeLibra needs read access to verify repository details and license information. You retain full control of your code.

Step 3: Choose Your Licensing Model

CodeLibra supports two dual licensing approaches:

Classic Dual Licensing

• Your module is available under a copyleft license (e.g., AGPL-3.0) for open-source use
• Commercial users must purchase a CodeLibra License for proprietary development
• Best when you want to ensure commercial users pay for proprietary use

Voluntary Dual Licensing

• Your module is available under a permissive license (e.g., MIT) for all use
• The CodeLibra License is an optional purchase for users who want formal commercial terms
• Best when you want broad adoption with optional paid licensing

If you're switching licenses, make sure you have the right to do so (you must own the copyright or have contributor agreements in place).

Step 4: Configure Your Module

Provide the following information:

• Module name: A display name for your module
• Description: A brief description of what your module does
• Module URL: Link to your project website or documentation (optional)

Step 5: Create a Release

A release represents a specific version of your module that can be licensed:

1. Select a tag or commit from your repository
2. Provide a version identifier (e.g., "1.0.0")
3. Add release notes (optional but recommended)

Each release becomes a licensable unit. Subscribers receive licenses covering all releases during their subscription period.

Step 6: Identify License Dependencies

If your module includes code from other CodeLibra modules, you must identify these as license dependencies:

1. Review your module's dependencies
2. Search for any that are available on CodeLibra
3. Add them as license dependencies

When you add a license dependency:

• Your licensees automatically receive licenses to those dependencies
• Revenue is automatically shared with the upstream developers
• The composite price is shown to potential licensees

Not all software dependencies are license dependencies. See License Dependencies for details.

Step 7: Set Your Price

Set the annual subscription price for your module. Dependency prices are added automatically. Consider the value your module provides to commercial users—you can adjust pricing later (changes apply to new subscribers only).

See Setting Prices for pricing guidance.

Step 8: Publish Your Offer

Once you've configured everything, review all settings and click Publish.

Your module is now available for commercial licensing. When someone purchases a license:

• They receive a legally binding CodeLibra License
• Payment is processed automatically
• Your revenue (80% of the license fee) is credited to your account
• Funds are available for payout after 14 days

Step 9: Set Up Payouts

To receive your earnings:

1. Go to your organization settings
2. Navigate to the Payouts section
3. Connect a payout method (bank account or other supported method)
4. Configure your payout preferences (manual or automatic)

See Payouts for details.

What Happens Next

With your module published:

• Discovery: Your module appears in the CodeLibra catalog
• Licensing: Commercial users can purchase licenses instantly
• Updates: Add new releases as you develop; subscribers automatically get access
• Revenue: Earn 80% of each license fee, with automatic dependency sharing

Quick Tips

• Keep releases current: Publish new releases as you make significant updates
• Update dependencies: If you add new CodeLibra dependencies, update your license dependency list
• Monitor your dashboard: Track licensing activity, revenue, and subscriber statistics

For Subscribers

Who Needs a CodeLibra License?

You need a CodeLibra License when:

• You want to use a CodeLibra-listed module in proprietary, closed-source software
• The module is offered under classic dual licensing (copyleft + commercial)
• You want to avoid the obligations of the open-source license (e.g., AGPL's requirement to release your source code)

You might want a CodeLibra License when:

• The module uses voluntary dual licensing (permissive + commercial)
• You want formal commercial licensing terms even though the permissive license allows your use
• You want the assurances or documentation that come with commercial licensing

What You Get

When you purchase a CodeLibra License subscription:

License Coverage

• Licensed releases: Access to the release available when you subscribed plus all releases published during your subscription
• Perpetual use of covered releases: Your license to use releases published during your subscription doesn't expire when your subscription ends
• New releases: To access releases published after your subscription ends, you'll need an active subscription

License Rights

• Use the module in proprietary software
• Create derivative works for your own proprietary products
• Sublicense to your users for the purpose of using your product (not for their own development)
• Deploy in production without copyleft restrictions

How Licensing Works

Subscriptions

CodeLibra licenses are subscription-based with perpetual components. Pay yearly for continued access to new releases. Releases covered by your subscription remain licensed to you permanently—renew to continue receiving new releases, or let expire if you don't need updates.

Dependencies

If the module you're licensing has dependencies on other CodeLibra modules:

• All dependencies are included automatically
• You receive separate licenses to each dependency
• The total price includes all required licenses
• Existing licenses you hold are credited (no double-paying)

Step 1: Create Your Account

1. Visit codelibra.com and click Sign Up
2. Create an account with your email or connect via GitHub
3. Create or join an organization (licenses are held by organizations, not individuals)
4. Provide organization details and set up billing information

Step 2: Find and Review the Module

Browse the CodeLibra catalog or search for specific modules. On the module's page, you'll see:

• Module description and details
• Open-source license (what's available for free)
• Commercial license pricing
• Dependencies (if any)

Step 3: Purchase Your License

1. Click Subscribe or Get License
2. Review the pricing breakdown (includes all dependencies, minus credits for any you already have)
3. Select your subscription term and complete payment
4. Receive confirmation and license documentation

Managing Your Subscriptions

Your dashboard shows all active subscriptions, expiration dates, covered releases, and included dependencies. Before expiration, you can renew to continue receiving new releases or let expire if you don't need updates (your existing licenses remain valid).

As you adopt more CodeLibra modules, existing dependency licenses are credited automatically.

License Documentation

For each license you receive:

• Unique License ID
• Licensed module and version information
• License holder (your organization)
• Start and expiry dates
• Full license terms
• Verification link

Download documentation as PDF certificates or machine-readable formats for automated compliance. Share verification links with auditors to demonstrate licensing compliance.

Understanding Your Rights

What You Can Do

• Use in proprietary software and distribute to customers
• Internal deployment without limits
• Create derivative works for your proprietary products

What Requires Attention

• Sublicensing limits: Your customers can use your product, but can't independently develop with the licensed module
• Attribution: Follow attribution requirements in the license terms
• Scope: The license covers the specified module(s); different modules need their own licenses

Always refer to the CodeLibra License for complete terms and conditions.

Billing and Refunds

Prices are set by module developers and shown as a single composite price including all dependencies. Invoices are generated for each purchase and accessible from your account settings. Refunds are available within 14 days of purchase; after 14 days, refunds are evaluated case-by-case.

Next Steps

For Developers

• Onboarding a Module — Detailed walkthrough with screenshots
• Setting Prices — Pricing strategies
• License Dependencies — Understanding dependency handling
• Revenue Sharing — How earnings are distributed

For Subscribers

• Purchasing Licenses — Detailed purchasing guide
• Subscriptions and Renewals — Managing ongoing subscriptions
• License Verification — Verify and share your licenses
• The CodeLibra License Explained — Understand the license terms