I think it helps to think in terms of their revenue model - might help predict what features they develop too: - bitbucket wants enterprise developers to use i

I think it helps to think in terms of their revenue model - might help predict what features they develop too: - bitbucket wants enterprise developers to use it. (so it must be free for the private repos the enterprise needs). It's a gateway drug. - github wants its offering to be directly valuable to its users (which might be open-source, startup, small, medium or enterprise team). This predicts that github will be a better as a whole package (including issue tracking etc); and bitbucket will be great for git itself. But there's also much commonality: they both want to attract new users; "viral marketing" (in the sense of social projects pulling more people into the ecosystem) is helpful to both. But I think bitbucket sells itself as "free private repos* so there isn't really an overlap. I predict that bitbucket must not become a viable alternative to atlassian's paid offerings; but github isn't restricted in that way (of course, they might well add paid offerings). It seems there's also a danger for bitbucket: if users adopt their issue-tracking etc, it might be painful to upgrade; and so users might as well switch to github or other. Bitbucket should have an auto-upgrade (or, I guess their present issue tracking could evolve into a freemium model... that probably makes the most sense).