Schedule 11: Avalonia Enterprise Licence

Version 1.1, effective as of 19 September 2026

This Product Schedule forms part of and is subject to the Avalonia UI Master Terms and Conditions. Capitalised terms not defined herein have the meanings given in the Master Terms.

1. Product-Specific Definitions

"Software" refers to Avalonia Enterprise, comprising the complete developer tooling suite, the full UI Component catalogue (as included in Avalonia Pro), and source code access to the Components.

"Tools" refers to the developer tools and applications included in Avalonia Enterprise, in the editions that Avalonia UI makes available under a paid licence. An edition of an Avalonia UI tool or extension that Avalonia UI makes available free of charge, used under that edition's own licence terms, is not one of the Tools.

"Components" refers to the proprietary user interface controls, libraries, and similar software components provided as part of Avalonia Enterprise for incorporation into Avalonia-based applications. Avalonia UI may add to or remove Components from the offering at its sole discretion, subject to Section 4.2 of this Schedule.

"Source Code" means the human-readable source code of the Components provided to the Licensee under this Schedule.

"Named User" means a specific individual (for example, an employee or contractor of the Licensee or of another entity within the Licensed Scope) designated by the Licensee to hold a Named User licence under this Schedule. The licence is issued on a per-Named User basis, and the number of Named User licences held by the Licensee is set out in the Order Form, as increased under Section 2.2 or Section 2.6.

"Redistributable Components" means the runtime portions of the Components that may be distributed as part of the Licensee's applications in compiled form, specifically: Avalonia UI runtime libraries required for rendering UI controls, and any assemblies explicitly designated as redistributable in the Software documentation.

"Affiliate" means any entity that controls, is controlled by, or is under common control with the Licensee, where "control" means direct or indirect ownership of more than fifty percent (50%) of the voting securities or equivalent ownership interests of that entity.

"Application" means a software product or project developed by or for the Licensee or any of its Affiliates, together with the source code repositories in which it is developed.

"Licensed Scope" means the legal entities, business units or Applications identified as the licensed scope in the Order Form or, where the Order Form identifies none, the contracting entity named in the Order Form. The following rules apply:

(a) where the Licensed Scope is described by legal entity or business unit, it includes every Application developed by that entity or business unit;

(b) the Licensed Scope includes every individual who works on an Application within it, whether that individual is engaged by the Licensee, an Affiliate or a contractor; and

"Component Development Work" means:

(a) authoring or modifying XAML or source code that instantiates, configures, customises, extends or derives from a Component;

(b) authoring or modifying styles, themes or control templates that target a Component; or

For clarity:

(i) Component Development Work does not include work carried out solely with the Avalonia open-source framework, nor incidental references to Component types in code that does not create or customise a user interface (for example, a using directive, a type passed through unchanged, or a test that exercises a view model);

(ii) editing a file that contains Component markup or code is Component Development Work only where the edit changes the markup or code that instantiates, configures, customises, extends, derives from or targets a Component;

(iii) where work is carried out by or with an automated tool, AI coding assistant or software agent, it is treated as carried out by the individual who instructs or directs that tool or, where no individual does so, by the individual who accepts its output into the Licensee's codebase; and

(iv) work falls within paragraphs (a) and (b) whether it addresses a Component directly or through a wrapper, derived type, template or other abstraction that exposes the functionality of a Component, regardless of the purpose for which that abstraction was created.

"Non-Development Use" means obtaining, restoring packages for, compiling, building, running, executing, testing, debugging, profiling, packaging, signing, deploying, distributing or operating software that incorporates the Components, where the individual concerned performs no Component Development Work and does not use the Tools.

"Supported Software" means:

(a) the Software; and

(b) the Avalonia open-source framework, in its current major version, in the immediately preceding major version, and in any LTS Release within its LTS Window,

in each case as provided by Avalonia UI and as used in an Application within the Licensed Scope. Supported Software does not include versions of the open-source framework modified by anyone other than Avalonia UI, third-party libraries, or the Licensee's own code. Avalonia UI may at its discretion assist with other versions, but has no obligation to provide fixes for them.

Including the open-source framework in the Supported Software is a commitment to provide the services in Sections 6 to 9 of this Schedule in respect of it. It does not make the framework part of the Software, does not change its licence (which remains the MIT licence), and gives no warranty in respect of it.

