DigitalOcean MicroVMs Features

Last verified 19 Nov 2026

DigitalOcean MicroVMs are lightweight virtual machines that run a container image in an isolated kernel, pause automatically when idle, and resume on the next request with memory, files, and processes intact.

DigitalOcean MicroVMs are lightweight virtual machines built for workloads that alternate between bursts of work and long idle periods, such as AI agent sessions, sandboxes for untrusted or generated code, and per-user environments. Each MicroVM runs one container image in its own virtual machine with its own kernel, isolated from other workloads.

You choose the image, size, networking, ports, environment variables, and outbound policy when you create a MicroVM. After that, the platform pauses and resumes it with your traffic, and you can checkpoint it, run commands in it, copy files in and out, or destroy it. You manage MicroVMs from the Control Panel, doctl, the API, or an AI assistant through the DigitalOcean MCP server.

Container Images

A MicroVM runs a public container image, such as one from Docker Hub, or a private image from your team’s DigitalOcean Container Registry (DOCR). Images must follow the Open Container Initiative (OCI) image format and be built for linux/amd64. For all image requirements, see MicroVMs Limits.

Auto-Pause and Auto-Resume

A MicroVM pauses after an idle timeout, which defaults to 5 minutes. The next HTTP request, command, console session, or file transfer resumes it, with its memory, files, and running processes intact. You can turn auto-resume off at creation to require a manual resume, and you can pause and resume a MicroVM yourself. A paused MicroVM incurs storage charges only. For details, see MicroVM Lifecycle.

Projects and Tags

Each MicroVM belongs to a project, your team’s default project unless you choose another, and can have tags. You can rename a MicroVM, change its tags and idle timeout, and move it to another project without recreating it. For details, see How to Update a MicroVM.

HTTPS URLs and Access Tokens

Each MicroVM gets its own authenticated HTTPS URL for the HTTP port you choose at creation, serving HTTP or HTTP/2. You can add up to nine more URLs, including URLs for the other ports you declare. For details, see How to Send Requests to a MicroVM.

Requests authenticate with a team API token, or with an access token that reaches only one MicroVM. Access tokens let you share a single MicroVM with a person or service without giving them access to anything else. For details, see How to Create Access Tokens for a MicroVM.

Networking and Outbound Controls

A MicroVM uses public networking with a shared NAT gateway by default, or you can place it in a VPC network in the same region.

With public networking, you can restrict a MicroVM’s outbound traffic to the domains and IP addresses you allow. You can also attach credentials, such as API keys, to allowed hosts. The platform adds them to outbound requests, so code in the MicroVM never holds the secret. For details, see How to Restrict a MicroVM’s Outbound Traffic and MicroVM Networking and Access.

Checkpoints

A checkpoint captures a MicroVM’s memory and disk. You can create new MicroVMs that start from that state, already warmed up. For details, see MicroVM Checkpoints.

Commands, Console, and File Transfer

You can run a single command in a MicroVM’s container with doctl or the API, and open an interactive shell from the Control Panel, doctl, or the API. For details, see How to Run Commands and Open a Console in a MicroVM.

You can also upload and download individual files of up to 64 MiB. For details, see How to Upload and Download Files in a MicroVM.

Monitoring with Insights

MicroVMs send usage and lifecycle metrics to DigitalOcean Insights, and the MicroVM’s Insights tab charts them. You can also choose to store platform logs and traces for each MicroVM’s lifecycle events. For details, see How to Monitor a MicroVM.

MCP Server

The DigitalOcean MCP server includes tools for managing MicroVMs, so AI assistants and agents can create, pause, resume, checkpoint, and destroy MicroVMs, run commands in them, and read and write their files. For the available tools, see MicroVMs MCP Tools. To connect a client to the hosted MicroVMs MCP server, see Configure Remote MCP.

We can't find any results for your search.

Try using different keywords or simplifying your search terms.