AGPL core
Understand the core and your hosting choices.
Labeling software becomes part of your operation. License terms, documented interfaces and control of your installation help you understand how it works and plan how to maintain it.
Status: OpenLabelEngine is in pre-beta. The core is licensed AGPL-3.0-only. The source repository is not public, so there is no public download today. Contact the project for the current source and package access path.
The core uses AGPL-3.0
The OpenLabelEngine core carries the GNU Affero General Public License, version 3 only (AGPL-3.0-only). Its terms govern running, modifying and conveying the covered software. The official AGPL-3.0 text is the reference for those conditions.
Section 13 addresses modified versions that interact with users over a network, including an offer of corresponding source to those users. The GNU licensing FAQ explains that requirement. Review the actual license and notices supplied with the version you use.
Evaluate source and package together
For an evaluation, request the exact build, matching source-access details, license and third-party notices together. Record the version so a finding can be tied to the code and package you reviewed.
A project or organization page does not by itself establish that a particular source repository, signed installer or release package is publicly available. Contact the project for the current source and package access path.
Self-hosting gives you operational choices
You can place the Center in your environment and run Automation Services near the printers and data they need. The Center, local service and configured trigger locations determine the connectivity required by each workflow.
- Installation: choose a supplied package and configure addresses, HTTPS and service enrollment.
- Data: maintain the database, stored assets, credentials and access permissions.
- Continuity: plan backup, restore, updates and the dependencies needed during a connection loss.
- Output: evaluate your printer, media, driver where used, and representative label designs.
The license is one part of the decision. Infrastructure, administration, integration and any agreed support also belong in your operating plan.
Commercial scope is a separate agreement
The open-core model distinguishes the AGPL core from separately licensed commercial modules and services. Confirm the current availability, hosting arrangement, support commitments and included features in the actual offer. A roadmap entry does not establish an available module or service.
Review the published pricing information → · Discuss your requirements →
Contribute or report a problem
Use the contribution process and terms supplied with the source version you have. Include the version, a concise reproduction and synthetic sample data for a product issue. Use the security reporting guidance for a vulnerability.
Choose an installation path → · Explore the interfaces → · Plan operation and recovery →