"LTS Release" means a release of the Avalonia open-source framework that Avalonia UI designates as a long-term support release, together with the versions of the Components that Avalonia UI designates as corresponding to it. At the date of this Schedule, Avalonia UI designates each major version, and every fourth minor release after it, as an LTS Release. Avalonia UI may change how it designates future releases; a change does not affect a release already designated.

"LTS Window" means, for an LTS Release, the period of five (5) years from the date on which Avalonia UI first makes that release generally available.

"Critical Issue" means a defect or problem that renders the Supported Software substantially unusable or causes a material loss of functionality with no reasonable workaround available, affecting a production environment or blocking a production deployment.

"Machine" means a physical or virtual computer, or a hosted development environment, used by one Named User.

"Supported Platforms" means the platforms listed at https://docs.avaloniaui.net/docs/supported-platforms, as updated by Avalonia UI from time to time.

"Embedded Linux" means Linux distributions running on embedded hardware that are not included in the Supported Platforms list under the Embedded Linux section.

2. Customer Eligibility and Licensed Users

2.1 Organisations Only

This Schedule is available only to entities (corporations, companies, partnerships, and other organisations). Individual customers should refer to Schedule 10A (Avalonia Pro - Individual) or the lower tiers.

2.2 Who Requires a Named User Licence

Within the Licensed Scope, the Licensee must hold a valid Named User licence for each individual who:

(a) uses the Tools;

(b) performs Component Development Work; or

For the purposes of paragraph (a), an individual uses the Tools where the Tools are operated by that individual, or by an automated tool or software agent acting on that individual's instruction.

Where an individual first falls within paragraph (a) or (b) during a Support Period, that individual may commence and continue the relevant activity, and the Licensee must obtain a Named User licence for them within thirty (30) days of the date on which they first fall within that paragraph. Licences obtained under this paragraph are charged pro rata at the rates then applicable and are co-terminous with the current Support Period. An individual must hold a Named User licence before acting under paragraph (c).

2.3 Non-Development Use Requires No Licence

No Named User licence is required for an individual whose involvement is limited to Non-Development Use.

Whether a Named User licence is required is determined solely by the activities an individual performs, and not by that individual's job title, team, department or role. An individual in any role requires a Named User licence if they do any of the things listed in Section 2.2.

By way of illustration only, and without limiting the definitions in Section 1: an engineer who builds, runs, tests, debugs or deploys software containing the Components, but who authors no XAML or code that uses a Component, requires no Named User licence; that same engineer requires a Named User licence if they author or modify XAML or code that instantiates, configures, customises, extends or derives from a Component.

The presence of the Components on an individual's machine, or within a repository, package cache or build artefact to which that individual has access, as a necessary consequence of obtaining or building software that incorporates the Components, does not of itself require a Named User licence.

2.4 Other Licences, Free Editions and Circumvention

A licence held under another Avalonia UI Product Schedule (including a trial licence, or a licence for Avalonia Plus or Avalonia Pro) does not satisfy Section 2.2. Within the Licensed Scope, every individual who uses the Tools or performs Component Development Work must hold a Named User licence under this Schedule, whether or not they also hold a licence under another Product Schedule.

Use of an edition of an Avalonia UI tool or extension that Avalonia UI makes available free of charge, under that edition's own licence terms, is not use of the Tools and does not of itself require a Named User licence.

The Licensee shall not rely on Section 2.3 to permit an unlicensed individual to perform Component Development Work or to use the Tools.

2.5 Open-Source Framework Unaffected

Nothing in this Schedule requires a Named User licence for, or otherwise restricts, the use, modification or distribution of the Avalonia open-source framework under the MIT licence. An individual whose work is limited to the open-source framework requires no licence under this Schedule.

Avalonia UI does not condition access to the open-source framework, or to its security updates, security advisories or software bills of materials, on payment of any fee.

2.6 Changes to the Licensed Scope

The Licensed Scope may be extended by written agreement between the parties to include additional legal entities, business units or Applications. Named User licences must be obtained for those individuals who fall within Section 2.2 within the extended scope, with effect from the date of the extension.

3. Licence Grant

3.1 Grant of Licence

Subject to payment of all applicable fees and continuous compliance with the Master Terms and this Schedule, Avalonia UI grants to the Licensee a non-exclusive, non-transferable, perpetual licence to:

(a) Integrate and Use. Install and use the Software (including Tools and Components) for developing software applications and integrating the Components into such applications.

