For AI agents: The documentation index is at https://docs.digitalocean.com/llms.txt. Markdown versions of pages use the same URL with index.html.md in place of the HTML page (for example, append index.html.md to the directory path instead of opening the HTML document).

Build your application the way you want with our suite of compute products including VMs, managed containers, PaaS, and serverless functions.

Droplets

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 the right resources (like CPU, RAM, and storage) for your workload.

DigitalOcean Kubernetes

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

App Platform is a fully managed Platform-as-a-Service (PaaS) that deploys applications from Git repositories or container images. It automatically builds, deploys, and scales components while handling all underlying infrastructure.

Functions

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.

DigitalOcean MicroVMs

Lightweight virtual machines that run a container image in its own kernel, pause when idle, and resume on the next request with memory and processes intact.

Cloudways

Cloudways is a managed cloud hosting platform where teams can build, deploy, and scale web applications.

Latest Updates

Upcoming Changes

• App Platform’s XL build resources (8 CPUs and 20 GiB of memory during builds) are now enabled for all apps by default. The xl-build flag is now deprecated and will be removed in a future release. Remove xl-build from your app spec to avoid potential errors once the flag is fully retired.

9 October 2026

• DigitalOcean MicroVMs are available in public preview in MKC1. MicroVMs are lightweight virtual machines that run a container image in its own kernel, pause automatically when idle, and resume on the next request with memory, files, and processes intact. You can checkpoint a MicroVM to start new MicroVMs from a warmed-up state, and run commands or open a console in it with doctl or the API. For more information, see DigitalOcean MicroVMs.

8 October 2026

• Starting with DOKS 1.37, GPU device plugins are no longer enabled by default on clusters with GPU nodes. Dynamic Resource Allocation (DRA) drivers are available as opt-in cluster plugins (nvidia_gpu_dra_driver or amd_gpu_dra_driver). Device plugins (nvidia_gpu_device_plugin or amd_gpu_device_plugin) remain available but must be enabled explicitly. Device plugins and DRA drivers are mutually exclusive. When you switch between them on an existing cluster, DOKS replaces the GPU worker nodes so each node starts with a clean state. For more information, see Supported GPUs.

• When you upgrade an existing DigitalOcean Kubernetes (DOKS) cluster to version 1.37 or later, DOKS automatically enables the CoreDNS Cluster Proportional Autoscaler (CPA) plugin if CoreDNS is still running the default of two replicas. If you have manually changed the CoreDNS replica count, DOKS leaves it as is, and you can enable CPA yourself. CPA is already enabled by default on new clusters running Kubernetes 1.36 or later. For more information, see How to Configure CoreDNS Autoscaling.

29 September 2026

• Isolated Worker Nodes for DigitalOcean Kubernetes (DOKS) are now in general availability. Every worker node in an isolated cluster runs without a public IPv4 address, so nodes are removed from the public internet at the network level rather than only protected by a firewall.

  Outbound traffic, including node provisioning and container image pulls, routes through a VPC NAT Gateway, and other resources in the same VPC reach the nodes over private addresses. The Kubernetes API server stays publicly reachable so you can still manage the cluster. You can enable isolation only when you create a cluster running Kubernetes 1.36 or later.

For more information, see the full release notes.