End-of-Support (EOS)

What Is End-of-Support (EOS)?

End-of-support is the date after which a vendor stops providing patches, updates, and technical assistance for a product. Depending on the vendor, it may be an intermediate stage before full end-of-life, the product may still be usable and even technically running, but the organization is on its own for security patches and troubleshooting from that point forward.

Some vendors distinguish EOS from EOL explicitly and offer a paid extended support tier in between: standard support ends, but customers willing to pay a premium can continue receiving critical security patches for a further defined period. This staged approach gives organizations more runway to plan a migration without an abrupt security cliff, but it comes at a cost that increases the pressure to actually use that extra time productively rather than treating it as another deadline to defer.

For decommissioning and portfolio management purposes, EOS is tracked as its own field in a well-maintained application inventory, distinct from EOL, because the two dates can be years apart for the same product and each carries a different urgency. An application past EOS but still within an extended support window is a lower-priority risk than one that has passed EOL entirely with no support option remaining at any price.

Key Points

• Often an intermediate stage before full EOL. Some vendors offer paid extended support after standard EOS, meaning EOS and full end-of-life can be years apart for the same product.
• Still means unpatched, from that point on, absent extended support. Standard end-of-support means no more security patches under the normal support agreement, regardless of whether an extended paid tier exists.
• Tracked separately from EOL in a mature inventory. Because the two dates carry different urgency and cost implications, well-run application portfolios track EOS and EOL as distinct fields rather than treating them as interchangeable.
• Creates a cost-versus-risk decision. Paying for extended support buys time but at increasing cost, which is meant to be used to actually execute a migration or retirement plan, not simply postpone the decision again.
• A useful earlier warning signal than EOL. Since EOS frequently precedes EOL, tracking it gives decommissioning planning more lead time than waiting for the final end-of-life date to act.

Common Use Cases

📅 Tracking EOS dates in the application inventory

IT maintains EOS and EOL as separate fields for every application in its inventory, using EOS as the earlier trigger to begin planning a migration or retirement well before the final end-of-life date arrives.

💰 Evaluating extended support versus migration

Facing an approaching EOS date, an organization compares the cost of purchasing extended vendor support for another year against the cost of accelerating a planned migration, making a deliberate decision rather than defaulting to whichever requires less immediate action.

🔍 Security review flagging EOS systems

A security review identifies applications that have passed end-of-support but not yet full end-of-life, flagging them as elevated but not yet critical risk, and prioritizing remediation ahead of systems that have already passed EOL entirely.

End-of-Support (EOS) vs. Related Concepts

EOS is frequently discussed alongside, and sometimes confused with, two related terms.

END-OF-LIFE (EOL)

The point at which a product is fully discontinued, with no support available at any price. EOS often precedes EOL, sometimes by years, particularly when a vendor offers a paid extended support tier in between.

LEGACY SYSTEM

The general category that EOS and EOL status both contribute to defining. A system doesn’t need to have passed either milestone to be considered legacy, but passing EOS is a common, objective data point used in that classification.

TECHNICAL DEBT

The broader accumulated risk and cost of deferred modernization. Running past-EOS software, particularly without purchasing extended support, is one specific and easily quantified contributor to an organization’s overall technical debt.