The App's current owner(s) pay, of course. For traditional "installed" Apps, this could easily be the current (and new) end-users of the App. For a purely hos

The App's current owner(s) pay, of course. For traditional "installed" Apps, this could easily be the current (and new) end-users of the App. For a purely hosted app (eg. an App that serves web clients), hosting must be arranged. If the App has no revenue model to pay for hosting, perhaps don't use it (embed it) within your app? That would be a risk. If you "fork" it, then you're responsible to host it -- if it isn't hosted by each client App installation already. The "forked" version of the App hosts its own DHT, so its data is completely distinct from the original. So, yes: there are decisions to be made, but they revolve around long-term viability of the encapsulated/forked App -- not the fundamental possibility of doing so.