(b) Reproduce and Distribute in Executable Form. Reproduce, embed, and distribute the Redistributable Components as part of the Licensee's own software applications, in executable (compiled) form only, and solely as an integral part of those applications. Distribution is permitted only as part of the application's binary or installation package, not as a standalone product or library. End-users may install and use applications incorporating the Redistributable Components without additional runtime or distribution fees.

(c) Perpetual Rights. The rights granted above are perpetual for versions obtained during a valid Support Period. Applications developed and distributed under this licence may continue to be used indefinitely, subject to the termination provisions in the Master Terms.

3.2 Named User Licence Requirement

The licence is per Named User. Use of the Tools, access to the Source Code, the performance of Component Development Work, and the raising of support requests are reserved to Named Users, and the Licensee shall not allow multiple individuals to share a single Named User licence. Non-Development Use is permitted in accordance with Section 2.3. This Section applies in respect of every individual, whether inside or outside the Licensed Scope.

A Named User licence may be used only in connection with Applications within the Licensed Scope. Where a Named User is to use the Software on another Application, the Licensed Scope must first be extended under Section 2.6 to include it.

A Named User may install the Tools on more than one Machine (e.g., work computer, home laptop) for that Named User's sole use.

3.3 Licence Reassignment

A Named User licence may be reassigned to a different individual subject to:

(a) A ninety (90) day cooldown period from the most recent assignment;

(b) Submission of the reassignment request through the Avalonia UI Customer Portal;

(c) Immediate cessation of use by the previous Named User and removal of all installations from machines solely used by that individual; and

(d) No circumvention of the per-Named User licensing model.

The cooldown period in paragraph (a) does not apply where the previous Named User has ceased to be employed or engaged by the Licensee or by another entity within the Licensed Scope, or has ceased to work on any Application within the Licensed Scope.

3.4 Build Servers and Continuous Integration

The Licensee may install and use the Software on automated build machines and CI servers without purchasing a separate Named User licence, provided that:

(a) The build server is used solely for automated compilation, testing, packaging, and deployment, with no interactive use;

(b) Every individual who uses the Tools or performs Component Development Work holds a valid Named User licence;

(c) The build server does not provide interactive access to the Software or expose its functionality to unlicensed users; and

(d) The build server exception is not used to circumvent the Named User licensing model.

This exception covers compilation, testing, packaging and deployment only. Code authored or modified by an automated tool or software agent, wherever it runs, is attributed to an individual under the definition of Component Development Work.

3.5 Platform Scope

Each Enterprise licence includes the right to develop, deploy, and run applications on all Supported Platforms, plus Embedded Linux as described in Section 8 of this Schedule.

4. Source Code Licence

4.1 Scope of Source Code Grant

Avalonia UI grants the Licensee a non-exclusive, non-transferable licence to access and internally use the Source Code solely for understanding, debugging, and troubleshooting. The Licensee may modify the Source Code for internal use only and may compile such modifications for use in its own applications. Distribution of modified object code is permitted only as a replacement for corresponding Redistributable Components within the Licensee's own applications.

4.2 Component Catalogue Changes

Avalonia UI may add new Components to or remove existing Components from the offering at its sole discretion. Removal of a Component does not affect the Licensee's perpetual rights to versions of the Software that included that Component, but Avalonia UI has no obligation to continue developing, maintaining, or supporting removed Components. Source Code access for removed Components ceases at the end of the Support Period in which the removal occurs.

4.3 Redistribution Prohibited

The Licensee shall not distribute, publish, licence, or otherwise make the Source Code or any derivative works thereof available to any third party. Redistribution of object code compiled from modified Source Code is permitted only as an embedded component of the Licensee's own application.

4.4 Confidentiality and Security

The Source Code constitutes Avalonia UI's Confidential Information and contains valuable trade secrets. The Licensee must maintain its confidentiality, limit access to authorised Named Users, and refrain from storing the Source Code in any publicly accessible location.

4.5 Competition Restriction

The Licensee shall not use the Source Code to create any competing software products, developer tools, component libraries, or frameworks that replicate or compete with Avalonia UI's commercial offerings.

4.6 Ownership and Derivative Works

Avalonia UI retains all rights in and to the Source Code. The Licensee hereby assigns to Avalonia UI all rights in any corrections, modifications, or derivative works of the Source Code.

4.7 Technical Requirements for Modified Code

Any object code compiled from the Source Code or derivatives:

(i) must be obfuscated using a commercially reasonable obfuscation tool;

