diff --git a/README.md b/README.md
index 8a6ae3ce5..f31238f2d 100644
--- a/README.md
+++ b/README.md
@@ -243,6 +243,10 @@ If an Observer fails to meet these expectations they can be excluded from future
 
 * [Community / Travel Fund](./community-fund/COMMUNITY_FUND_POLICY.md) - OpenJS Foundation projects and their community members are able to take advantage of our community fund.
 
+#### OpenJS Ecosystem Sustainability Program 
+
+* [OpenJS Ecosystem Sustainability Program](./project-resources/ESP/ECOSYSTEM_SUSTAINABILITY_PROGRAM.md) - The Ecosystem Sustainability Program is an opt-in OpenJS partner program to help secure outdated software and create new revenue streams for our projects.
+
 ### Policy Change Proposal Process
 
 The OpenJS CPC is chartered to oversee the technical governance of all OpenJS Projects, Collaboration spaces and Working Groups under the OpenJS Foundation. The CPC establishes the default governance, conduct, and licensing policies for all Projects and Collaboration spaces. Projects have broad powers of self-governance.
diff --git a/project-resources/ESP/ECOSYSTEM_SUSTAINABILITY_PROGRAM.md b/project-resources/ESP/ECOSYSTEM_SUSTAINABILITY_PROGRAM.md
new file mode 100644
index 000000000..a64bddc81
--- /dev/null
+++ b/project-resources/ESP/ECOSYSTEM_SUSTAINABILITY_PROGRAM.md
@@ -0,0 +1,77 @@
+# OpenJS Ecosystem Sustainability Program 
+
+## Summary 
+
+The Ecosystem Sustainability Program (ESP) is an opt-in OpenJS partner program to help secure outdated software and create new revenue streams for our projects. Working in partnership with the Foundation and participating projects, ESP partners provide a revenue share based on sales generated through co-marketing efforts. 
+
+## Benefits
+
+Eligible projects that opt into the program receive revenue that can be used to:
+
+- Grow their community
+- Pay contractors
+- Support travel
+- Cover other project-related expenses
+
+## Current Partners
+
+- [HeroDevs](https://www.herodevs.com/)
+
+## Eligibility
+
+For a project to participate in the program:
+
+- A partner must be providing support to end-of-life (EOL) versions of the project
+- The project must be willing to place links to the partner on various pages/repositories where EOL versions are mentioned 
+- The project must be willing to manage funds via [Open Collective](https://opencollective.com/).
+
+## How To Participate
+
+Projects that are interested in participating in the program should contact operations@openjsf.org.
+
+## How To Enroll In Open Collective
+
+Because funds are distributed to the project and in most cases not an individual, we suggest creating an *[Open Collective](https://docs.opencollective.com/help/collectives/create-collective)* account and project collective. 
+
+In most cases, projects do not have bank accounts and must [sign up](https://opencollective.com/opensource/apply) with Open Source Collective to be a fiscal host. This means Open Collective will hold the funds on your behalf, handle taxes, and enable you to pay vendors and contractors. 
+
+### Important Information About Payments
+
+- Payments are made to projects every 6 months
+- Project payments are excluded from the Linux Foundation General & Administrative (G&A) fee
+- Open Collective charges a 10% fee on incoming funds if it is used as a fiscal host. The Open Collective [Docs](https://docs.oscollective.org/how-it-works/fees) provide detailed information on fees.
+
+
+## General Guidelines
+
+### Version Support Page
+
+The project readme and website should clearly indicate which versions of the project are supported and which are not. Here’s [a great example from the Node.js website](https://nodejs.org/en/about/previous-releases#release-schedule):
+
+![Node Release Schedule](esp-herodevs-node.png)
+
+### Referral Link Placement & Best Practices
+
+The goal of prominently placing referral links is to maximize the likelihood that a user who is stuck on an unsupported version will learn of the existence of alternatives. This might mean that, prior to an EOL milestone or a major version release, one would temporarily have a prominent banner or link.
+
+- Projects should have a prominent Version Support Page
+- Referral links to partners must be placed within the top ⅓ of the page
+- The Version Support Page must link to partner pages for the versions our partners support
+- When documenting which versions are no longer receiving patches, consider adding a link with copy: “read more about extended support options” that directs to an EOL page.
+- Project-specific referral links will be provided as part of the onboarding process.
+
+### Referral Link Page Examples
+
+![Vue Referral Page Example](esp-herodevs-vue.png)
+
+![Angular Referral Page Example](esp-herodevs-angular.png)
+
+### End-Of-Life Events
+
+In the 3 to 12 months before a version goes EOL, it would be ideal to add a prominent banner on the entire project's homepage indicating that the version is going EOL, the date upon which it will go EOL, and a link to the Version Support Page.
+
+## Partner Specific Guidelines
+
+### HeroDevs
+
+HeroDevs has offered to directly assist projects by providing specific recommendations and, upon request, utilizing their resources and staff for design and PR filing.
diff --git a/project-resources/ESP/esp-herodevs-angular.png b/project-resources/ESP/esp-herodevs-angular.png
new file mode 100644
index 000000000..c1e4f2d6b
Binary files /dev/null and b/project-resources/ESP/esp-herodevs-angular.png differ
diff --git a/project-resources/ESP/esp-herodevs-node.png b/project-resources/ESP/esp-herodevs-node.png
new file mode 100644
index 000000000..4eccd83ae
Binary files /dev/null and b/project-resources/ESP/esp-herodevs-node.png differ
diff --git a/project-resources/ESP/esp-herodevs-vue.png b/project-resources/ESP/esp-herodevs-vue.png
new file mode 100644
index 000000000..060b48e05
Binary files /dev/null and b/project-resources/ESP/esp-herodevs-vue.png differ