The Legit Teams Blog

Sept
28

Why the World Needs Another Git Repository Hosting Service

We woke up at 8:00 AM on a Saturday, a time unreasonably early for the average college student, to attend our first hackathon as a team. We had already planned out what we wanted to create; the task at hand was simply to start building it. So what was the first step?

We needed a git repository to collaborate on—to use to work simultaneously on our project. Yet this entailed having a server for hosting, creating a repository on the server, adding a user so everyone could access the system, and giving the user the necessary permissions. And that, well, that simply got us a remote we could use with git. No interface to view the code and review each other’s changes, no notifications when someone had pushed, no simple way to manage further collaborators and permissions when a friend wanted to join in.

Why? Couldn’t we have just used some public repository hosting service for free? Indeed, we could have, but this project was private. It was a service we were planning on launching after the Hackathon—a possible startup idea, if you will. It was not code we wanted to share with the world.

So the question follows: couldn’t we have just used, say, GitHub, under a paid plan? Certainly. But GitHub limits us on the number of repositories we can create. And, as college students, our private projects combined included developing three iPhone games, working on potential startups, and creating sites for clients as freelancers. That’s already a good deal of repositories. And what about all the assignments for our computer science classes? What about the group projects that were—and are—begging for simple, private git collaboration? What about secure data we store in git that we’d like to back up on an external server? GitHub’s repository limit just didn’t make sense.

But don’t get us wrong; GitHub is a service that should be commended. We use it for our public projects, and we would recommend it to you in a heartbeat. Even GitHub paid plans, for the number of features the service provides, are worth it for the right audience. But that’s the key: the right audience.

Small groups of college students, individuals, and/or freelancers, as we started to experience, are not necessarily the right audience. We, with a myriad of private projects and needs constituting a nice interface, notifications, and easy management, did not need all that GitHub offered. Forking, graphs, wikis, network tacking, and pages are great, but for open source.

So why should we be paying approximately $1/repository when we don’t need all the open-source-focused features? And why does it make sense to pay per repository when the real cost is in space and IO? Our whole set of repositories probably aren’t more than 500 MB. And 500 MB, at current prices, costs merely a few cents. IO, in like manner, is negligible; we only push our repositories to the server once in a while. So why $10 or $20 a month?

What we need is private repositories—private repositories tailored for small teams. And that’s why we created Legit Teams. We provide you with a nice code viewing interface, notifications, easy repository setup, and a simple way to manage collaboration. In return, you pay for space. You get unlimited collaborators and unlimited repositories, as these cost us nearly nothing. It’s as simple as that.

But first try our free plan, which allots you enough space for a few projects, as you’ll automatically be signed up for it when you register. See whether you like the service, and proceed with it if it meets your needs. If you experience problems, or dislike anything, we’d love to hear your feedback to make our service better.

We hope you benefit from Legit Teams, and can only ask for your support by becoming a paid member. Until next time.

Karthik Viswanathan and Ayush Sood
Legit Teams Co-Founders