(ii) may not include "AvaloniaUI", "Avalonia UI", "Avalonia Pro", or "Avalonia Enterprise" in assembly names, namespaces, or publicly visible identifiers;

(iii) must preserve all original copyright notices and proprietary markings; and

(iv) may only be distributed as an embedded, non-extractable component of the Licensee's application.

4.8 Termination of Source Code Licence

Upon termination of this Schedule, expiration of the Support Period, or any lapse in support coverage, the Licensee must:

(i) immediately cease all use of the Source Code;

(ii) permanently delete all copies of the Source Code; and

(iii) upon request, certify in writing that all copies have been destroyed.

5. Affiliates and Licensed Scope

Affiliates of the Licensee may use the Software under this Schedule only where they are included in the Licensed Scope. The Licensee remains responsible for compliance with this Agreement by every entity and individual within the Licensed Scope, and by any other individual to whom it makes the Software available.

Section 2.2 requires Named User licences only for individuals within the Licensed Scope. It does not require the Licensee to obtain licences for individuals outside the Licensed Scope, and their use of the Avalonia open-source framework, or of other Avalonia UI products under their own Product Schedules, is unaffected by this Schedule.

That limit applies to the requirement in Section 2.2 only. Individuals outside the Licensed Scope may not, in reliance on this Schedule, use the Tools, perform Component Development Work, access the Source Code or raise support requests, and any use they make of Avalonia UI's commercial products must be licensed under another Product Schedule. Sections 3.2, 4, 10 and 11 apply to the Licensee in respect of every individual, whether inside or outside the Licensed Scope.

Where an individual outside the Licensed Scope uses the Software without a licence, Section 11.4 applies, and the Licensee must, within thirty (30) days of becoming aware of that use, either extend the Licensed Scope under Section 2.6 or bring that use to an end.

6. Support and Service Level

6.1 Support Period

Purchase of an Enterprise licence includes access to Software Updates, and to support services for the Supported Software, for an initial period of twelve (12) months from the Effective Date.

6.2 Support Channels

During the Support Period, the Licensee is entitled to:

(a) Email support at [email protected];

(b) Access to a private issue tracker for the Licensee's account; and

(c) Software Updates released by Avalonia UI.

Support requests may be raised only by Named Users, and must relate to Supported Software as used in an Application within the Licensed Scope. A Named User may raise a request that arises from the work of other individuals within the Licensed Scope. Avalonia UI may decline to respond to requests received from individuals who are not Named Users, or that relate to Applications, teams or entities outside the Licensed Scope.

6.3 Standard Response Time

Avalonia UI will use reasonable efforts to respond to support requests within one (1) Business Day of receipt.

6.4 Critical Issue Response

Each Enterprise account is allocated three (3) Critical Issue escalations per twelve-month Support Period. When the Licensee designates an issue as a Critical Issue (and the issue meets the definition in Section 1), Avalonia UI will use reasonable efforts to respond within eight (8) Business Hours of receipt. Unused Critical Issue escalations do not carry over to subsequent Support Periods.

6.5 Emergency Bug Fixes and Hot Patches

For issues that qualify as Critical Issues, Avalonia UI will use reasonable efforts to provide emergency bug fixes or hot patches where commercially practicable. Emergency fixes may be delivered as interim patches pending inclusion in a regular Software Update.

6.6 Best-Effort Issue Prioritisation

In addition to the SLA commitments above, Avalonia UI will make a best-effort attempt to prioritise GitHub issues logged by Avalonia Enterprise customers. Priority will only be given to issues that include a reproducible bug report.

6.7 Renewal of Support

At the end of each twelve-month Support Period, support continues for a further twelve months upon receipt of the applicable renewal fee. Avalonia UI will provide at least thirty (30) days' notice of the upcoming renewal and the applicable fees. There is no automatic charge, and the Support Period is not extended without payment of the renewal fee.

Avalonia UI has no obligation to offer renewal and may, in its sole discretion and for any reason, decline to renew support. If Avalonia UI declines renewal, support will end at the end of the then-current Support Period.

6.8 Lapse of Support

If the Licensee does not renew support, the perpetual licence continues for the version of the Software in the Licensee's possession at the time support lapsed. However, the Licensee will no longer receive Software Updates, patches, support services, or any of the services described in Sections 7, 8, or 9 of this Schedule.

7. Technical Engagement Services

