Ask HN: What Paid Services Do You Use For Your Startup?
What paid services do you find the most useful in running your startup?
What paid services do you find the most useful in running your startup?
http://journal.dedasys.com/2008/11/24/slicehost-vs-linode
I was with SH myself, and before I wrote that article, I dropped them an email asking about the 64 vs 32 bit thing, and was simply informed that they have no plans for 32 bit, so I went ahead and switched, then wrote my article and have been happy since. I sincerely hope the SH guys will get competitive again, at which point I'll gladly update my article.
Also, something that Linode was missing for a while was backups. They're rolling them out now:
http://blog.linode.com/2009/04/03/backup-service-enters-beta...
The "community" section of the Slicehost website is really exceptional though. Insanely great.
Bandwidth is pooled between all of your slices.
Money is pooled -- if you pay a certain amount, you get the "annual discount", but then you can use that for paying for whichever slices each month. And you can bring slices up and down whenever you want to, and pay a prorated amount.
There's a nice API so you can automate a lot of your activities.
On the other hand, Linode does seem to be a bit cheaper on RAM and a lot cheaper on bandwidth.
Bandwidth is pooled between all of your nodes (and it doesn't matter which data center you place them in).
We offer prepayment discounts: 10% for 12 months and 15% for 24 months. We also prorate all billing to the day (you only pay for what you use).
There is an API for the DNS Manager, with more to come.
They're cheap, so I still use them for personal projects, but personally, I'd never trust my business with them.
Just another data point.
In my case, the "left on the table" amount is about 1/100th of my sales. From last week. That doesn't exactly justify me dropping everything and spending my freaking expensive engineering time figuring out how to migrate without causing breakage or downtime.
Www.ycombinator.com is a machine at Pair Networks, and News is at The Planet. We use EasyDNS for domains.
We used to use Highrise (we may actually still be paying for it) but we abandoned it because it wasn't flexible enough.
Fogbugz (bug tracking)
Github (scm... paying but included with EY)
NewRelic (perf monitoring... paying but included with EY)
Protx (payment gateway. Awful customer service, don't recommend them)
Easyspeedy (test server that we should get rid of, really)
We (and our users) get satisfaction from them...
I also use Google apps for my domain for email hosting (free). I also use Woopra's real time analytics (free).
I have an online store that I'm paying Yahoo Merchant Solutions for. I also pay for an extra line with Vonage for my business line. ($10 a month).
I've used Google Adwords for advertising occasionally.
Also use EC2 for test and staging servers as then we only need them up for the actual test or staging period.
To the question I also pay for authsmtp, and will probably be using the pay level of "New Relic" as well soon, for rails profiling.
It is not trivial to implement in an application but does seem to be very concise for the features it provides. The con for this flexibility naturally is increased complexity. They do offer a 'Simple Pay' solution if you don't need the extra features, but I've not used that.
During development you can tie you application to the FPS 'sandbox' which simulates the complete user experience as well as virtual payments and fees so that you can see exactly how things will work in production from various points of view with out actually moving money around.
I needed subscriptions, so I could not use the other popular solutions (when the decision was made), and therefore can't compare. However, I refuse to use paypal because they put 100% of the risk on the account holder, while at the same time not disclosing information about the purchaser to allow for fraud investigation, this is flat out unacceptable.
Lots of freebies too, though.
The internal side: serverbeach, github, campfire
I think they're all great, so it's easier to say what we would switch away from.
We would switch from serverbeach to slicehost if we were scaling faster.
We would switch from highrise to a different CRM if it was easier to write custom reports.
AdWords (I spend more than everything else on this list, doubled.)
SwiftCD (outsourced CD fulfillment)
Paypal / Google Checkout
Slicehost
Microsoft AdCenter
CrazyEgg
Clicky (getclicky.com)
After that, it's just business class internet service and the electric company . . . I say screw all this hosting, cloud hosting, and bunches of paid web apps; in this day and age you should be able to install apache and set up whatever you need, and move to Rackspace or hire accounts if you are ever actually making money (which I'm not).
All of those services provide things that I need, but don't want to spend time administering. In the case of The Planet they are providing the network, but I still maintain the servers. I am thinking about moving to Amazon once the contract is up.
From a non-webapp perspective, I pay for legal and accounting too. I have thought about paying for a personal assistant, but haven't pulled the trigger yet.
Other services I subscribe to and find work well are: - Zoomerang (online surveys) - MyEmma (e-mail marketing) - GoToMeeting (web conferencing) - Jott (voice capture and transcription, integrated with Smartsheet)
A merchant account is in the cards, though we don't know where yet (and haven't finished the process of incorporation, so can't get one yet).
At some point we might use Exceptional (I like the look of it, but I'm not a coder so I'm not making the decision of whether we need it or not) and if Get Satisfaction proves useful perhaps pay for a plan there. We'll see.
With unfuddle you can even get a (small) free private repo.
However, it is dirt simple to set up a git repository for use by a few people on a box where they have accounts anyway.
cd /var/local/
mkdir myapp
... appropriate permissions, add a few files ...
git init
And you're done. Granted, you can do fancier things, but we're talking about startups with just a few people here, right?Just my $0.02
* Since you connect to the server anyway, that one's open.
* Security patches is a regular apt-get update and not much more.
* Ticket management... ok, that's an extra, but github still doesn't have a ticket tracking system, does it?
Also, my point depends on an assumption that may not be true for everyone: that you have your own server that you run.
I could manage all of that stuff directly, but I shouldn't because I don't do it all day long which means that either I'll a) do it wrong or b) have to do several hours of research to make sure I don't do it wrong or c) routine multi-hour interruptions when things break or d) combine a+b+c because that's what will happen in reality.
It's because of this that we outsource the following things that we could do ourselves:
* Email hosting (Tucows)
* DNS servers (Tucows)
* VoIP (Vonage)
* 800# (Onebox)
* External system monitoring (Pingdom)
* General server sysadmin (a friend of mine)
* StreamSend (Email Marketing - not that good, but dealing with RBL and email deliverability is worse)
* Payflow Pro (credit card gateway - BAD customers service o/w OK)
It costs some REAL money, but saves much more in opportunity costs, headache, etc. Plus our services improve as these companies improve offerings.
We only directly manage things that can save us TONS of money or are strategically important. Here's the list of those things:
* SugarCRM
* RT (bug tracking. was outsourced but too $$ so we moved in house)
* Internal system monitoring
* Hosting (we run our own systems since we have tons of custom dependencies)
I guess it might be okay to run git on my mail server. Except I don't have a mail server: That's outsourced. (Way too much trouble to run for oneself.) All I run for myself is local machines (not about to serve from those -- poor uptime, firewalls are a pain) and web/database servers, and I don't want the constraint of even having to remember that git is running on one of them. I want a git setup that is out of sight, out of mind, and far away from my bumbling sysadmin (a.k.a. "me").
And we're haggling over the price of github, here. It's dirt cheap.
One point, however:
> You can't switch server hostnames or IPs without potentially affecting your git users.
Yes, you can. Computers should have:
* One or more IP addresses.
* A hostname that is attached to that computer, and only that computer, such as thor.example.com
* Hostnames that are attached to services on computers, such as git.example.com, mail.example.com, www.example.com, and so on. You can change these to point where they're needed, so as to not cause any interruptions or problems for your users.
> And we're haggling over the price of github, here. It's dirt cheap.
Sure, but I'm cheap, and for my setup, it's money I can save, and it just seems weird to pay for something that's so easy to set up.
But if it's a labour of love? Priceless...
- Slicehost (some hosting)
- Datapipe (hosting)
- EC2 (Document/media conversion)
- S3 (Storage)
- Panther Express (CDN)
- PBWiki
- PivotalTracker
- Protoshare
- DNSMadeEasy
- Hosted MS Exchange
- JIRA/Fisheye/Crucible
Migrating away from: Slicehost (redundant with AWS) Lighthouse (redundant with Pivotal Tracker)
Already migrated away from: Basecamp
Slicehost (Hosting) AWS (Storage) Authorize.net (Recurring Billing) Bank of America (Banking)
and we're currently looking into paying for an 800 number...anyone have any suggestions for this?
EDIT: Scratch that. Looks like I'll need your email addresses to refer you. You'll each get a $25 credit and I'll net $20 total. Not bad.
My address is brian at firstblogmedia dot com. Drop me a line ASAP.
We pay for slicehost.
webfaction, AWS (ec2, sqs, s3), paypal
Typical Rails shop stuff, :)
However, my system is not fully implemented and deployed (hence no link yet), so I'm not ready to provide a full endorsement. I can only say that the experience so far on the development side has been very good, and the sandbox makes extensive testing before deployment very easy.
I will report back when I've deployed the system in production.