Unlike NYCGA.net, which was a utility for Occupy Wall Street in New York managed by a NYC based group of techies, Occupy.net is a set of tools, each of which is maintained by a different team, many of whom aren’t located in the New York area. In some ways it’s the software equivalent to the GVCS: all of the FLO software tools our community needs to build a robust social movement. The intention behind the toolkit is to do more than simply provide the Occupy movement with useful tools; it’s to provide an FLO alternative to the world’s largest web application provider – Google. That isn’t as crazy as it might sound: there is an FLO alternative for nearly every Google application, but no one has tied all these FLO alternatives together with a unified design language, single user sign-on, comprehensive documentation and community support network to create something that feels competitive. Our ability to frame Occupy.net as an alternative to corporate software is what attracts activist technologists to maintain services under the Occupy.net name. Unfortunately, it doesn’t seem to attract the attention of the mainstream media, who are looking for stories about social media flash mobs organized on corporate social networks like Facebook and Twitter, not how a bunch of technologists are designing, deploying and maintaining enterprise grade FLO software solutions that will be able to enhance the movement’s growth over the long term and chart how to create software infrastructure for the new, emergent, FLO economy.