# DigitalOcean v5 Droplets decouple CPU, memory and storage — but drop the monthly usage cap DigitalOcean’s generally available v5 Droplets use 5th-generation AMD EPYC processors, let builders size compute, memory, storage and networking more independently, and switch the new configurations to per-second billing at hourly rates without a monthly usage cap. v5 gives DigitalOcean users a more composable VM shape instead of choosing only from fixed bundles, with vendor-claimed per-core performance gains up to 30%. The billing model deserves equal attention: long-running v5 instances do not inherit a monthly usage ceiling. - Status: Active - Published: 2026-08-28T22:07:20+12:00 - Updated: 2026-08-28T22:07:20+12:00 - Categories: Cloud & Infrastructure, Hosting - Tags: AMD EPYC, cloud hosting, compute sizing, DigitalOcean - Canonical HTML: https://beyondthe.news/dossiers/digitalocean-v5-droplets-flexible-sizing-amd-epyc-per-second-billing ## What changed DigitalOcean made v5 Droplet configurations generally available in the `mem1`, `ric1`, `atl1` and `mkc1` datacenters on August 25–26, 2026. The new generation runs on 5th-generation AMD EPYC processors and lets users configure CPU, memory, storage and networking with more independence than the older fixed plan catalog. Shared-vCPU and dedicated General Purpose configurations are available for standalone Droplets, with a subset also supported for DigitalOcean Kubernetes. DigitalOcean says v5 delivers up to 30% higher per-core performance than the previous generation. The new configurations are billed per second at an hourly rate and do not have a monthly usage cap. ## Why it matters The practical change is both technical and economic. Builders can right-size a memory-heavy, CPU-light or storage-specific workload more closely instead of paying for a larger fixed bundle simply to obtain one constrained resource. At the same time, the absence of a monthly usage cap means a VM that stays online all month should be budgeted from its hourly rate rather than assuming DigitalOcean’s traditional monthly ceiling will limit the bill. Teams should compare workload-level performance and total monthly cost, not only the new processor-generation headline. ## v5 turns Droplet sizing into a more composable resource choice DigitalOcean says v5 lets customers configure vCPU, memory, storage and networking independently within the new catalog. Shared configurations use shared vCPUs for cost-sensitive workloads, while General Purpose variants provide dedicated vCPUs. That makes the platform more suitable for applications whose RAM or storage needs do not scale neatly with CPU count. ## The processor refresh can change per-instance consolidation v5 runs on 5th-generation AMD EPYC processors. DigitalOcean claims up to 30% higher per-core performance compared with its previous generation. That is a vendor claim and workload-specific, but if reproduced on an application’s own code it can reduce the number of vCPUs or instances needed for the same throughput. ## The billing model needs explicit monthly arithmetic DigitalOcean documents v5 as per-second billing at an hourly rate without a monthly usage cap. That gives precise billing for short-lived instances, but it also means long-lived production VMs should be modeled from actual running hours. Builders migrating from older capped Droplet plans should not assume the same maximum monthly spend behavior. ## Availability is still region-limited The first GA v5 regions are Atlanta, Richmond, Kansas City and Memphis. DigitalOcean Kubernetes supports only a subset of v5 configurations there, with specified boot-disk sizes. Teams with latency, data-residency or multi-region requirements should therefore treat v5 as a regional option rather than a universal replacement for the existing Droplet catalog. ## Key details - DigitalOcean announced v5 Droplet general availability on August 25–26, 2026. - v5 runs on 5th-generation AMD EPYC processors. - DigitalOcean claims up to 30% higher per-core performance than the previous generation. - Users can size CPU, memory, storage and networking more independently. - Both Shared and dedicated General Purpose v5 configurations are available. - Initial v5 availability includes `atl1`, `ric1`, `mkc1` and `mem1`. - A subset of v5 configurations can be used in DigitalOcean Kubernetes node pools. - v5 is billed per second at an hourly rate without a monthly usage cap. ## Builder takeaways - Rebenchmark representative CPU-bound requests before simply reproducing your old vCPU count on v5; better per-core performance may change the most economical shape. - For memory-heavy services, compare a right-sized v5 configuration with the larger fixed bundle you currently use and calculate savings from the whole resource mix. - For always-on workloads, convert the hourly rate into a full-month estimate because v5 does not have a monthly usage cap. - Check regional availability and DOKS plan support before designing a migration; the first v5 rollout is not global. - Treat the 30% performance figure as an upper vendor claim and benchmark application throughput, latency and noisy-neighbor sensitivity on the exact Shared or General Purpose configuration you plan to deploy. ## What to watch - Expansion of v5 into additional DigitalOcean regions. - Whether v5 becomes the default generation for new Droplets or coexists long-term with fixed older plans. - Independent benchmarks across web servers, databases and build workloads rather than synthetic CPU-only tests. - How the uncapped hourly billing compares with older capped plans for continuously running production services. - Whether DigitalOcean extends the same independent sizing model more broadly across Kubernetes and managed platform products. ## Uncertainties - The up-to-30% per-core improvement is a DigitalOcean claim and will vary by workload. - DigitalOcean’s public release material does not imply every arbitrary CPU/RAM/storage combination is available; builders still choose from the supported v5 configuration catalog. - The economic advantage of flexible sizing can be offset for long-running instances by the lack of a monthly usage cap, depending on the selected hourly rate. ## Sources - [DigitalOcean Release Notes — v5 Droplet configurations](https://docs.digitalocean.com/release-notes/) — DigitalOcean · primary/vendor · 2026-08-25T00:00:00+12:00. Primary documentation for v5 availability, processor generation, flexible resource sizing, regions, DOKS support and per-second uncapped billing. - [Now Generally Available: v5 Droplets](https://ideas.digitalocean.com/changelog) — DigitalOcean · primary/vendor · 2026-08-26T00:00:00+12:00. Primary product announcement with the up-to-30% per-core performance claim and GA scope. - [Droplets documentation](https://docs.digitalocean.com/products/droplets/) — DigitalOcean · primary_documentation · 2026-08-25T00:00:00+12:00. Current Droplet product documentation confirming v5 configuration and billing details.