4 ms·
Put the code / schematics into escrow, and require that the company or its successors must release the contents of the escrow in the event that the service ceas
by midnitewarrior 3y ago
Put the code / schematics into escrow, and require that the company or its successors must release the contents of the escrow in the event that the service ceases to be commercially viable. If another company wants to take over the assets and operate the service, they can, but they are obligated to release the contents of the escrow in the event they cease to operate the service.
- lobsterthief 3y agoHonestly, escrow is usually just one small part of the puzzle compared to the many SaaS/hosting services chained together to make the thing work. I’m sure most iOT startups that fail are no different.
- ghaff 3y agoIn general, throwing some code over the wall for some commercially unsuccessful (or just something small time the creator got tired of) project is pretty much useless 99.99%+ of the time. As you say, for starters, it's probably only a piece of a fully-documented product.