GitHub to Seek $2B Valuation in Latest Funding Round
bloomberg.com
bloomberg.com
It is not proof however that being full on open source in everything you do is profitable however I wished that to be the case.
What does this have to do with leveraging open source software?
The awesomeness of Github is that it is created by developers, for developers. John Carmack, once estimated that Stack Overflow may have saved billions of dollars in productivity[1]. Hard to estimate but seeing the sheer accelaration in Open Source world, after Github, I am sure, a similar estimate would be much higher for Github.
[1]: https://twitter.com/ID_AA_Carmack/status/380018564792455168
2B/21 Million Repos = $95 per repo
obviously they're not pulling in that kinda cash, but I'd love to see enterprise pricing.
I find it laughable that in 2015 people are still claiming companies strategically delaying monetization have worthless businesses. They care about long term growth, not money in the hand. See Facebook and Twitter. And a bunch of other companies.
Whatsapp seems to have less revenue potential than products which have already shown an inability to find the black, such as AIM.
Edit: gonna try it
My city has 500,000 people. I'm going to estimate there are 500 liquor stores here. So that's 1 per 1,000 people. The USA has 330 million people, thus 330,000 liquor stores.
A liquor store is probably worth about $50,000. Thus, they are all worth $16.5 billion.
Whatsapp has 800 million MAU's. If 2% of them convert to $10 a month paying customers, that is $160 million per month.
They could run that business much cheaper than the current one, so say 50 employees at $10k a month each. $500k a month. Double that for hosting and rent etc. $1 million a month.
Those costs seem way too low in relation to revenue so let's just bump that up to 50% of revenue. $80 million/month.
So $80 million per month profit. Or over 2 liquor stores per hour, 24/7/365. In about 15 years they'd own every liquor store in America.
Github seems to be mostly personal and open source projects. With good reason since it's trival to set up a git server yourself and so you'd only want to put up stuff that you want public-facing. But it's not so trivial to set up the web ui in git server and so I could see some value there (not sure if $2B of value though)
I used github at a company but only for some code that we wanted to share outside of our company. And if we had to pay for it we never would have used github since we could have spent a 1/2 day setting up a public-facing git server.
We would never have used it for our internal code - again, it's trivial to maintain your own git server and it would also be irresponsible of us to put our internal code on a public-facing server.
So... what makes them valued at 2B? Do they have any revenue at all? Maybe they can hook up with linkedin?
GitHub Enterprise[1].
> And if we had to pay for it we never would have.
I think you're the exception.
[1] And private repos, but I'd imagine that 80%+ of their revenue comes from on-premise enterprise deployments.
The risk/reward payoff is different for every company, and there are many who will outsource the hosting of much of their IP because the alternative is often a hindrance to companies who want to ship their core product.
https://about.gitlab.com/images/feature_page/webhooks_full.p...
But still all three GitLab, Stash and GitHub have horrible permission capabilities. Looks like GitLab might be the "best" with what they have http://doc.gitlab.com/ee/permissions/permissions.html, but that is still pretty poor. A simple example would be the requirement to only allow a single user the ability to create tags, that user being the build bot. Enterprise's of course have all sorts of unique permission models that they want to abide by and most of them could be supported out of the box with a more fine grain model.
There are many other permission uses cases such as fine grain create and delete branch permissions. Only the release users should be allowed to create release/* branches. No one should be allowed to delete the 'master' branch.
There are projects where I want to give developer access, but they are not allowed to create or delete any branch, they can only push new changes that are "finished". If they want to make a in progress branch they need to do it somewhere else.
We already have the different between master and developer uses on protected branches. But it is an interesting idea to protect release/* and stable-* branches by default.
The third paragraph is a bit of an edge case to me. Either you allow them to participate in non-protected branches or you have them work from a fork. Pushing changes is on the same level as creating branches to me.
Another example is having a machine the mirrors a perforce, svn or other rcs. This bot will push up the mirror to a single branch called say 'svn-mirror'. You want to make sure that the mirror bot is the only one that can ever touch this branch. Again the mirror could be its own repo and no one else could be allowed to do anything, but users like to have the mirror along side the other main branches that they can push to.
I can give you a dozen "edge case" examples, each of which I have seen not only desired, but required. Lack of fine grain permissions are one of the three reason why companies (not individuals) will abandon an existing Git server and replace it with an alternative. (See http://benjamin-meyer.blogspot.com/2014/10/so-you-want-to-bu... for my full writeup) And you can't say it is hard to implement either, these permissions are nothing but cascading ref based permissions. A user or group has permissions to read/write/delete a ref or ref regular expression. Honestly just copy what gitolite (which has no frontend so it constantly being passed over) does and you will be ahead of all of your competition.
Add fine grain permissions to GitLab and I would recommend exploring going through the major hassle and pain of replacing Stash with GitLab, that is how valuable of a feature it is. Eventually Stash and the other Git servers will have this capability, might as well beat them to the punch and take some of their customers.
We want to integrate the mirror bot into GitLab itself, allowing you to track external repo's.
We would love to have the permissions of gitolite if we can implement them without complicating the settings for users that don't need this. I would be happy to look at prototypes how to implement this in the UI (I'm @sytses on twitter).
GitLab is open source, so if someone wants these advanced permissions the best way is to build them.
In the case of Github, source control is their primary business... Their lead-in is free to open-source, and this builds a lot of good will. Not to mention that Github Enterprise is a pretty nice project... if they come around to add better traditional project management support, I think it will be one of the best options around.
It's extremely easy to setup a private git server (Linux + SSH + Git), but the extra tooling and visibility they offer to non-programmers is what sells. Not to mention very transparent tooling with Go and NPM.
I know that some people prefer Bitbucket because they have free private repositories too... but my concern there is what is their business model in the end? Github has a simple, effective business model and strategy that works. The good will in the open-source community (from gh-pages, to easy forking/sharing/pull-requests) has made them the first choice for most (at least newer) open source projects at this point. This brings loyalty, so when you job needs to host private repositories, it's only natural to use the same platform you're already interacting with. This is a pretty significant impact.
The only down side, is their dedicated clients, and tooling that is geared only towards their platform. I don't like lock in, and while I don't think that is their intent, it will lead down that path for some. I also find that GUI tooling for Git in general is kind of crappy, though it's hard to carry the flexibility git offers in a GUI while making the most common workflows straight forward. Dealing in a very small team with few branches working mostly against master is much different than several large teams working on a codebase with many branches/conflicts in play.
As a business strategy, Enterprise software has plenty of room for a profit margin. As it stands, they have mindshare and are probably actually breaking even, or making at least a modest profit. This funding round is probably more about flushing out their enterprise offerings, so they are better in terms of competing with alternatives, or even bringing in better bridge/migration support.
I've seen/used Jira, TFS, SVN and plenty of other systems that integrate project management and source control. There's definitely room for much better tooling here, and Github is in a better position than most to take over this space.
Also, if you are a small organization you could pay as little as 7 to have a private repo.
It's mostly CRUD applications with some business logic mixed in.
Nobody is trying to steal your CRUD code.
Edit: just to clarify. I don't mean your crud code specifically. Just crud code in general. Maybe you specifically have some super amazing IP to guard.
Pied Piper?
And I know you probably think IP/code is a company's most valuable asset but for most companies that's not even close. A company's most valuable asset is how it goes about delighting customers.
If you're suggesting that IP/code sitting on GitHub servers is somehow at risk of being divulged then I will disagree.
and also poor security on the part of programmers where they submit ssh keys, for example, to publicly facing projects.
Not sure I understand this. Isn't uploading your code to an AWS box "putting your IP on another company's servers"?
Unless you host your own email, servers, chat, storage and backups, you are putting your IP on another company's servers.
But if you do want to use Amazon securely I believe that they have the ability to encrypt your drive.
That said, rack space is incredibly cheap these days, and throwing in a 1u ubuntu server in a 1/4 secure rack is cheaper than hosting a dedicated vps at amazon.
I completly understand starting out using shared services as a startup, but eventually, and soon, you'll want to move to your own systems. It's just an expense for your business, and you would be irresponsible to leave your systems vulnerable.
(my projects have been more sensitive in the past than the typical CRUD app, and so perhaps I'm paranoid)
Moving to our systems only makes sense to me if its a core part of my business or if 3rd party solutions are inadequate. Paying 2 engineers $75/hr to reinvent IRC/git/email poorly is a poor use of time and money.
At the end of the day, if GitHub steals my IP (for whatever reason) I can sue GitHub (if its not morally wrong, they have a legal reason to discourage them from doing so). If my "1u ubuntu server" is hacked due to a poor default, I have no recourse.
You know the answers to all of these things. Just come out and say what you think about Github and their business model instead of wasting our time answering these supposed questions.
More repositories means more money.
The idea being that just because you don't find inherent value in something doesn't exclude others from finding their own value and additionally triviality doesn't necessary preclude others from claiming value.
> So... what makes them valued at 2B? Do they have any
> revenue at all? Maybe they can hook up with linkedin?
It has been speculated[1] that certain companies/endeavors derive some part of their value from the fact that VC firms and other investors view them as a "force multiplier" for _other_ startups. They have some amount of value simply as being an integral part of the overall software/startup ecosystem, and investors may want to keep a good things going. Further, investors may desire to keep Github from being acquired by some larger company with a different agenda. Investing at a high valuation may result in a lower likelihood of an acquisition.Certainly Github would qualify, if that is the case.
Especially when your repo is public, it won't have the same appeal on Bitbucket.
I don't know what kind of software you write, but if your users choose things based on GitHub vs BitBucket hosting, I think you should find new users.
That just sounds like a reworded "It's what all the cool kids are using" to me.
If you can't describe in words, the possible reason(s) why someone using and/or contributing to a project, would prefer GitHub over BitBucket, it seems like my original comment is valid, no?
I would liken this to Todd Barry's take on Coke vs Pepsi (https://www.youtube.com/watch?v=nacbxCgfQHc):
"It made me very sorry for her, because her body is telling her that she hates something that tastes exactly like something she loves."
The user-functionality differences between GitHub and BitBucket are insignificant.
If the original post was talking about users who download and use an app/library from GitHub, then no I don't understand why the end-users would care if it comes from GitHub or BitBucket - whether you're cloning the repo or downloading a release, both make this very easy to do.
If the original post was talking about users who may submit bug reports, potentially fork & submit pull requests, and there really are people willing to contribute in those ways, but only if the project is hosted on GitHub.com, then I would seriously question those people's values and reasons for contributing in the first place.