> For the complete documentation index, see [llms.txt](https://resources.yamaindustrials.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.yamaindustrials.com/end-of-life-eol-policy.md).
# End-of-Life (EOL) Policy
This End-of-Life (EOL) Policy ("Policy") is published by Yama Industrials, Inc. ("Yama") at resources.yamaindustrials.com. This Policy is incorporated by reference into the Main Service Agreement ("MSA" or "Agreement") between Yama and Customer pursuant to MSA Section 1.2, and governs Yama's standards for supporting, recommending, configuring, and maintaining certain categories of network hardware in connection with the Services.
Customer is responsible for reviewing the then-current MSA and incorporated Yama policies as provided in the MSA. A reference to, or link to, Yama's designated terms or resources domain in an invoice, estimate, proposal, ticket, renewal, or other Customer-facing documentation provides notice in accordance with MSA Section 1.3 and may identify this Policy as an incorporated policy under MSA Section 1.2. This Policy applies to Customer accounts and hardware deployments only to the extent, and at the time, permitted by the MSA, including MSA Sections 1.4 and 20.2, and any applicable signed Order Form or SOW.
***
#### Defined Term
"EOL-Classified" means hardware that Yama has designated under this Policy as ineligible for one or more specified activities, including recommendation, sale, configuration, deployment, or managed-support offerings. An EOL classification is an internal Yama support determination only. It does not, by itself, represent, adopt, or correspond to any manufacturer's end-of-sale, end-of-support, end-of-life, security, warranty, or regulatory-compliance designation. A product may be EOL-Classified under this Policy while still receiving active support from its original manufacturer, and vice versa.
#### Overview
Yama maintains this Policy to identify hardware categories that Yama has determined, in its reasonable operational judgment, present a risk profile Yama has determined is incompatible with its then-current support standards for compliance-sensitive deployments, or that Yama has otherwise determined are no longer suitable for new sale, configuration, or managed-support commitment due to manufacturer end-of-life status or insufficient on-device storage or compute resources. This Policy is maintained on an ongoing basis, and Yama reserves the right to add, remove, or reclassify hardware categories in accordance with the Notice and Amendment provisions below.
This Policy currently addresses two hardware categories:
1. Ubiquiti UniFi Network Gateway Hardware
2. Arista Edge Threat Management (Untangle) Appliance Hardware
***
#### Part 1: Ubiquiti UniFi Network Gateway Hardware
**1.1 Scope**
This Part applies to all Customer Equipment and Yama Equipment consisting of Ubiquiti UniFi Cloud Gateway devices, Dream Machine devices, and related gateway hardware, whether procured through Yama, brokered by Yama under MSA Article 21 (Brokered and Resold Third-Party Services), or independently owned by Customer.
**1.2 Rationale**
Yama has determined that:
* The frequency and severity of cybersecurity threats affecting network perimeter devices has materially increased year over year, including ransomware, zero-day exploitation, and regulatory scrutiny under frameworks such as CJIS, HIPAA, and comparable state and municipal compliance regimes.
* Adequate on-device log retention (flow logs, IDS/IPS events, and audit trails) is a baseline requirement for Customer's ability to detect, investigate, and respond to security incidents, and to satisfy Customer's own regulatory or contractual compliance obligations.
* Certain Ubiquiti hardware tiers lack expandable on-device storage sufficient to support durable log retention, relying instead on fixed onboard flash memory and system RAM, which materially limits retention windows.
* This approach is consistent with prevailing industry practice, including manufacturer-driven end-of-support decisions for legacy consumer and prosumer hardware based on evolving security and technology standards.
**1.3 Hardware Classification**
| Tier | Representative Models | Storage Configuration | Classification |
| ------------- | ----------------------------------------------------------------------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Below Ultra | USG, UDR, legacy Dream Machine (non-Pro), UniFi Express | Fixed onboard flash (4–16 GB), no expansion | EOL-Classified — Not Recommended for Compliance-Sensitive Deployments |
| Ultra | UniFi Cloud Gateway Ultra, Cloud Gateway Fiber (base) | 16 GB fixed eMMC, 3 GB RAM, no expansion bay | EOL-Classified — Not Recommended for Compliance-Sensitive Deployments |
| Max and Above | Cloud Gateway Max, Cloud Gateway Fiber (SSD-equipped), UDM Pro, UDM SE, UDM Pro Max | Selectable NVMe SSD (0–2 TB) or HDD bay | Eligible for Consideration for Yama's Compliance-Oriented Support Offerings, Subject to Storage Being Populated and Section 1.4 Below |
\
Max-tier and above devices configured with the "No Storage" option are functionally equivalent to Ultra-tier devices for log retention purposes and are EOL-Classified under this Policy until storage is installed.
**1.4 Effect of Classification**
* Yama will not recommend, sell, configure, or renew compliance-tier support commitments for EOL-Classified hardware identified in Section 1.3, effective as of the Effective Date of this Policy, applicable to all Customer accounts and hardware deployments to the extent and at the time permitted by MSA Sections 1.4 and 20.2, regardless of when the hardware was originally deployed or when the account was established.
* Yama may, in its sole discretion, continue to provide Ad-Hoc Services with respect to EOL-Classified hardware on a time-and-materials basis, subject to MSA Article 4 and MSA Section 3.6.
* A designation of hardware as "Eligible for Consideration" under Section 1.3 reflects Yama's then-current operational assessment only. It is not a warranty, certification, legal opinion, or representation that any hardware, configuration, Customer environment, or Service satisfies CJIS, HIPAA, or any other legal, regulatory, contractual, insurance, or cybersecurity requirement.
* Nothing in this Part limits or expands Yama's right to modify, suspend, or discontinue any Service or Product, in accordance with the MSA, including MSA Sections 1.6, 3.6, 5.5, and 8.12, and MSA Article 12.
***
#### Part 2: Arista Edge Threat Management (Untangle) Appliance Hardware
**2.1 Scope**
This Part applies to all Customer Equipment and Yama Equipment consisting of legacy Untangle-branded Q-Series appliances (Q4, Q8, Q8W, Q12, Q20) and successor Arista Edge Threat Management ("ETM") appliance hardware, whether procured through Yama, brokered by Yama under MSA Article 21, or independently owned by Customer.
**2.2 Rationale**
Yama has determined that:
* Arista Networks, Inc. ("Arista"), the current owner of the Untangle NG Firewall product line, publicly announced end-of-sale of the ETM NG Firewall Q4, Q8, Q8W, Q12, and Q20 appliances on March 10, 2026, with the last day to order the affected products being June 30, 2026 (subject to availability). Per Arista's published End-of-Life Milestones, the last date for hardware RMA requests and the manufacturer end-of-life date for these devices are both June 30, 2029.
* Arista's published migration guidance designates the following Arista VeloCloud Edge OS appliances as the corresponding replacement products: the 710 Series for the Q4, the 720 Series for the Q8 and Q8W, the 740 Series for the Q12, and the 4100 Series for the Q20.
* Arista's published migration guidance also identifies a software or virtual appliance edition of ETM NG Firewall as an alternative migration path for affected customers.
* Where Customer elects a software-only NG Firewall deployment, the underlying bare-metal or virtualization host may be sourced either (a) by Customer, from any reputable, commercially supported third-party hardware vendor, or (b) by Yama, under an active Yama support subscription, as further described in Section 2.4 below.
* Continued reliance on hardware beyond its manufacturer-supported RMA and end-of-life dates presents a risk profile Yama has determined is incompatible with its then-current support standards for compliance-sensitive deployments.
**2.3 Hardware Classification**
| Category | Hardware/Product | Manufacturer Status | Classification |
| -------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Legacy Untangle Q-Series | Q4, Q8, Q8W, Q12, Q20 | End-of-sale announced March 10, 2026; last order June 30, 2026; hardware RMA and manufacturer end-of-life both June 30, 2029 | EOL-Classified — Migration Required for Continued Eligibility for Compliance-Tier Support |
| NG Firewall Software Edition (VM) | Software-only / virtual appliance deployment | Actively sold by Arista | Eligible for Consideration — Bare-Metal/Hypervisor Sourced per Section 2.4 |
| Arista VeloCloud Edge Hardware | 710 (replaces Q4) / 720 (replaces Q8, Q8W) / 740 (replaces Q12) / 4100 (replaces Q20) | Actively sold by Arista; manufacturer-designated replacement line for the Q-Series | Eligible for Consideration for Yama's Offerings — Arista-Designated, Manufacturer-Recommended Migration Path, Subject to Customer Requirements, Licensing, Compatibility, and a Signed Order Form or Statement of Work |
| Third-Party General-Purpose Server Hardware (Customer-Sourced) | Dell (e.g., PowerEdge), HP/HPE (e.g., ProLiant), or equivalent enterprise-grade server hardware | Actively sold and supported by respective OEM | Eligible for Consideration — Approved Customer-Sourced Bare-Metal/Hypervisor Host, Subject to Section 2.4 |
| Third-Party Dedicated Appliance Hardware (Customer-Sourced) | LogicSupply, Protectli, or other comparable reputable network-appliance hardware manufacturer | Actively sold and supported by respective OEM | Eligible for Consideration — Approved Customer-Sourced Bare-Metal Host, Subject to Section 2.4 |
| Yama-Selected Hardware (Under Active Support Subscription) | Any hardware selected, specified, procured, or supplied by Yama at its discretion for the specific Customer engagement | Determined by Yama on a per-engagement basis | Eligible for Consideration — Governed by Applicable Order Form/SOW, Subject to Section 2.4 |
\
Approval of any third-party hardware vendor not expressly listed above (including future additions to this Policy) is subject to Yama's sole discretion and will be evaluated against the same minimum specification and support-availability criteria applied to the vendors listed herein.
**2.4 Effect of Classification and Hardware Sourcing**
* Yama will not recommend, sell, configure, or renew compliance-tier or managed support commitments for legacy Untangle Q-Series hardware identified in Section 2.3, effective as of the Effective Date of this Policy, applicable to all Customer accounts and hardware deployments to the extent and at the time permitted by MSA Sections 1.4 and 20.2, regardless of when the hardware was originally deployed or when the account was established.
* Yama may, in its sole discretion, continue to provide Ad-Hoc Services with respect to EOL-Classified Untangle hardware on a time-and-materials basis, subject to availability of manufacturer support, MSA Article 4, and MSA Section 3.6.
* Customer-Sourced Hardware. Where Customer elects a software-only/virtual NG Firewall deployment on Customer-selected third-party bare-metal hardware, Customer is solely responsible for procuring, sizing, securing, patching, and maintaining the underlying hardware and hypervisor infrastructure, including all manufacturer warranty and support arrangements with the applicable third-party vendor, except to the extent expressly and separately assumed by Yama in a signed Order Form or Statement of Work. This allocation is consistent with MSA Section 11 and MSA Article 21, as applicable.
* Yama-Selected Hardware. Where Customer maintains an active Yama support subscription, Yama may, in its sole discretion and as part of the scoped engagement, select, specify, procure, and/or supply the bare-metal or appliance hardware on Customer's behalf, documented in the applicable Order Form or Statement of Work. The scope of Yama's responsibility for sizing, configuration, warranty coordination, and ongoing maintenance of such hardware shall not exceed what is expressly set forth in that Order Form or SOW, and remains governed by MSA Article 14 and MSA Article 21.
* No Compliance Determination. A designation of hardware as "Eligible for Consideration," "Supported," or similar under Section 2.3, whether Customer-sourced, Yama-selected, or manufacturer-designated, reflects Yama's then-current operational assessment of general compatibility and industry reputation, or Yama's own procurement determination, only. It is not a warranty, certification, legal opinion, or representation that any hardware, configuration, Customer environment, or Service satisfies CJIS, HIPAA, or any other legal, regulatory, contractual, insurance, or cybersecurity requirement.
* Ownership and Equipment Status. Hardware selected, procured, furnished, deployed, leased, rented, or otherwise supplied by Yama shall constitute Yama Equipment unless expressly identified as sold to Customer in a signed Order Form. All Yama Equipment remains subject to MSA Article 7, including the applicable access, return, recovery, replacement-value, and continuing-charge provisions. No reference in this Policy to Yama-selected or Yama-supplied hardware conveys title, ownership, or rights beyond those expressly stated in the applicable signed Order Form.
* Nothing in this Part limits or expands Yama's right to modify, suspend, or discontinue any Service or Product, in accordance with the MSA, including MSA Sections 1.6, 3.6, 5.5, and 8.12, and MSA Article 12.
***
#### 3. General Provisions (Applicable to Both Parts)
**3.1 No Duty to Monitor Customer Hardware**
Nothing in this Policy expands Yama's obligations beyond those set forth in MSA Section 11. Yama has no duty to monitor, audit, or inventory Customer's deployed hardware for EOL-Classified status absent an express, separately scoped engagement to do so. Customer remains responsible for the security, configuration, and compliance of its own environment, except to the limited extent Yama expressly assumes a specific responsibility in a signed Order Form or Statement of Work.
**3.2 Effect on Ad-Hoc and Suspended Accounts**
This Policy applies equally to Customers under active subscription-based Services and Customers under Ad-Hoc Support Status or suspension pursuant to MSA Sections 3.5, 3.6, and 8.12, and to hardware deployed before, on, or after the Effective Date of this Policy, subject in all respects to MSA Section 20.2. Publication of this Policy at resources.yamaindustrials.com constitutes sufficient notice to all Customers regardless of account status. Yama may, as a courtesy and in its sole discretion, provide additional direct notice to Customers with active subscription-based Services; such courtesy notice does not create an ongoing obligation to provide further notice and does not expand the scope of any Services.
**3.3 Reinstatement of Suspended or Ad-Hoc Accounts**
Where a Customer account is suspended or held in Ad-Hoc Support Status and seeks reinstatement of subscription-based Services, Yama may, as a condition of reinstatement, require a hardware compliance review against this Policy and may condition continued or renewed support on either (a) Customer's migration away from EOL-Classified hardware, or (b) a written acknowledgment, in a form approved by Yama and executed by Customer's authorized representative, of the EOL-Classified status, the associated limitations and risks (known and unknown), and any resulting limitations on Yama's support obligations.
**3.4 No Warranty; Reliance Limits**
This Policy is a statement of Yama's internal support standards. Except as expressly stated in a signed Order Form or Statement of Work, Customer shall not construe this Policy, including any hardware classification, recommendation, or designation contained herein, as a representation, warranty, certification, or guarantee of regulatory compliance, security, fitness for a particular purpose, or uninterrupted availability.
**3.5 Errors, Omissions, and Corrections**
This Policy is intended to reflect Yama's good-faith operational standards and publicly available third-party manufacturer information as of the date of publication or most recent revision. Any factual error, omission, outdated citation, typographical error, or inaccurate third-party reference contained in this Policy (including any manufacturer date, model designation, or specification) shall be construed, to the maximum extent possible, in a manner consistent with the express text of this Policy, the defined terms set forth herein, and the order of precedence established by MSA Section 1.4, and shall not, by itself, render any classification, condition, or requirement of this Policy void, unenforceable, or a basis for a claim of detrimental reliance against Yama. Yama may correct any clerical, typographical, formatting, or objectively verifiable factual error by publishing a revised version of this Policy at any time. Any such non-substantive correction shall relate back solely to clarify the original text and shall not be construed as a substantive amendment. Any substantive change to a classification, condition, requirement, or Customer obligation shall be governed by Section 4 and MSA Section 20.2.
**3.6 No Waiver; Severability**
No failure or delay by Yama in enforcing any provision of this Policy shall constitute a waiver of that provision or of Yama's right to enforce it at a later time. If any provision of this Policy is held invalid, illegal, or unenforceable in any respect, such provision shall be enforced to the maximum extent permitted, and the remaining provisions shall remain in full force and effect, construed so as to give maximum effect to the express text of this Policy and the remaining provisions hereof.
**3.7 Order of Precedence**
This Policy is an incorporated Yama policy for purposes of MSA Section 1.2. In the event of any conflict among the documents comprising the Agreement, including this Policy, the order of precedence set forth in MSA Section 1.4 shall govern. For the avoidance of doubt, neither an Order Form nor a Statement of Work supersedes this Policy or the MSA unless such document is later in time and expressly overrides the specific conflicting provision in a writing signed by an authorized officer of Yama.
***
#### 4. Notice; Amendments
Publication of this Policy at resources.yamaindustrials.com, together with a reference to or link to Yama's designated terms or resources domain in Customer-facing documentation, provides notice in accordance with MSA Section 1.3 and identifies this Policy as an incorporated Yama policy under MSA Section 1.2. Yama may amend, expand, revise, add to, remove from, or reclassify hardware categories or approved third-party vendors under this Policy at any time by publishing a revised version at resources.yamaindustrials.com, with a revised "Last Updated" date and, where applicable, a distinct Effective Date. Any amendment to this Policy shall be effective and applied in accordance with MSA Section 20.2. Unless otherwise expressly permitted by the MSA or an applicable signed Order Form, a revised Policy applies prospectively to new Orders, renewals, reinstatements, Ad-Hoc Services, and Services commencing after expiration or termination of a prior committed term, and shall not alter a non-waivable commitment expressly stated in a signed Order Form during its then-current committed term. A changelog of material revisions, including the effective date and scope of each version, is maintained below.
**Changelog**
| Version Date | Effective Date | Change | Application |
| ------------- | -------------- | ------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| July 29, 2026 | July 29, 2026 | Initial publication of EOL Policy, Parts 1 (Ubiquiti) and 2 (Arista/Untangle). | Customer accounts and hardware deployments, existing and future, to the extent and at the time permitted by the MSA, including MSA Sections 1.4 and 20.2. |
\
***
*This Policy is a Yama-published policy incorporated by reference into the Main Service Agreement pursuant to MSA Section 1.2. In the event of any conflict between this Policy and the Main Service Agreement, the order of precedence set forth in MSA Section 1.4 controls.*
\
\