DigitalOcean Droplets are Linux-based virtual machines (VMs) that run on top of virtualized hardware. Each Droplet you create is a new server you can use, either standalone or as part of a larger, cloud-based infrastructure.
We offer four different kinds of Droplet plans: one shared CPU plan and three dedicated CPU plans.
|Droplet Plan||CPU||Range of Resources||RAM-to-CPU Ratio||Processor|
|Standard||Shared||1 - 32 vCPUs
1 - 192 GB RAM
|General Purpose||Dedicated||2 - 40 vCPUs
8 - 160 GB RAM
|4 GB per vCPU||Intel Xeon Skylake (2.7 GHz, 3.7 GHz turbo)|
|CPU-Optimized||Dedicated||2 - 32 vCPUs
4 - 64 GB RAM
|2 GB per vCPU||Intel Xeon Broadwell (2.6 GHz)
Intel Xeon Skylake (2.7 GHz, 3.7 GHz turbo)
|Memory-Optimized||Dedicated||2 - 32 vCPUs
16 - 256 GB RAM
|8 GB per vCPU|
|Ubuntu||20.04 (LTS) x64
18.04.3 (LTS) x64
16.04.6 (LTS) x64
16.04.6 (LTS) x32
|FreeBSD||12.1 x64 zfs
12.1 x64 ufs
11.3 x64 zfs
11.3 x64 ufs
|CoreOS (only available via the API)||2512.3.0 (stable)
Each Droplet includes free outbound data transfer, starting at 1000 GiB/month and scaling up. Outbound data transfer is shared between all Droplets each billing cycle. Additional transfer is billed at $0.01/GiB, but most users don't exceed the amount included with their Droplets.
You can view your accumulated monthly transfer allowance on your account's billing page in the Droplet transfer section. For an in-depth description of how data transfer accrual works, read our detailed bandwidth billing page.
Most Droplet plans are available in all regions. General Purpose Droplet plans are available in NYC1, FRA1, SFO2, AMS3, and SGP1.
Due to limited capacity, NYC2, AMS2, and SFO1 are currently disabled for users who don't have resources in those regions already. Standard plans larger than 48 GB of RAM and all optimized plans are unavailable in these regions.
Learn more in the regional availability matrix.
Tags are custom labels you apply to Droplets that have multiple uses:
Filtering. Tagging multiple Droplets with the same label lets you organize your resources and view a filtered list of Droplets that share that particular tag.
Automatic inclusion in firewall rules and load balancer backend pools. Automatically include Droplets in a firewall or load balancer configuration by tag, minimizing administration overhead when adding new Droplets to your infrastructure.
API call execution on multiple Droplets at once. Initiate an action across all Droplets with the same tag using the DigitalOcean API. Identifying groups of Droplets and administering all of them at once reduces the time required to manage resources.
DigitalOcean Floating IPs are publicly-accessible static IP addresses that you can assign to Droplets. A floating IP provides an additional static address you can use to access a Droplet without replacing or changing the Droplet’s original public IP address.
DigitalOcean Block Storage is a flexible, convenient way of managing additional storage (in units called volumes) for your Droplets. Volumes are independent resources that you can move between Droplets within the same region. You can increase the size of a volume without powering down the Droplet it’s attached to. They’re most useful when you need more storage space but don’t need the additional processing power or memory that a larger Droplet would provide,
DigitalOcean Cloud Firewalls are a free, network-based, stateful firewall service for your DigitalOcean Droplets. They block all traffic that isn’t expressly permitted by a rule. You can define the Droplets protected by a firewall individually or by using tags.
DigitalOcean Load Balancers are a fully-managed, highly available load balancing service. Load balancers distribute traffic to groups of Droplets, which decouples the overall health of a backend service from the health of a single server to ensure that your services stay online.
Some Droplet network traffic is restricted to help prevent malicious actions, like reflected DDoS attacks. We know these restrictions also prevent functionality like configuring direct server return and using Droplets as routers and site-to-site VPN gateways. Future changes to our network will support this functionality. Until then, some workarounds include using a VPN mesh network or overlay network.
The following types of traffic are restricted:
TCP and UDP traffic on port 11211 inbound from external networks (due to the Memcached amplification attacks in March 2018).
Traffic not matching a Droplet's IP address/MAC address.
SMTP via Floating IPs and IPv6.
Droplets have a maximum network throughput limit of 2 Gbps.
By default, users can create up to 100 volumes and up to a total of 16 TiB of disk space per region. You can contact our support team to request an increase. You can attach a maximum of 7 volumes to any one node or Droplet, and this limit cannot be changed.
You can't create more than 10 Droplets at the same time using the control panel or the API.
We have released a Droplet metadata endpoint which returns whether or not a Droplet is scheduled for a live migration. The impact of live migrations on Droplets is minimal, so users now only receive direct notifications for migrations that require us to power down a Droplet, which (except in emergencies) we send 7 days in advance.
Memory-Optimized Droplets are now available for the BLR1 datacenter region.
Memory-Optimized Droplets are now in general availability and are available in the SFO3 and TOR1 datacenter regions.
Users can now search for Marketplace apps directly from the Droplet Create page.
For more information, see all Droplets release notes.