Hacker News Reader

What structural guarantees have you embedded in your corporate structure to ensure that data won't be rendered inaccessible if you have to shut the system down due to acquisition or lack of funding?

View on HN

Well the reason we're actually charging for Larder rather than pursuing some kind of "growth" strategy is to do our best to avoid going out of business due to lack of funding. We're building a lifestyle business rather than a startup, to be honest, and it's highly unlikely we'll ever get acquired either. We just want to make a living building things and selling them (unusual, I know). So while I can't make any guarantees, what's most likely is that if Larder ever does shut down or go away, it'll be through a decision we make personally, and so we'll provide plenty of time to export your data (which is already possible from the account page, whenever you'd like it) before taking it offline.

How would you like such a guarantee implemented? Maybe something involving a third party?

Do some form of local caching and p2p distribution.

I don't see this kind of software needing to be managed by a third party. This is easily something doable with a p2p protocol.

Reply on news.ycombinator.com