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.

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.

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.

10 September 2026

• The DigitalOcean Control Panel now supports adding and removing allow and deny rules based on IP addresses and CIDR ranges when you create or manage regional load balancers that use HTTP or Network traffic management. See How to Create Regional Load Balancers and How to Manage Regional Load Balancers. Global load balancers do not support firewall rules, and DigitalOcean Kubernetes (DOKS)-managed load balancers continue to use Kubernetes service configuration.

9 September 2026

• DigitalOcean Kubernetes (DOKS) now supports Spot GPU node pools in public preview. You can run worker nodes on interruptible Spot GPU capacity for AMD Instinct MI350X and MI355X and NVIDIA B300 GPUs, at a lower, variable rate than on-demand GPU nodes.

  Spot GPU node pools work with the cluster autoscaler, and you can pair them with an on-demand GPU node pool as a configurable fallback. For supported GPU shapes, regions, pricing, and behavior, see Spot GPU node pools.

For more information, see the full release notes.