Perhaps I'm not up to date on Atlassian's hosting options, but every company I've ever worked at which uses Atlassian (including my current) hosts the servers themselves, I believe. You pay for the software/licenses/updates, and Atlassian simply hands over a pile of Java jars and documentation. It is up to your ops staff to choose a server, fire it up on there, back it up, update it, etc. This would be the same as running your own Trac, right?
postingposts|3 years ago
Some do run it onsite which is similar to running Trac but with two major differences: 1. Contributing bugs to Atlassian helps only Atlassian. 2. You have to pay Atlassian.
The counter argument is that a company of Atlassian or even further scaled, at Google’s size, should be able to provide some meaningful customer support or engineering around bugs or issues while using the platform.
But in reality, Atlassian’s cloud outage is over 2 weeks, could have likely been resolved if everything was handled properly on-site (for those who like to play Devil’s advocate, there’s your hinge) as opposed to going to the cloud.
What I’m arguing for is the idea it’s beneficial to everyone to support platforms which enable the user to DIY, and we consider engineers or admins people who do that: Engineer and admin.
In other words: the car industry doesn’t compete over the shape of the wheel, why do we?