Revenue Sharing

CodeLibra automatically distributes license revenue among all developers in a module's dependency chain. This guide explains how revenue sharing works.

The Basic Model

When a licensee purchases a subscription to your module:

1. They pay a single composite price covering your module and all license dependencies
2. CodeLibra takes a 20% commission from the total
3. The remaining 80% is distributed proportionally to each developer

How Distribution Works

Revenue is distributed based on each developer's module price within the composite total.

Example: Simple Module (No Dependencies)

Your module costs $100/year:

Example: Module with Dependencies

Your module costs $100/year and has two dependencies:

• Dependency A: $50/year
• Dependency B: $25/year
• Total composite price: $175/year

Each developer receives 80% of their module's price, regardless of how many modules are in the chain.

Example: Licensee Has Existing Dependencies

Same scenario, but the licensee already has a license to Dependency A:

Developer A doesn't receive payment because the licensee already has an active license—they were paid when that original license was purchased.

The Commission Structure

CodeLibra charges a 20% commission on all license revenue. This covers:

• Payment processing fees
• Platform infrastructure and maintenance
• License administration and tracking
• Customer support infrastructure

What you keep: 80% of your module's license price

No other fees: There are no setup fees, monthly charges, or hidden costs. CodeLibra only earns when you earn.

When Revenue Is Credited

Timeline

1. Purchase: Licensee completes payment
2. Processing: Payment is verified
3. Credit: Revenue is credited to your account
4. Hold period: 14-day hold for refund window
5. Available: Funds become available for payout

The 14-day hold protects against chargebacks and refund requests. After this period, funds are available for withdrawal.

Visibility

You can see:

• Pending revenue (within hold period)
• Available balance (ready for payout)
• Transaction history
• Per-module revenue breakdown

Renewals

When a subscriber renews:

• Revenue is distributed just like an initial purchase
• If prices have changed, the new prices apply
• If dependencies have changed, the new configuration applies

Example: Your price increased from $100 to $120:

• Original subscribers continue at $100 until renewal
• At renewal, they pay $120, and you receive $96 (80% of new price)

What Happens in Special Cases

Refunds

If a subscriber receives a refund within the 14-day window:

• The transaction is reversed
• Revenue credits are removed from all developers' accounts
• Funds that were held are not distributed

After the 14-day window, refunds are evaluated case-by-case and generally not available.

Chargebacks

If a payment is charged back:

• Revenue is reversed for all developers
• This can affect already-available funds
• Persistent chargeback issues may affect account standing

Module Removal

If you remove your module from CodeLibra:

• Existing licenses remain valid (subscribers keep their rights)
• No new licenses can be purchased
• Pending revenue is still distributed normally

Dependency Changes

If an upstream dependency changes its pricing:

• New composite prices reflect the change
• Your revenue per transaction may stay the same (your price unchanged) but the total transaction size changes
• Existing subscribers see changes at renewal

Revenue Analytics

Your dashboard provides:

Overview metrics:

• Total revenue (all time, this month, etc.)
• Number of active subscribers
• Average transaction value

Per-module breakdown:

• Revenue by module
• Subscriber counts
• Trend analysis

Transaction details:

• Individual transaction records
• Dependency revenue breakdown
• Refund/chargeback tracking

Tax Considerations

You are responsible for tax obligations on your earnings. CodeLibra:

• Provides revenue reports and transaction history
• May provide tax forms as required by law (e.g., Form 1099-K for U.S. developers)
• Reports gross earnings before payout fees

Consult a tax professional for guidance specific to your situation.

Maximizing Revenue

Price Appropriately

Underpricing leaves money on the table. See Setting Prices for guidance.

Maintain Your Module

Active, well-maintained modules:

• Retain subscribers better
• Attract more new subscribers
• Command higher prices

Release Regularly

Each new release:

• Adds value for existing subscribers
• Provides marketing opportunities
• Demonstrates ongoing development

Monitor Dependency Costs

If your dependencies become expensive:

• Your composite price rises
• This may affect conversion
• Consider whether all dependencies are necessary

Common Questions

Why does CodeLibra take 20%?

The 20% covers payment processing (typically 2.9% + $0.30 per transaction), platform costs, and the infrastructure required to run the licensing system. This is competitive with or better than alternatives when you consider total costs.

Can I get a lower commission rate?

Volume-based commission tiers may be available. Check your account settings or contact support for details.

What if a dependency developer doesn't have a payout method set up?

Their revenue accumulates in their account until they set up payouts. Your revenue is unaffected.

Can I see exactly how revenue was distributed for a transaction?

Yes, transaction details show the full breakdown including all dependencies and their shares.

Next Steps

• Payouts — How to withdraw your earnings
• Setting Prices — Pricing strategy
• License Dependencies — Managing dependencies