The following services are included in the Enterprise licence during each active Support Period and may be requested by a Named User. All services described in this Section 7 operate on a "use it or lose it" basis: unused allocations do not carry over to subsequent Support Periods and are not refundable.

7.1 Annual Architectural Audit

The Licensee is entitled to one (1) architectural audit per twelve-month Support Period. The audit consists of a review by Avalonia UI technical staff of the architecture of one Application within the Licensed Scope, nominated by the Licensee, with written recommendations. The Licensee must request the audit in writing through the Customer Portal. Avalonia UI will schedule the audit within a reasonable timeframe, subject to availability.

7.2 Quarterly Technical Check-Ins

The Licensee is entitled to one (1) technical check-in per calendar quarter during the Support Period. Technical check-ins are brief sessions (typically 30 to 60 minutes) with Avalonia UI technical staff to discuss technical questions, upcoming releases, and best practices. The Licensee must schedule check-ins through the Customer Portal.

7.3 Video Consultations

The Licensee is entitled to four (4) video consultations per Named User licence per twelve-month Support Period, up to a maximum of twelve (12) consultations in aggregate per Support Period. The allocation attaches to the licence and not to the individual, so reassigning a licence does not create a further allocation. Video consultations are scheduled sessions with Avalonia UI technical staff to address specific technical questions or challenges. The Licensee must request consultations through the Customer Portal, and scheduling is subject to availability.

8. Expanded Platform Support

8.1 Embedded Linux Support

In addition to the Supported Platforms, the Enterprise licence expands support coverage to include Embedded Linux distributions not listed in the Supported Platforms under the Embedded Linux section. This includes assistance with porting, configuration, and troubleshooting of the Supported Software on qualifying embedded Linux environments.

8.2 Reasonable Efforts

Embedded Linux support is provided on a reasonable-efforts basis. Avalonia UI does not guarantee that the Supported Software will function on all embedded Linux configurations and reserves the right to designate certain configurations as unsupported after evaluation.

9. Additional Enterprise Benefits

9.1 IP Indemnification

Avalonia UI shall defend, indemnify, and hold harmless the Licensee against any third-party claim that the Software (in unmodified form, as provided by Avalonia UI) infringes any patent, copyright, or trade secret of a third party. This indemnification is subject to and governed by the terms set out in Section 3.5 of the Master Terms, as supplemented by this Section. Section 3.5 of the Master Terms applies to the Licensee under this Schedule notwithstanding the "Applicability" paragraph of that Section.

For the avoidance of doubt, this indemnification does not extend to: (a) any modification of the Software by the Licensee (including modifications to the Source Code); (b) combination of the Software with third-party products not provided by Avalonia UI; (c) use of the Software in a manner not contemplated by the documentation; or (d) any version of the Software other than the most current version, the immediately preceding major version, and any version that corresponds to an LTS Release within its LTS Window.

The Avalonia open-source framework is not part of the Software for the purposes of this Section.

9.2 Product Roadmap Access

The Licensee may request access to Avalonia UI's product roadmap by submitting a written request to [email protected]. Upon receipt, Avalonia UI will schedule a call to share relevant roadmap information. Product roadmap information constitutes Avalonia UI's Confidential Information and is subject to Section 5 of the Master Terms. The roadmap is provided for informational purposes only and does not constitute a commitment to deliver any specific features, products, or updates.

9.3 Long-Term Support

During the Support Period, Avalonia UI will:

(a) where it releases a fix for a security vulnerability in the current release of the Supported Software, provide a corresponding fix for each affected LTS Release that is within its LTS Window, within a reasonable time having regard to the severity of the vulnerability; and

(b) use reasonable efforts to backport critical stability fixes to each LTS Release within its LTS Window, and critical security and stability fixes to the immediately preceding major version of the Supported Software ("N-1") where that version is not itself an LTS Release.

Where a security fix cannot reasonably be backported to an LTS Release (for example because it depends on an architectural change, or on a third-party dependency that no longer receives fixes), Avalonia UI will instead provide a mitigation, a workaround or a supported upgrade path to a release that contains the fix.

Avalonia UI determines, in its sole discretion, which stability fixes are critical and technically feasible to port. Avalonia UI makes no commitment to backport feature enhancements or minor bug fixes, or to provide fixes for an LTS Release after its LTS Window ends. Support beyond the LTS Window may be available under a separate agreement.

