hadn't thought about that but it might be an option.
The current setup is to have the discourse install running on a separate Digital Ocean droplet - that keeps it separate and clean. Installed using the official beta discourse (v1.4) github repo.
Not sure forking the code down to a second github would be of much use as the discourse devs are happy to look at pull requests and fixes directly into their codebase. It's happened a few times looking at their site and my work on the kunena importer should be included in a new build soon.
I am keeping the costs down, ACC not being a paid service needs to be costs minimal, but i don't want to skimp on the features. Digital ocean are a very keenly priced solution with ease of use as well, and we get a full dedicated server instance not just an app.
Dev input for the site is always greatly appreciated, no one is an expert in everything so having input from many people is always great.