Pricing and Eligibility

Published from the source document. Propose an edit through a pull request; direct wiki edits are replaced by the next publication.

APEX pricing and eligibility

Pricing guide for APEX Source Available License 1.1, 24 September 2026. The complete schedule is in LICENSE sections 13 and 14. This page explains those rules; it is not a separate license or accepted commercial Order. The LICENSE and any accepted Order control. See the document guide for the roles of the public license and its summaries.

Tiers

Tier	Annual revenue / eligible use	Monthly equivalent	Annual license fee
Free	Internal production use with revenue up to and including EUR 2,000,000; qualifying research and teaching regardless of revenue; up to 90 days of non-operational evaluation for all organizations	EUR 0	EUR 0
Business	Internal use with revenue above EUR 2,000,000 and below EUR 10,000,000	EUR 179	EUR 2,148
Business Plus	Internal use with revenue at least EUR 10,000,000 and below EUR 50,000,000	EUR 359	EUR 4,308
Custom	Revenue at least EUR 50,000,000, or group-wide / multi-entity use, SaaS, OEM or White Label	Individual quotation	Individual quotation

The monthly amounts are comparison figures only. Business and Business Plus subscriptions are twelve-month licenses, billed annually in advance in EUR, plus applicable taxes. There is no monthly billing or monthly cancellation option in these prices. Custom pricing and scope are agreed individually; the default term is also twelve months, paid annually in advance, unless its agreement expressly provides otherwise.

Standard subscription prices are fixed EUR amounts, presented monthly on the website in both German and English. Perpetual prices are individually quoted in EUR, starting at EUR 8,000. There is no currency switch or exchange-rate API. Revenue eligibility thresholds are also denominated in EUR under the assessment rules below.

At the applicable initial or annual assessment for ordinary internal production use, exactly EUR 2 million qualifies for Free, exactly EUR 10 million requires Business Plus, and exactly EUR 50 million requires Custom. Later revenue growth does not change purchased perpetual rights within their agreed scope. The research/teaching and evaluation exemptions are independent of the revenue bands, but only cover their narrowly defined activities below. They do not authorize a production SaaS, OEM, White Label or group-wide operational deployment.

Perpetual alternative

Offer	One-time license fee
Perpetual license on request	From EUR 8,000; individual quotation

The one-time quote considers company size and deployment scope at purchase. Larger companies and broader deployments are quoted higher; there is no fixed Business Plus perpetual price. The accepted Order records the exact price, purchased version and covered use. This is not usage metering and introduces no per-user, per-site, per-operation or per-run charge. Prices exclude applicable taxes. Free eligibility is unchanged.

The selected perpetual option provides indefinite Internal Use of the specific version identified in the accepted Order, including source access, internal modifications and private internal forks of that version. Standard internal use covers one legal entity and all its own sites. Revenue bands and Custom triggers determine the initial agreement, not recurring charges for the purchased version.

No later revenue true-up. Once purchased, later revenue growth alone does not trigger additional license fees, annual reassessment, a compulsory tier change or a new Custom agreement for the agreed use, including when revenue crosses EUR 10 million or EUR 50 million. The entitlement continues for the purchased version within the agreed scope. Additional legal entities, SaaS, OEM, White Label or other new types of use outside that scope require a separate agreement before expansion. More users, sites, operations or planning volume within the licensed entity's existing scope do not create additional license fees.

Future versions and upgrades published by Qunevo are not included in this version-specific entitlement. They and any services require a separate agreement; no upgrade price or credit has been selected. The Order must identify the purchased version and payment arrangements. Sections 7 to 11 of the LICENSE govern duration, breach, termination, transfers, control changes and legal remedies, preserving the no-revenue-true-up policy above. There is no annual perpetual-license renewal or recurring license fee.

Included scope

• Self-hosted internal use by one licensed legal entity at all of its own locations, including its branches. Separately incorporated affiliates are separate entities.
• Unlimited users, installations, planning runs and planning volume within that scope. No per-site, per-user, per-operation or per-run charges.
• Source access, internal modifications and private internal forks for the permitted use.
• Subscriptions include access to versions Qunevo publishes during their entitlement period. Perpetual licenses cover the specific purchased version and internal derivatives of it. Neither option promises a release frequency, future feature or particular architecture.

The fee does not include individual maintenance, support, response times, an SLA, integration, hosting or customization. Qunevo offers these separately by quotation. The customer's chosen AI model (LLM) and usage may incur additional provider fees, separate from the APEX license. LICENSE section 11 distinguishes gratuitous-use defect exclusions from paid remedies and limits damages subject to express exceptions. These limits do not change prices or eligibility. The LICENSE makes no choice of governing law or exclusive court.

Free use

Small organizations

A single legal entity with applicable annual revenue of no more than EUR 2,000,000 may use APEX productively for its own internal operations. Group revenue and the Custom triggers still apply. Free does not mean non-production only.

Research and teaching

Schools, universities and non-profit research institutions, and people acting on their behalf, including scientists, students and researchers, may use APEX without a license fee for non-commercial academic research, classroom teaching, coursework and associated demonstrations. This exemption has no revenue threshold or 90-day limit.

It does not cover commercial R&D, commissioned operational planning, a paid scheduling service, or an institution's own operational administration or production. Those activities use the ordinary revenue-based tiers or Custom. A commercially funded project is exempt only where the use remains non-commercial academic research and does not deliver operational scheduling or a service to the sponsor; otherwise its scope must be agreed separately.

Evaluation

Every legal entity may evaluate APEX for up to 90 consecutive calendar days, beginning with the first execution for evaluation. This includes organizations that would need Custom for their intended deployment.