Security fixes to the Avalonia open-source framework are released publicly under the MIT licence. The Licensee's entitlement under this Section is Avalonia UI's commitment to produce those fixes for LTS Releases; access to them is not conditional on payment.

10. Licence Restrictions

In addition to the restrictions in Section 4 of the Master Terms:

10.1 Competition Restriction

The Licensee shall not use the Software primarily to develop, test, or provide a Competing Product or Hard Fork.

"Competing Product" means any product, package, extension, component library, toolkit, or developer tool that the Licensee distributes to third parties and that is intended to replace, replicate, or serve as a substitute for Avalonia UI's commercial offerings.

"Hard Fork" means a fork of an Avalonia UI open-source project that is published to NuGet or any other package feed and positioned as a replacement for the original project.

This restriction does not prevent the Licensee from: building applications for end users; providing consulting or development services; evaluating Avalonia UI alongside alternatives; or contributing to non-competing open-source projects.

10.2 Minimum Functionality Requirement

Applications incorporating Redistributable Components must provide primary and substantial functionality beyond the Software itself. The Licensee may not create applications that consist primarily of the Software's UI Components or provide access to such Components for third-party developers.

10.3 No Shared Use of Development Tools

The Licensee may not share, pool, or otherwise allow any person other than the designated Named User to access or use the Tools, regardless of whether access is concurrent or sequential.

10.4 Licence Key Restrictions

The Licensee shall not share, distribute, or otherwise make available any Licence Keys to individuals who are not licensed Named Users under this Schedule.

11. Compliance

11.1 Records and Attestation

The Licensee shall maintain accurate records of Named Users and of the deployment of Redistributable Components.

Once per twelve-month Support Period, on request, the Licensee shall provide a written attestation signed by an authorised representative confirming the number of Named Users and confirming that, so far as the Licensee is aware having made reasonable enquiry, the Tools have been used and Component Development Work has been performed only by Named Users.

11.2 Evidence of Compliance

The Licensee may rely on its own version control records to make that enquiry. Version control records that attribute changes to the individuals who made them, and that show that changes falling within the definition of Component Development Work were made only by Named Users, are sufficient evidence of compliance with Section 2.2(b). Compliance with Section 2.2(a) is evidenced by Avalonia UI's own records of Licence Key issuance and activation, and the Licensee is not required to produce further evidence of use of the Tools.

Nothing in this Agreement requires the Licensee to give Avalonia UI access to its source code, repositories or systems.

11.3 Further Information

The attestation in Section 11.1 is the means by which Avalonia UI verifies compliance with this Schedule. Where Avalonia UI has reasonable, good-faith grounds to believe that the Licensee is materially under-licensed, it may, on not less than thirty (30) days' written notice setting out those grounds, ask the Licensee for further information reasonably necessary to confirm the number of individuals who fall within Section 2.2. The Licensee may provide that information in summary form.

Avalonia UI will not conduct on-site inspections under this Schedule. Avalonia UI shall treat any information obtained under this Section 11 as Confidential Information of the Licensee under Section 5 of the Master Terms.

11.4 Cure

Where use in excess of the licences held is identified, whether by the Licensee or by Avalonia UI, including a failure to obtain a Named User licence within the period specified in Section 2.2, the Licensee shall, within thirty (30) days of identification, obtain a Named User licence for each affected individual and pay the fees that would have been payable had each licence been obtained on the date the relevant use commenced.

A shortfall that is cured in accordance with this Section is not a Material Breach, whatever its size, and no compliance surcharge, interest or verification costs under Section 4.7 of the Master Terms are payable in respect of it, provided that:

(a) the shortfall was not deliberate; and

(b) either the Licensee reported it before receiving a request or notice from Avalonia UI under this Section 11, or it is the first shortfall identified in any period of twenty-four (24) months.

A shortfall is deliberate where the Licensee knew that a Named User licence was required and did not obtain one.

The remedies in Section 4.7 of the Master Terms apply in full to a shortfall that is deliberate, that does not meet condition (b), or that is not cured within the period above.

11.5 Relationship with the Master Terms

This Section 11 applies in place of Section 4.7 of the Master Terms to the extent that the two conflict. Avalonia UI's automated compliance monitoring described in Section 4.7 of the Master Terms is unaffected. That monitoring is limited to data Avalonia UI collects in the ordinary course of providing the Software, including Licence Key issuance, activation and telemetry records, and does not extend to the Licensee's source code, repositories or systems.

End of Schedule 11