GitHost Shutting Down April 30th

On April 30th GitHost will be closing it's doors. We've had a good run, but the growth we had hoped to see just isn't there, and it's time to move on and focus on other things.

You will continue to have service to your instances until April 30th, at which time all remaining instances will be destroyed. You will not be billed again for any instances online. Please be sure to backup any Git repos you would like to save before that time. We will not be able to recover any data for you.

Regards,

The GitHost Team

SSL support for custom domains

We just released a nice update to our CE instance support, SSL for custom domains.

Now if you are running a custom domain for your CE instance you can add your SSL certificates! Any new instances created will now have the option to add SSL for custom domains, and all existing instances with custom domains can be edited to use your own SSL certificates.

To celebrate we're also giving out $10 worth of credit so you can try SSL support for your own domains, at no charge! Use promo code "customssl", it works for new and existing users!

Get Started Now!

Get free instances by referring your friends!

Want to earn some credit towards free instances and help us out in the process?

Head over to your Account Settings page and start sharing your unique referral link. For every user that signs up and uses GitHost, we'll credit your account $10 before billing you. Invite enough of your friends and you could end up using GitHost for free each month!

Introducing zero configuration GitLab CI

Gitlab product ci

If having a secure, managed GitLab CE instance to host your code is only half the battle, then being able to run your tests and builds on the same platform is the other. That's why today we're proud to release our newest feature, zero configuration GitLab CI!

Now, in one click you can have a GitLab CI instance created and linked to GitHost, GitLab Cloud, or your own personal install. To make it even better, with the flick of a slider you can spin up build runners in seconds, all linked to your CI master coordinator, with zero configuration!

Need to burn through a large amount of builds quickly? Spin up a pool of runners to chug through the workload, then simply turn down the dial when you're done!

Pricing is simply $10 / month per master coordinator and $10 / month for each runner. If your runners are not online the entire month we will only charge for the time they were running.

Try it today! Use promo code "gitlabci" for a $10 credit after sign up!

Linking your new CI instance to CE instances is easy with support for GitHost, GitLab Cloud, or any other GitLab CE instance!

GitHost or GitLab

Spin up and destroy build runners at will based on your workload.

GitHost or GitLab

Here's a quick run through from CI instance creation, to linked build runners, with zero configuration!

GitHost Ci

Try it today! Use promo code "gitlabci" for a $10 credit after sign up!

Introducing lower GitLab CE pricing

We want everybody to have access and benefit from personal, private GitLab CE instances. That's why today we're proud to announce that we've lowered the prices for our Developer and Business plans, and removed the user limits on all plans!

Now you can get started with a Developer plan for only $7/month, with unlimited users and projects. Need a larger plan? You can also choose from our Startup plan for $25/month, or the Business plan with lower pricing for $50/month.

Larger plans get you larger, beefier instances with more cpu and memory, which helps to support more users and larger projects.

What are you waiting for? Checkout our plans and signup today!

GitHost vs GitLab.com

Ciro Santilli raised some very interesting questions the other day on a GitHub issue, and I'd like to recap them here.

His question basically boiled down to: "Why choose GitHost over GitLab.com's free offering" and here is my answer.

GitHost is different from GitLab.com in several ways. First, you are hosting your repos on private instances with GitHost, whereas on GitLab.com you're in a shared environment. That may not be an issue to some people, but others feel safer knowing their code isn't sitting next to others. On that note, another upside to private instances is, if GitLab.com were to become the target of a break in, even if the end result was to get someone else's code, your code could potentially be leaked also. Most businesses don't want to take that risk.

GitHost handles upgrading and monitoring your instances for you also, just like GitLab.com does. One of the main takeaways from GitHost is that you can also have your repos and data backed up to amazon for free, to your own amazon account. This leaves you in control of your data, free to move it to any GitLab instance you'd like.

One last note about GitLab.com's free offering. If they continue to grow, and ever reach GitHub scale, the unlimited users, unlimited private repos for free model isn't going to scale. Eventually the infrastructure and maintenance costs of offering that service for free isn't going to scale or be an economical option to get exposure for GitLab.

