Last week, Logical Awesome — the company that makes GitHub — announced GitHub:FI (Firewall Install). The new product is designed for those that, “wish to enjoy the benefits of GitHub, but are unable to do so because of corporate restrictions or laws that prevent you from hosting your code with a third-party service.” Essentially, GitHub:FI is a version of GitHub that can be installed on a company’s own computer inside a private network.

The GitHub:FI announcement reveals a number of interesting issues around autonomy and network services. First, the product is a symbol of recognition by GitHub of the business limitations of a purely service-based business. Not everyone will be willing or able to hand their data or computation over to a third-party. GitHub:FI exists to serve a group of people that want a level of autonomy that, while far from Franklin Street Statement style autonomy, is more than the centralized version of GitHub can provide. It marks a guarded step toward increased autonomy by a cloud poster-child.

Second, it’s interesting to see this reluctance to centralized services being described as motivated by organizations under strong institutional pressures — groups like large firms and governments. Although it certainly makes sense that these groups would be reluctant to “outsource” to centralized systems, GitHub:FI shows that these groups may provide an unlikely ally in at least part of the fight for autonomy.

Third, in Logical Awesome’s words, GitHub:FI, “is well over the cost of our most-expensive hosted plan.” In this pricing structure, the distributed option presented in GitHub:FI is framed as a form of tax on autonomy. We suspect there will be much more of this going forward. Of course, as GitHub remains proprietary software, users of GitHub:FI get only buy partial autonomy.

Finally, the product’s name is interesting. Not so long ago, we treated network services as exceptional and local software as normal. The idea of calling distributed software a “firewall install” is an explicit attempt to reframe conceptions of normal and exceptional in terms of where we expect software to reside or, perhaps, a reflection of just how entrenched services have already become.

This post was written with Dafydd Harries.