Product lifecycle policy

This article applies to all products.png


CrashPlan strives to continually innovate and evolve its solutions, providing customers with richer functionality and more robust products. As part of this ongoing evolution, certain CrashPlan products will reach the end of their lives. Our goal is to provide straightforward product lifecycle policies that help customers better design, deploy, and manage their IT investments and upgrades.

This article outlines CrashPlan's lifecycle policy for its products

Product lifecycle policy

A CrashPlan product is:

Any good or service produced or provided by CrashPlan.

The following policy items apply to all CrashPlan products, including both software and hardware:

  1. CrashPlan may choose to announce the end-of-sale and end-of-support dates for its products at any time.
  2. CrashPlan works with its customers to ensure continuity of business when announcing the end-of-sale or end-of-support dates for its products.
  3. Notifications and reminders to customers for end-of-support begin approximately 6 months prior to the end-of-support date.



end-of-sale date

The date when a product is no longer available for purchase from CrashPlan or its authorized resellers.


Access to maintenance, remote monitoring and the CrashPlan technical support team is no longer available. Patches and bug fixes are no longer available to products that have reached end-of-support.

major software version

A significant software version that is defined as x.0. Example: 10.0.


Once obsolete, the product is not sold, improved, repaired, maintained or supported.


Any good or service produced or provided by CrashPlan.

product lifecycle

The processes surrounding the introduction, growth and maturity of a product. The product lifecycle includes a series of technical and business milestones and activities that, once completed, make a product obsolete. 

software versions

CrashPlan uses four designations for software versions:

  • Major software versions contain large features and changes to functionality. Major version numbers are one decimal place that is always zero, such as 8.0 or 10.0.
  • Minor software versions contain smaller features and enhancements to existing functionality. Minor version numbers are one decimal place, such as 8.8 or 10.2.
  • Maintenance software versions contain bug fixes and other small changes. Maintenance version numbers are two decimal places, such as 8.8.1 or 10.2.1
  • Patch software versions contain bug fixes or other corrections that must be addressed before the next scheduled release point. Patch version numbers are 3 decimal places, such as or


Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more