Assembla Blog

I "complained" on their blog and got a fair response from their team. Here's what they said: http://blog.assembla.com/assemblablog/tabid/12618/bid/12217/April-14-R… To summarize: they didn't have a sustainable business plan and when the costs got too bit they canceled free service. They say now that they're better prepared. Maybe they're worth giving another try?

If anyone is interested in more details, I've just posted an interview here with the same guy. Worths the check. http://blog.assembla.com/assemblablog/tabid/12618/bid/10041/Distribute…

Was. http://blog.assembla.com/assemblablog/tabid/12618/bid/6986/Release-2-0… Okay, it still is great in terms of features, and maybe for open source/public projects. But their flakiness in the past week and their management's communication issues put them to the "was" category for us.

Assembla (http://blog.assembla.com/assemblablog/tabid/12618/bid/98335/Looking-fo…

I believe that its a test of how quickly you can patch your applications when something like this does come out - We did it in 3 hours from time of bulletin - how about you? http://blog.assembla.com/assemblablog/tabid/12618/bid/93731/Continuous…

Agreed. It looks like the author was getting some heat for that point. http://blog.assembla.com/assemblablog/tabid/12618/bid/87899/Seven-Thin… If you take him for his word, I'm sure he didn't mean anything by it (he says he's in that demographic). But I can't say that I'd let him off the hook that easily. Off-hand comments like this almost always come back and bite hard.

Assembla isn't free for closed-source projects (http://www.assembla.com/plans?locale=en) unless there's a hidden plan. Apparently they made the change back in 2008 (http://blog.assembla.com/assemblablog/tabid/12618/bid/6986/Release-2-0… but this article was written today which is confusing. Am I missing something? BitBucket (http://bitbucket.org) went free for private repositories a while back and recently added git support. That might be a better alternative today.

Which is apparently what Assembla has done for internal product development: http://blog.assembla.com/assemblablog/tabid/12618/bid/7437/Why-Subvers…

Assembla is also having issues with some code repositories (including my private SVN) http://blog.assembla.com/assemblablog/tabid/12618/bid/44389/Problems-w…

I could have sworn their accounts used to be free and then they took away the free accounts in 2008. http://blog.assembla.com/assemblablog/tabid/12618/bid/7019/New-subscri… I remember because we were using assembla for some stuff and then moved away when they started charging. I guess that move didn't work too well for them.

I think the rationale behind this is important for all SAAS (and software) businesses to learn from: a) Desirable customers really don't care about the difference between $4 and $9. b) The user experience of consistent and predictable pricing is much more important than getting prices which are "rationally connected with costs" or "as cheap as possible". (Businesses in particular hate microtransactions. OKing a $20 a month transaction is trivial, OKing an ongoing variable cost is not -- I need to attach detailed projections and get the projections vetted by three people.) c) If you prominently advertise Only Costs $2! and Use Us Because $10 Is Too Much To Pay For This Service! then your customer base is going to be primarily people who are looking to spend no more than $2 and you will have to write blog posts when you plan on doing major, disruptive changes like charging more for a business input than their morning latte costs. Edit: Prior blog post on pricing here: http://blog.assembla.com/assemblablog/tabid/12618/bid/7870/SaaS-is-che… Factoids: Most popular plan costs $2.30. Average ticket size below $10. Company very, very proud that their average customer spends less than the cheapest plan at competitors. (This was, apparently, not a red flag at the time.)