AlbumentationsX License Options

Choose the permissions that fit your use of AlbumentationsX: a commercial agreement or AGPL-3.0-only. Both options give you access to the maintained AlbumentationsX library.

Commercial, proprietary, internal, or production status alone does not require a purchase. The legacy albumentations package remains available under MIT. Its license history is explained below.

On this page

• Commercial coverage
• Institutional procurement
• Quick answers about AGPL and training
• Deployment examples
• Package and license history

What a Commercial License Does

A commercial agreement with Albumentations LLC can let you use, modify, integrate, host, or distribute AlbumentationsX without AGPL source-sharing requirements for the use covered by that agreement.

Choose the coverage your company needs:

• Your team and projects: name the legal entity, users or teams, and projects or model families.
• Your applications and services: agree on rights to integrate and modify AlbumentationsX within proprietary software.
• Your customer deployments: include distribution rights for a named product, SDK, container, appliance, or on-premises installation.

The offer states the scope, price, and term. Affiliates, contractors, additional products, and distribution rights are covered only when included in the agreement. Third-party licenses and notices continue to apply. Support, maintenance, warranties, indemnity, and service levels are included only when expressly agreed.

Request a commercial license quote or email [email protected] with a short description of what you are building and what you want covered. You do not need a completed legal assessment to make an inquiry. Commercial license purchases help support AlbumentationsX development.

Institutional Procurement

The product being licensed is the AlbumentationsX Python library. You install and run it in your own environment; augmentation processes your data there.

For a quote, proposed agreement, or supplier questionnaire, email [email protected]. Include your legal entity, intended use, requested coverage, and the forms or documentation requirements for your review.

Technical documentation for your assessment:

• Security policy and vulnerability reporting
• Supported environments
• Release verification

Short Answers

Do I need to pay because my organization is commercial?

No. Companies can use AlbumentationsX at no charge under AGPL-3.0-only when they comply with its applicable conditions. Revenue, company size, and the words "proprietary" or "production" do not create a payment requirement. A commercial agreement is available when your organization wants the alternative rights it provides.

We only use AlbumentationsX for internal training. Do we need a commercial license?

Internal training alone does not require a purchase. AGPL section 2 permits running the unmodified Program and making or running private covered works that are not conveyed, subject to the license remaining in force. Check separately whether copies reach another legal entity or users interact with a modified version over a network.

You can still choose a commercial agreement for your team's training software, for example when your organization prefers explicitly agreed licensing terms. That choice does not imply that ordinary trained weights need a license from Albumentations.

Can I use AlbumentationsX in an MIT, Apache-2.0, or BSD repository?

The repository label alone does not decide the answer. Independent works can coexist in an aggregate; distributing a combined work can introduce copyleft conditions for that work. Integration, communication between components, and what recipients receive matter. A commercial agreement can grant express rights for the covered integration.

Does any web service have to publish its source?

No. Section 13 addresses remote interaction with a modified version that supports that interaction. It requires offering that version's Corresponding Source to those users. Whether an integrated application forms such a version or combined work depends on the implementation; leaving the library's own files unchanged does not settle that question.

Does "internal use" always avoid AGPL obligations?

No. Private execution and copies that are not conveyed are addressed in section 2. Section 13 can still apply to a modified version used over an internal network. Copies shared with another legal entity, including an affiliate or contractor, need separate consideration.

Is support included in a commercial license?

Support is a separate purchase unless your agreement expressly includes it. A license does not automatically provide an SLA, response-time commitment, maintenance service, warranty, or indemnity.

Does sponsorship include a commercial license?

No. Sponsorship voluntarily supports maintenance and does not change your usage rights. A commercial license is a separate agreement defining the rights your company purchases.

Can contributors' code be offered under commercial terms?

Contributor permissions depend on the agreement accepted for each contribution. The current CLA describes its grants and acceptance requirements; an earlier signature is not automatically acceptance of a later agreement.

Model Weights and Predictions Are Not Automatically Covered

Using AlbumentationsX to augment training inputs does not, by itself, make ordinary model weights, predictions, metrics, or augmented images AGPL. Section 2 covers output only when that output, given its content, is itself a covered work. Output containing protected program code needs separate analysis.

Also check what software accompanies the output. Delivering a Python environment, SDK, container, or application containing AlbumentationsX is different from delivering only weights or predictions. A network service based on a modified version raises its own source-offer question even when its outputs do not contain library code.

Check These Facts First

For a particular deployment, identify:

1. The installed package and version.
2. Whether AlbumentationsX or software combined with it has been modified.
3. Who receives copies, including customers, contractors, and separate legal entities in a corporate group.
4. Whether users interact with a modified version through a network.
5. Whether you deliver library code, a combined application, only outputs, or a mixture.

These facts connect your system to the license clauses below. A label such as "internal ML pipeline" does not replace them.

What the AGPL Text Actually Distinguishes

The GNU AGPLv3 text defines the conditions of the public option:

• Section 2: running the unmodified Program, private covered works that are not conveyed, and the treatment of outputs.
• Sections 4–6: conveying source or object-code copies, including applicable notices, licensing, source, and installation-information requirements.
• Section 5: conditions for conveying a work based on the Program, with a separate distinction for aggregates of independent works.
• Section 13: an offer of Corresponding Source to users interacting remotely with a modified version that supports such interaction.

AGPL permits commercial activity. Academic, personal, or nonprofit use must also comply with the applicable conditions. This guide explains the options; the license text and your signed commercial agreement, if any, control the rights granted.

Do not replace "covered work" with "your entire project"

AGPL does not automatically extend to every file in a company or repository because one module imports a library. Its whole-work conditions concern the covered work. Determine whether integrated components form such a work or remain independent, taking account of the architecture, communication, delivery, and applicable copyright law. Neither a Python import nor an unchanged library file resolves that boundary by itself.

Common Scenarios

For additional interpretation from the license steward, see the GNU licenses FAQ.

The Two Package Lines Have Different Licenses

The legacy package's last release was published on May 27, 2025. The AlbumentationsX repository began on June 19, 2025, and the new package was announced on June 25. The legacy repository was archived in July 2025; its code and published releases remained available under their original terms.

Published AlbumentationsX tags 2.1.3 through 2.3.1 declared AGPL-3.0-or-later in package metadata. Those releases retain the permissions that accompanied them. The AGPL-3.0-only identifier applies prospectively from 2.3.2; earlier versions are not republished with different license metadata.

See the repository licensing history for exact version boundaries and third-party notices. For technical differences, read AlbumentationsX vs Legacy Albumentations.

Questions to Send With a Commercial Inquiry

Start with your company, what you are building, and the team or product you want covered. During follow-up, we can clarify the package version, modifications, customer deliveries, network use, affiliates, and any separately requested support. The resulting offer states the agreed scope, price, and term.

Request a quote or email [email protected].