With that said, I love GitLab. I've contributed code to their open source projects, I built and maintained DigitalOcean's one click GitLab image during my time there, and I've spoken with Sytse (GitLab B.V CEO) about GitHost and it's future. Sytse is a great guy, and fully supports GitHost because it means more exposure for their enterprise offerings.

GitLab is wonderful, and is helping to decentralize our community's reliance on the monopolies like GitHub which are quickly getting shaky track records both in terms of uptime and moral issues.

GitHost is a bootstrapped startup. We have no outside funding and running costs are very minimal at this point. This leaves us in a position to grow and fine tune the product without rushing to market and gain new users because we have massive bills to pay. One of the biggest pain points of hosting your own GitLab repo is that you have to handle upgrades and security releases yourself, and it's sometimes a time consuming procedure. GitHost abstracts all of that away from the users. We handle the upgrades and security fixes. We handle uptime monitoring and server health checks, and we support our users anytime day or night. We also handle automatic nightly backups to Amazon. All of this combined makes maintaining your GitLab install effortless and transparent, it's all taken care of, for a minimal monthly cost. If your main objective is to work on code, or support your business then it's a no brainer. Let us handle everything, and you can focus on doing what you do best, shipping code.

GitLab.com is great, and if you don't have business constraints or are just looking to host personal side projects then it's a great option, I even have an account there.

GitHost is for professionals and businesses that want the peace of mind of dedicated repo hosting, monitored uptime, and a business model that can scale because it's not freemium.

If you have any questions feel free to email [email protected]

Try GitHost free for a week!

We want everyone to be able to try private GitHost instances with automated upgrades, backups and uptime monitoring, that's why today we're happy to announce that you can now try GitHost instances free for a week!

Simply create an instance and give it a spin. If you don't like it in any way simply delete the instance within 7 days and you'll never be charged for it!

This applies to both new and existing users. Each and every instance you create will be exempt from billing for the first week of it's existence. If the instance is over 7 days old, whether active or deleted, it will show up on your monthly invoice as usual.

GitHost for Nonprofits and Educational Institutions

We are committed to ensuring everyone has access to their own private GitLab instances for collaborating and managing projects and teams. With that in mind, we’re happy to announce that we are now offering free hosted, private GitLab instances for Nonprofit and Educational organizations. It’s super easy to get setup, just sign up using the normal channels and shoot us an email to [email protected]. We’ll verify your information and make sure you never get charged for your GitHost instances!

Heartbleed and GitHost

Heartbleed

The Heartbleed bug affected nearly every operating system in existence, and had everyone from solo developers to enterprise level businesses rushing to fix the problems caused by it. Moments after learning of the vulnerability we began patching the OS level OpenSSL libraries on our infrastructure and on all user GitHost instances. Shortly after that, GitLab released updated packages to fix the issue within the GitLab software itself. Last but not least, our SSL certificates were regenerated using the new OpenSSL libraries and distributed to all user instances running on the *.githost.io subdomain.

If you'd like to test and verify your GitHost instances are secure please checkout Filippo Valsorda's online Heartbleed test tool.

This bug caught the internet off guard, but we patched and secured our systems quickly. GitHost will always be on top of security issues and respond quickly to all reports.

Instance metrics have arrived!

Screen+shot+2014 04 06+at+8.58.25+pm

We've been working hard to make GitHost dead simple for hosting private GitLab instances. One important component to any system is having insight into resource usage. We believe that being able to see what's happening with your instance will not only help you make informed decisions about your business, but it will also help us to better serve you.

So, today we're proud to have launched instance metrics! The next time you view your instance details page you'll notice the nifty new graphs section! We're starting out with tracking memory and disk usage and displaying those on the UI in 15 minute, 60 minute, and 24 hour intervals.

More metrics will follow after we've given the current setup some time to bake in production. Your feedback is important so please let us know if there are any specific things you'd like to see on GitHost!