GetGit

Simple Gitea hosting

October 2, 2019 Launched!

I feel like I’ve been working on GetGit forever (it’s been about 9 months!), but I’m happy to say it has finally been launched and even got a few signups on its first day!

This is my first real product launch. I learned a lot and have a lot more to learn. One of the biggest lessons I’ll take away is to be OK with good enough. Saying “good enough” may sound bad, but it’s way better than trying to achieve perfection (which will never happen). Things can always be improved, and it’s more satisfying to ship something than to perfect it forever.

There’s still more work to do. I have new features I want to develop and launch and lots of marketing to do!

Todd Yandell

7 Likes

4 Comments

Say something nice…

Post Comment

2
This is great. Good idea that's not so different as to confuse, a fresh pricing model, nice looking landing page.

Minor suggestions:
- For "Sign up and get started with Gitea." maybe "Sign up to get started with GetGit."
- For "If all else fails, other pricing options are available" maybe "And if you still need more room, other pricing options are available"
- For "It’s (sort of) simple to set up a server, but managing it is another story." maybe "Although it’s simple to set up a server (sort of), managing it is another story. "
- For "we chose the alternative: Just pay once. It’s like how buying software used to be." maybe "we chose the alternative: just pay once. That's how buying software used to be." (and maybe end with an exclamation mark)
- For "It works for us thanks to the lightweight design of Gitea. Our infrastructure is set up specifically for Gitea, and we think it works great!" maybe "This pricing works for us thanks to the lightweight design of Gitea. Because our infrastructure is set up specifically for Gitea, our compute and storage resources are used very efficiently." (I'm not as sure about the wording of this one, but you do want a clear answer...the first thing I thought on seeing the $15 was "how can GetGit afford to do this? are they losing money on every customer? will they burn through their cash and leave me looking for new hosting?")
Again, despite all of these suggestions, it looks good and sounds promising!
Shawn

·
7 years ago
·
Reply
1. 2
  
  Thanks Shawn, those are all great suggestions! I really appreciate the time you took to rewrite some of my copy. I'll definitely be making a few adjustments.
  
  You make a great point in your last comment. I don't want customers to feel uneasy about the pricing model. It's a big part of what I wanted to do to make Gitea more accessible, but maybe it does sound too good to be true, or at least untenable.
  
  As a user, what do you think would ease your mind about the price? I want to offer a good explanation but I don't necessarily want to get into the technical details of how it all works to try to prove it. Do you think it would help to present the price as an introductory price?
  
  Thanks for your feedback!
  
  tyandell
  
  ·
  7 years ago
  ·
  Reply
  1. 1
    
    Glad I could help!
    
    "Introductory rate" is good for a few reasons. I hear that and think "I'd better take advantage of this now"; I assume people joining after me will pay the full rate and keep the business afloat; and I feel like I must be smart and cool to be in a position to early-adopt it.
    
    Another option would be to call $15 the Base Plan or Standard Site or Budget Tier; then I would assume others who need more space or features than I do will keep the service profitable. If it is presented as one of these -- a "minimal, no-frills" account -- I might actually be less concerned about "how is this sustainable?".
    
    As far as going into technical details, if it wouldn't be giving away the secret sauce and if it could be done succinctly, your prospects (people looking to host their code away from Github, Gitlab, or Bitbucket) should be able to handle it.
    
    One other doubt that comes to mind is backups and failover. It might be good to throw in some mention that these are handled. Doesn't have to be an SLA, just evidence of a commitment to data protection.
    
    Shawn
    
    ·
    7 years ago
    ·
    Reply
    1. 2
      
      I totally agree. I'll be implementing some of these suggestions soon and we'll see how it goes! Thanks again for all your help!
      
      tyandell
      
      ·
      7 years ago
      ·
      Reply

GetGit

About

People