Subscriptions and Renewals

This guide explains how CodeLibra subscriptions work over time, including renewals, expirations, and managing your ongoing licensing needs.

How Subscriptions Work

The Subscription Model

CodeLibra uses a subscription model with perpetual components:

Annual subscription: You pay annually to maintain access to new releases and updates.

Perpetual license for covered releases: Releases published during your subscription period are licensed to you permanently, even after your subscription ends.

New releases require active subscription: To access releases published after your subscription ends, you need to renew.

What "Perpetual" Means

When we say your license to covered releases is perpetual:

• You can continue using those versions forever
• You don't need to keep paying to use software you've already licensed
• Your rights to those specific releases don't expire

What it doesn't mean:

• You don't get automatic access to new releases after your subscription ends
• You don't get ongoing support (unless separately arranged)

Example Timeline

Year 1 (subscription active):

• You subscribe in January
• Developer releases v1.0 (February), v1.1 (June), v1.2 (November)
• You're licensed for v1.0, v1.1, and v1.2

Year 2 (subscription expired):

• Your subscription expires in January
• Developer releases v2.0 (March)
• You can still use v1.0, v1.1, v1.2 (perpetual)
• You cannot use v2.0 (no active subscription when released)

Year 2 (later—subscription renewed):

• You renew in May
• Developer releases v2.1 (July)
• You can now use v2.0 (current release at the beginning of your new subscription) and v2.1 (released during your subscription)
• Plus all previously licensed versions

Renewal Process

Approaching Expiration

As your subscription approaches expiration:

• You'll receive email reminders (30 days, 7 days before)
• Dashboard shows upcoming expirations
• You can renew early at any time

How to Renew

1. Go to your organization dashboard
2. Find the subscription approaching expiration
3. Click Renew
4. Review the renewal price (may differ from original if prices changed)
5. Complete payment

Renewal Pricing

At renewal:

• The current published price applies
• If prices increased, you pay the new price
• If prices decreased, you pay the lower price
• Dependency prices are also recalculated

Early Renewal

You can renew before expiration:

• New subscription starts when current one ends
• No overlap charges
• Locks in current pricing

Grace Period

After expiration:

• Short grace period to renew without interruption
• During grace period, new releases aren't licensed
• After grace period, you'd start a new subscription

Managing Active Subscriptions

Viewing Your Subscriptions

Your dashboard shows:

• All active subscriptions
• Expiration dates
• Modules and dependencies included
• License status

Subscription Details

For each subscription:

• Start and end dates
• Releases covered
• Dependencies included
• Price paid
• Renewal options

Multiple Subscriptions

If you have many subscriptions:

• Each is managed independently
• Consider consolidating renewal dates for easier management
• Dashboard provides overview and filtering

When Not to Renew

You might let a subscription expire if:

You don't need new releases:

• The version you have meets your needs
• You're not actively developing with the module
• The module is in a stable state

You're moving away from the module:

• You're replacing it with alternatives
• Your project using it is being discontinued

Cost considerations:

• Budget constraints
• Value reassessment

Remember: Your perpetual licenses to already-covered releases remain valid.

Restarting After Expiration

If you let a subscription expire and later need new releases:

1. Start a new subscription (same as initial purchase)
2. The new subscription licenses releases from that point forward
3. Plus any releases during the gap that you didn't have licensed

Pricing:

• Current prices apply
• No penalty for previous lapse
• Existing dependency licenses still credited

Dependency Considerations

Dependencies and Renewals

When you renew:

• Main module subscription renews
• Dependency licenses are handled according to their own terms
• If dependencies have changed, pricing adjusts accordingly

New Dependencies Added

If the developer adds new dependencies to a release:

• You receive licenses to new dependencies automatically
• Total price may increase to reflect new dependencies
• This happens seamlessly as part of your subscription

Dependency Price Changes

If dependency prices change:

• Affects your renewal price
• Main module price unchanged (unless developer changed it)
• Composite total reflects current dependency prices

Billing and Payments

Subscription Billing

• Annual billing by default
• Payment charged at subscription start
• Renewal payment charged at renewal date

Automatic Renewal

Automatic renewal may be available:

• Keeps subscription active without manual action
• Notified before charges
• Can cancel anytime before renewal date

Failed Renewal Payments

If renewal payment fails:

• You'll be notified
• Grace period to fix payment
• Update payment method and retry
• Subscription lapses if not resolved

Payment Method Updates

To update your payment method:

1. Go to organization settings
2. Navigate to billing/payment
3. Add new payment method
4. Set as default for renewals

Cancellation

You can cancel a subscription:

• No refund for remaining time (past 14-day window)
• Subscription continues until expiration
• Perpetual licenses remain valid
• Won't auto-renew if cancelled

Record Keeping

What to Keep

For compliance and accounting:

• Original purchase confirmations
• Renewal receipts
• License documents
• Invoices

Accessing Historical Records

Your dashboard provides:

• Complete transaction history
• Downloadable invoices
• License document archives
• Renewal records

Audit Readiness

Maintain records showing:

• Active licenses and their coverage
• Historical subscriptions
• Payment documentation
• Version information

Common Questions

What happens to my code if I don't renew?

Nothing changes with your existing code. You're perpetually licensed for releases you had access to. You just can't incorporate newer releases without renewing.

What if a module is removed from CodeLibra?

Your existing licenses remain valid. You simply can't purchase new subscriptions through CodeLibra (though the developer may offer alternatives).

Can I pause a subscription?

Pausing isn't currently supported. You can let it expire and restart later when needed.

Do I get notified of new releases?

Notification options vary. Check module pages or developer communications for release announcements.

Next Steps

• License Verification — Verify and share your licenses
• Purchasing Licenses — Initial purchase details
• Getting Started — Overview for new subscribers