What if the vendor goes out of business — how do I mitigate?

Vendor failure is the single biggest risk in extension purchasing. Mitigation comes from doing the right due diligence up-front + having an exit plan baked in.

Before you buy:

• Check vendor longevity. 5+ years of Magento history is a soft floor. Vendors that started in M1 and survived the M1→M2 migration are battle-tested.
• Check commit cadence. The vendor’s public GitHub or Bitbucket repo — if commits are flowing in the past 12 months, they’re still in business. Stale repos = walk away.
• Check support response speed. Send a hard pre-purchase question. Time the response. >48 hours = warning sign.
• Check community sentiment. Magento Stack Exchange + Magento Community Forum for the vendor name + bug terms.

Mitigation in your contract:

• Source code escrow. Some vendors offer source-code release if the company dissolves. Worth asking, especially for $1k+ licenses.
• Prefer marketplace-listed modules. Adobe holds vendors to a contract that includes minimum support obligations.

If the worst happens:

• Fork it. If you have access to the source, freeze it at the last working version and have your dev maintain it (security patches + Magento compat) until you can replace it.
• Plan replacement on your next major project. Don’t do an emergency rip-out unless it’s broken — bake the replacement into the next refresh.