New Size Slugs for Droplet Plan Changes
Today, we announced wide-ranging changes to our Droplet plans, bringing improved resources across the board. These new plans are now available via the API and can be referenced using their respective size slugs.
Size slugs are human-readable strings used to specify the type of Droplet
in certain API requests. In the past, size slugs were typically based on the
amount of RAM provided with the plan (e.g.
1gb). Moving forward, we are
standardizing on a format comprised of the identifier for the Droplet’s class,
the vCPU count, and the amount of RAM in order to provide more flexibility in
the plans we are able to offer you. For example, our new $5 per month Standard
Droplet comes with 1 vCPU and 1 GB of RAM. So its size slug is:
Applications and scripts with hard-coded size slugs must be updated to take advantage of these new plans. In order to provide a transition period, 1st Generation Droplet plans will continue to be available via the API using the legacy size slugs until July 1st, 2018.
The table below shows the new 2nd Generation Standard Droplet plans along with their corresponding size slug. For always up-to-date information on available plans and pricing, please see our pricing page.
|Standard||s-1vcpu-1gb||1||1 GB||25 GB||1 TB||$5|
|Standard||s-1vcpu-2gb||1||2 GB||50 GB||2 TB||$10|
|Standard||s-1vcpu-3gb||1||3 GB||60 GB||3 TB||$15|
|Standard||s-2vcpu-2gb||2||2 GB||60 GB||3 TB||$15|
|Standard||s-3vcpu-1gb||3||1 GB||60 GB||3 TB||$15|
|Standard||s-2vcpu-4gb||2||4 GB||80 GB||4 TB||$20|
|Standard||s-4vcpu-8gb||4||8 GB||160 GB||5 TB||$40|
|Standard||s-6vcpu-16gb||6||16 GB||320 GB||6 TB||$80|
|Standard||s-8vcpu-32gb||8||32 GB||640 GB||7 TB||$160|
|Standard||s-12vcpu-48gb||12||48 GB||960 GB||8 TB||$240|
|Standard||s-16vcpu-64gb||16||64 GB||1,280 GB||9 TB||$320|
|Standard||s-20vcpu-96gb||20||96 GB||1,920 GB||10 TB||$480|
|Standard||s-24vcpu-128gb||24||128 GB||2,560 GB||11 TB||$640|
|Standard||s-32vcpu-192gb||32||192 GB||3,840 GB||12 TB||$960|
Available Droplet plans, the resources they provide, and the size slug used to
identify them can be accessed programmatically by querying the