Evaluation may include sandbox trials, retrospective comparisons and isolated shadow tests whose outputs are not acted on. It must not control or influence live operations, replace a production system, or provide services to third parties. A live pilot whose results affect actual production is production use and requires the corresponding entitlement from the start.

New installations, versions, accounts or forks do not restart the period. Evaluation does not automatically become a paid license and creates no automatic charge. At the end, further execution requires another applicable entitlement: eligible Free use, a paid standard license or an agreed Custom license. LICENSE section 8 permits limited retention and continued source collaboration after expiry without extending execution rights or permitting operational use of evaluation outputs without an applicable production entitlement.

Revenue measurement

Assessment date. Determine the tier before the first production use. Reassess Free production eligibility annually and subscriptions for each subsequent annual term if one is agreed. Perpetual pricing and eligibility are assessed at purchase; there is no later revenue reassessment or surcharge for the agreed perpetual use. Use the most recent completed fiscal year as of the assessment date, not a rolling twelve-month total or a forecast where a completed year exists.

Revenue. Use total worldwide revenue from ordinary activities recognized in the entity's annual accounts under its consistently applied accounting standards, after discounts, returns and sales taxes/VAT. Revenue means turnover, not profit, company value, funding raised or only the revenue attributable to APEX. If final accounts are not yet available for the latest completed year, use documented provisional figures for that year and correct the classification when final figures become available.

No completed fiscal year. Use a documented good-faith estimate for the first fiscal year and record that basis. Reassess using the latest completed fiscal year at the next annual assessment, as provided in LICENSE section 13.1.

Annual review. For Free production use and subscriptions, ordinary revenue growth or decline alone does not change an accurately established tier or fee during its twelve-month assessment period. Apply the new band at the next assessment. Purchased perpetual entitlements are excluded from annual revenue reassessment and later revenue-growth charges. LICENSE sections 9 and 10 address incorrect declarations and changes of control. Expanding into a deployment outside the licensed scope requires the relevant agreement before that expansion. Subscriptions do not automatically renew; each further term requires an accepted renewal Order.

Records. Keep a reasonable record of the fiscal year, revenue figure, group perimeter and conversion method used. Eligibility can be established through a declaration and proportionate supporting evidence; there is no continuous revenue reporting or usage metering requirement.

Corporate groups and entity scope

Control means direct or indirect ownership of more than 50% of voting rights, or the power to direct an entity's management. A Group consists of the ultimate controlling parent and all entities it controls, including the Licensee. Entities under that common control are affiliates for this schedule.

For a member of a Group, use the Group's worldwide consolidated revenue, eliminating intra-group revenue, for the latest completed group fiscal year. Where consolidated accounts are not prepared, use an equivalent aggregation for that period with intra-group revenue eliminated. A small subsidiary cannot use only its own revenue to avoid the appropriate band. If members have different reporting years, use documented accounting records covering the same group fiscal period; agree any necessary alternative estimation method with the Licensor before relying on a tier. A change of Group of the same licensed entity is reflected at the next annual assessment for Free and subscriptions. It does not create a revenue true-up for a valid perpetual entitlement within its agreed scope. Entity transfers and scope expansion are addressed separately in LICENSE section 10.

Revenue measurement does not enlarge the license scope. Free, Business and Business Plus each cover only one legal entity and its own sites. Shared access, planning or operation for more than one group entity requires Custom regardless of revenue. A single group member may use a standard tier if the consolidated revenue qualifies and no other Custom trigger applies.

Currency conversion

If the applicable accounts report in EUR, use that amount. Otherwise convert the reporting-currency revenue to EUR using the arithmetic mean of daily conversion rates into EUR over the same completed fiscal year:

1. Use the ECB reference-rate series for days in that fiscal year on which the reporting-currency-per-EUR rate is published.
2. For each such day, divide 1 by the reporting-currency-per-EUR reference rate to obtain EUR per unit of reporting currency.
3. Take the arithmetic mean of those daily conversion rates into EUR and multiply by the fiscal-year revenue. Round only the resulting EUR revenue to cents before comparing the thresholds.

For consolidated accounts, convert the consolidated reporting-currency total rather than converting subsidiaries again. Do not use today's spot rate or select a favorable day. For a start-up estimate, use the same method for the twelve months preceding the assessment date until a completed fiscal year is available.

If the ECB does not publish the needed currency or the series is unavailable, agree and record an alternative public central-bank series and equivalent averaging method with the Licensor before relying on a tier. Reference rates here determine eligibility only. Subscription and perpetual invoices use EUR unless expressly agreed otherwise.

Uses requiring Custom

• Revenue of EUR 50,000,000 or more for ordinary internal production use at the applicable assessment date; the no-later-revenue-true-up rule preserves existing perpetual use within its agreed scope.
• Group-wide or other multi-entity operational use, including shared scheduling centers serving separate affiliates.
• SaaS: giving third parties access to APEX functionality, whether hosted, managed or exposed through an API, including a service that runs APEX to perform their scheduling.
• OEM: distributing or embedding APEX or a derivative in a third-party product, appliance or solution.
• White Label: making APEX or a derivative available to third parties under another brand.

These deployment triggers apply regardless of revenue or whether a fee is charged to the third party. Contractors acting only for the Licensee's permitted internal operations are addressed in the license and are not independent licensed beneficiaries. Selling the Licensee's own manufactured goods does not by itself turn its internal planning into SaaS or OEM use. Separately purchased infrastructure hosting for the Licensee's own deployment is not itself a right to offer APEX to others.

The narrowly defined public source collaboration permission in LICENSE section 5 is not itself SaaS, OEM or White Label use. It allows source forks and patches under the same terms without granting executable distribution or third-party production rights. Compiling or obtaining that source does not create an execution entitlement or avoid these revenue bands.