I would echo shared hosting to reduce cost.
Also, I wanted to share my perspective on why the open source concept you were striving for didn't go as you expected. In my view, there are tiers of software coding that require different levels of documentation. This ranges from very low for personal projects to moderate for small businesses to high for large businesses and open source. The high level of documentation is because all developers are not co-located and so common coding philosophy documents and code comments are the only thing to ensure all developers have the same understanding.
I looked into the github and had a difficult time understanding the software architecture since there wasn't a document that described it. Further, the various functions are not commented at minimum with their objective, inputs and outputs. Having to reverse engineer this is one of dante's seven levels of hell in my perspective.
If you really want to foster a strong open source community to support and further develop the code, I would advise to write a document that describes the software architecture and general philosophies followed along with commenting each function with objective and input and output descriptions in the header and perhaps also commenting any local variables as well.
I would be happy to start development of a local server solution (though this will not be a small undertaking since most will not have the same infrastructure that exists in the hosted server environment), but to begin, I would need the above - I'm sure there are others with a coding background that would also support provided there was a development list of tasks that could be assigned.