The “infrastructure” is just a single dedicated server. Ok, at the moment there are two of them, because we are migrating from an old one which was showing its limits, to a new one with more RAM (and also cleaning up the setup, making it a lot easier to redeploy the whole thing if needed). As a result the costs are temporarily increased.
According to the inc website, this is about $900 a year (I think this is for a single server?). We are past $5000 in donations this year, which means keeping the dedicated server online is not really a problem.
There has not been any financial reports for some time, but the largest expenses are actually paying developers who work full time on Haiku (no one currently), and funding coding sprints and other events (the biggest expense in 2017 with something close to $3000, IIRC, funding rooms and meals for 8 devs hacking on Haiku for a week in a distraction-free environment).
The server hosts:
- Website, forums
- Buildbot (master + some virtualized slaves - the remaining slaves are Mac Minis donated to Haiku by Mozilla and gracefully hosted by various project members)
- Buildmaster for HaikuPorts packages
- Storage space for nightlies and packages repositories (a lot of space, since we keep old versions to allow people to downgrade for testing)
- Pootle, for translating Haiku to various languages, and another tool for translating the userguide,
- irker, the bot providing commit notifications on IRC
Some tools in this set are not that usual or downright custom. So it is unlikely we can find someone hosting them as SaaS. We also had rather unpleasant experiences with outsourcing critical services (people who have been in the project long enough remember Berlios not allowing SVN commits because their disk was full, every other week end or so). It takes a lot of time to set up a proper workflow with the plumbing between all these tools, and it is quite annoying to do it on an SaaS infrastructure where we are at the mercy of an update (API deprecation, etc) - this is happening to Haikuports, where the hooks we use to trigger mailing list notifications from github commits will not be working anymore by the end of the year.
The needs are sufficiently complex that the dedicated server is worth it, and it is not even the place where most of our money is spent. I hope the inc can publish the financial reports so everyone can have a look and see this more clearly.