That is not at all the conclusion the author draws from this experience of his. Here's more of the paragraph, you quoted: >Earthly being open-source, you could

That is not at all the conclusion the author draws from this experience of his. Here's more of the paragraph, you quoted: >Earthly being open-source, you could already run your own Earthly remote runner (since we use Buildkit underneath, it was essentially a remote Buildkit), connect Earthly to it, and get similar benefits to Satellites even before this was a commercial offering. And so people did this on their own, hosting it in their own environment, without us managing it for them. Once we had this packaged up in a managed offering, people were flocking to it, mainly because they did not want to manage remote runners on their own. The author blames the failure on not validating what the were building was what clients wanted.