Unmodified internal use
The AGPL expressly permits running the unmodified program. Some organizations still choose commercial terms for procurement policy or a defined contractual scope.
Loading...
Licensing and pricing
AlbumentationsX is available under AGPL-3.0-only and separately negotiated commercial terms. The AGPL permits commercial and internal use subject to its conditions. Commercial terms provide an alternative set of rights for a defined scope.
The software is the same. The difference is the permission set and any services written into the signed commercial documents.
| Decision point | Public AGPL-3.0-only | Commercial terms |
|---|---|---|
| Commercial and internal use | Permitted, subject to the AGPL terms | Permitted for the scope defined in the signed agreement |
| Scope | Depends on the covered work and what you do with it | Names the entities, users, projects or products, deployment model, and term |
| Modifications, network interaction, and copies | May create conditions under the AGPL, depending on the deployment facts | Alternative rights can be defined for the agreed deployment |
| Support, SLA, warranties, or indemnity | Community channels; no paid service commitment | Included only when the order form or a separate schedule says so |
| License price | No license fee | Quoted from scope and any optional services |
This page provides general product information, not legal advice. Your organization decides whether the AGPL fits its deployment. We can explain the commercial option and draft a scope, but we do not decide AGPL compliance for you.
Pricing follows observable scope. Support and contract commitments are priced separately from license rights.
Labels such as “commercial,” “proprietary,” or “production” do not answer the licensing question by themselves.
The AGPL expressly permits running the unmodified program. Some organizations still choose commercial terms for procurement policy or a defined contractual scope.
Copies delivered in a product, SDK, container, appliance, or on-prem package make distribution and combination facts important. Commercial terms can address an agreed product scope.
AGPL section 13 can matter when users interact remotely with a modified version. Commercial terms can define alternative rights for the specified service.
Part of the NumFOCUS ecosystem supporting open-source scientific computing
Registered for U.S. government contracts and grants (UEI: VB8PKZ4KQS73)
No. The AGPL permits commercial and internal use subject to its terms. The relevant facts include the version, modifications, combination with other software, copies or distribution, and remote interaction with a modified version.
The signed agreement and order form define the scope. They can name the legal entities, users or teams, projects or products, deployment and distribution model, versions, and term.
Only when the order form or a separate support schedule includes it. License rights, support, response times, maintenance commitments, warranties, and indemnity are separate decisions.
Commercial licensing is contractual rather than a different feature build. The applicable rights and limits come from the signed documents; the order form identifies the covered deployment.
Pricing follows the agreed scope: named users or teams, legal entities, projects or products, deployment and distribution model, term, and any optional services or contract commitments.
Yes, under the license that applies to the version you evaluate. Evaluation and production are lifecycle stages, not automatic AGPL triggers. A separate evaluation agreement can be discussed if your organization requires one.
Compatibility depends on how the components are combined and distributed. We do not make that legal determination for your project. Commercial terms can define alternative rights for an agreed scope.
Ordinary model weights and predictions are not automatically covered merely because AlbumentationsX was used during training. A bundle that includes library code or other covered material needs separate analysis.
Start with your contact details, what you want help with, and the closest expected use pattern. A project description and initial scope are optional. You can add more details after submitting, and we will ask for package versions, legal entities, or contract requirements only when they become relevant.
We review the deployment facts, clarify any missing scope, and then propose commercial terms when there is a fit. The final rights, services, price, and term appear in the signed documents.
Tell us what you need. You do not need the package version or legal details to start. We usually reply within one business day.
The public AlbumentationsX repository is available under AGPL-3.0-only. Review the exact license and the version you plan to use before making your licensing decision.