- Provisioning is conceptually cheap, and this is their killer feature. You click the "Make a new VPS" button, you pick your distro, how much RAM you want, and an SSH key, and they spit out an IP address less than a minute later. `ssh root@198.xxx.xxx.xxx`
This is much nicer than eg. finding or downloading a box to mess with Vagrant or taking who knows how many hours to set up your own distribution in VirtualBox. Just a few minutes ago, I spun up a box, messed around with Gitlab, and destroyed it. Completely seamless; has all but replaced VBox for these "one-off VM experiments" that I sometimes try.
There's also an API for automatic provisioning if that's your thing.
- Pricing: Cheap, as you'd expect. 512MB for 0.7¢/hr or $5 a month. There's no difference between monthly and hourly pricing so if you want to pay a buck fifty to rent the 24-core 96GB monster for an hour, have at it.
The thing about DigitalOcean is that they're still such a new service that they haven't gotten everything all polished yet:
- No kernel upgrades. The kernel is kept outside of your virtual machine, which means that if you upgrade your kernel, then you'll get mismatched modules and your network interface won't come back. They've pinned kernel updates in ubuntu so this shouldn't be a problem, but you have to say "IgnorePkg = linux" in your /etc/pacman.conf if you're on arch. Security updates will be a pain though...
- You can't boot into a recovery image/liveCD. If the above happens to you, I assume you'll have to either restore from backup or file a ticket and ask them to pick things out of your VM's hard drive. (You do get raw console access provided by an HTML5 VNC client, which can be useful)
- Payments are weird because you can't see your VM or network usage, so it's unclear how much you'll be charged until they bill you at the beginning of your month. If you select to pay via paypal, you can't pay by a credit card linked to your paypal account (at least for the first transaction any way); I had to give them my credit card information directly. (I imagine they do this to cut down on fraud or spam)
- Services are still a bit barebones. You have to roll your own load balancing. There's no support for mounting an image into another VM to recover files. No internal networks; every VM has a public IP address, which makes me curious to see how they're going to handle IP address depletion if they ever get popular. You have to use your own firewall via iptables or similar.
They will manage your DNS for you though, if you like, and you can ask them to take a snapshot and automatically back up your VM every day or so.
My verdict? I think they're lovely and I really reccomend them especially for personal projects, but as of this writing (early april 2013), you should think about these things before you decide to use them in production.