DigitalOcean Droplets are Linux-based virtual machines (VMs). Each Droplet you create is a new server you can use. Choose from a variety of Droplet plans to get right resources (like CPU, RAM, and storage) for your workload.
Compute
Validated on 24 Jan 2025 • Last edited on 31 Jan 2025
Build your application the way you want with our suite of compute products including VMs, managed containers, PaaS, and serverless functions.
DigitalOcean Kubernetes (DOKS) is a managed Kubernetes service that lets you deploy Kubernetes clusters without the complexities of handling the control plane and containerized infrastructure. Clusters are compatible with standard Kubernetes toolchains and integrate natively with DigitalOcean Load Balancers and volumes.
App Platform is a platform as a service (PaaS) offering that lets you publish code directly to DigitalOcean servers without worrying about the underlying infrastructure, runtimes, or dependencies.
DigitalOcean Functions is a function as a service (FaaS) offering that lets you run your local serverless code in the cloud using Node.js, Python, Go, or PHP without managing any backend infrastructure.
Cloudways is a managed cloud hosting platform where teams can build, deploy, and scale web applications.
Latest Updates
20 June 2025
-
The DOKS Cluster Autoscaler now supports autoscaling across multiple node pools for a single workload. If the preferred node pool is at capacity, the autoscaler uses the next compatible option in sequence — ensuring scaling continues smoothly without disruption. This feature is in private preview. For more information, see Flexible Node Pool Selection.
19 June 2025
-
We have reverted to non-VPC-native cluster networking when creating new clusters with Kubernetes version 1.33 and higher using the
doctl
command line interface or API. If your VPC-native cluster provisioned successfully, no action is needed. If the cluster appears to be stuck in theProvisioning
state, please delete the cluster and create a new one.You can automatically configure VPC-native networking when using the control panel or manually configure it using
doctl
or the API. For more information, see Create a Cluster with VPC-native Networking.
16 June 2025
-
We have enabled VPC-native cluster networking by default when you create new clusters using Kubernetes version 1.33 or higher using the
doctl
command line interface or API. For more information, see Create a Cluster with VPC-native Networking. -
Load balancer services now default to network load balancers (NLB) instead of regional load balancers on clusters running on Kubernetes version 1.33 or higher. Use the
service.beta.kubernetes.io/do-loadbalancer-type
annotation with a value ofREGIONAL
orREGIONAL_NETWORK
to change the load balancer type. -
We have enabled the Gateway API by default on clusters with VPC-native networking running on Kubernetes version 1.33 or higher. This feature is in public preview. You can use the Gateway API to manage ingress natively in a Kubernetes cluster, without the need for third-party ingress controllers.
For more information, see the full release notes.