The type of work I do would change before the need for controlled local hosting will--in other words it might be that mine line of work will become obsolete or transform so dramatically that the requirement of controlled local hosting is moot. That would be nice, but I'm not holding my breath.
We use FogBugz, hosted in house (can't have our data out in the open for several reasons) and with some custom plugins to integrate with other in house systems like serial number lookup. I recently learnt that they most likely kind of cancelled that codebase too, but did not tell anybody. They just stopped to provide updates and also removed the excellent and powerful ability for plugins with the "performance update" enabled (instead they but popular plugins directly in their code):
The only info I can find on the future of FogBugz is here:
A VM is not really a solution for me for several reasons, especially if plugins are gone and our own will not work. I can only speculate, but it really looks that way. (They send newsletters to customers and announced the "performance update", but never talked about how and when this would come to "FogBugz for your Server")
I wish they were able keep the version for your server with plugins and without VM around.
On the other hand, it may not be affordable depending on the size of your shop, but that's a different matter.
We also have no plans to make an in-house solution. While the tide has not 100% turned, in most places at big companies like Amazon and Microsoft, they can already use SaaS solutions (you sign a big contract, but even if your app is on AWS, msft employees can use it). For the companies that cannot, the added complexity to development and support is likely not worth it (for us).
1) it must be sufficiently expensive. free is bad
2) i must convince everyone on my department that this is "the new way" that we operate (i.e. everyone has to use trello just like I would)
3) i must show through some pseudo science how it improves efficiency to several layers of management
Unless something is super compelling, it's not worth the effort. And if it is super compelling, it probably won't be approved anyway.
I guess I'm pretty jaded about the whole thing. If there is a neat tool, or some productivity enhancement/stress reducer, I usually just find a way to use it myself under the radar and don't share it with anyone (which offends me greatly as it's a terrible waste).
I'd actually have to go through that process for emacs 24, though in that case it's getting past the IT gatekeepers and proving to them that emacs 24 won't bring down the cluster. So I find a way to compile and run it and just don't talk about it a lot.
But anything web appish is out of the question. I settle for org-mode in emacs, but it'd be nice to collaborate. Sadly with our process of onboarding something, there's no room for experimentation or feeling something out or developing a workflow that would be worth demonstrating.
I used to work at a client site where they wanted us to list all of the tools we used (as software developers) because they didn't want us to use these "computers" that we were using, in their offices on their network, and instead they wanted us to all code using citrix dumb terminals.
I no longer work at that client site, or for the company that sent me there.