DigitalOcean
Cloud infrastructure provider offering Linux virtual machines, managed databases, object storage and an app platform across global datacenter regions.
- vps cloud
- Not documented
- $4.00
- NYC1, NYC2, NYC3 (New York City, United States); AMS3 (Amsterdam, the Netherlands); SFO2, SFO3 (San Francisco, United States); SGP1 (Singapore); LON1 (London, United Kingdom); FRA1 (Frankfurt, Germany); TOR1 (Toronto, Canada); BLR1 (Bangalore, India); SYD1 (Sydney, Australia); ATL1 (Atlanta, United States); RIC1 (Richmond, United States); MKC1 (Kansas City, United States); MEM1 (Memphis, United States)
Who it suits.
Teams that want plain Linux virtual machines with predictable per-second billing from $4 a month, and the option of managed databases beside them. App Platform adds Git and Docker deploys on top.
Consider something else if…
You want a platform that manages the runtime for you rather than a server you administer.
Editorial · Palash Bagchi · approved
What the documentation says.
Each value below links to the page it was read from, with the sentence it came from. Criteria DigitalOcean does not publish are not listed.
Pricing
Entry paid plan
$4.00
Sources (1) →Sources ↓
- Droplet Pricing | DigitalOcean ↗
“512 MiB / 1 vCPU / 500 GiB transfer / 10 GiB SSD — $0.00595 /hr, $4.00 /mo”
Read 2026-09-05 · official pricing
Pricing model
billed per second with a minimum charge of 60 seconds or $0.01, whichever is higher
Sources (1) →Sources ↓
- Droplet Pricing | DigitalOcean Documentation ↗
“billed per second with a minimum charge of 60 seconds or $0.01, whichever is higher”
Read 2026-09-05 · official docs
Egress over allowance
$0.01 per GiB (Droplets); $0.02 per GiB (App Platform)
Sources (1) →Sources ↓
- Bandwidth Billing | DigitalOcean Documentation ↗
“Droplets: Additional outbound transfer is billed at $0.01 per GiB. App Platform: Additional outbound transfer is billed at $0.02 per GiB.”
Read 2026-09-05 · official pricing
When you exceed a cap
Billed automatically — outbound transfer beyond the pooled plan allowance is charged at $0.01 per GiB; inbound transfer is free
Sources (1) →Sources ↓
- Droplet Pricing | DigitalOcean Documentation ↗
“Each Droplet plan includes an amount of free outbound data transfer. Additional outbound transfer is billed at $0.01 per GiB. Inbound transfer to Droplets is free.”
Read 2026-09-05 · official docs
Limits
Storage (entry plan)
10 GiB SSD on the cheapest Basic Droplet (Regular CPU, 512 MiB / 1 vCPU, $4.00/mo, size slug s-1vcpu-512mb-10gb)
Sources (1) →Sources ↓
- Droplet Pricing | DigitalOcean ↗
“Memory | vCPU | Transfer | SSD | $/hr | $/mo — 512 MiB | 1 vCPU | 500 GiB | 10 GiB | $0.00595 | $4.00”
Read 2026-09-05 · official pricing
Memory (entry plan)
512 MiB on the cheapest Basic Droplet (Regular CPU, 1 vCPU, $4.00/mo, size slug s-1vcpu-512mb-10gb)
Sources (1) →Sources ↓
- Droplet Pricing | DigitalOcean ↗
“Memory | vCPU | Transfer | SSD | $/hr | $/mo — 512 MiB | 1 vCPU | 500 GiB | 10 GiB | $0.00595 | $4.00”
Read 2026-09-05 · official pricing
Sites or apps included
No more than 10 Droplets can be created at the same time through the Control Panel or the API
Sources (1) →Sources ↓
- Droplet Limits | DigitalOcean Documentation ↗
“You can’t create more than 10 Droplets at the same time using the Control Panel or the API.”
Read 2026-09-05 · official docs
Included bandwidth
500 GiB of included outbound transfer on the cheapest Basic Droplet ($4.00/mo, s-1vcpu-512mb-10gb); this is an included allowance, not a hard cap — see overage_behaviour
Sources (1) →Sources ↓
- Droplet Pricing | DigitalOcean ↗
“Memory | vCPU | Transfer | SSD | $/hr | $/mo — 512 MiB | 1 vCPU | 500 GiB | 10 GiB | $0.00595 | $4.00”
Read 2026-09-05 · official pricing
File or inode limit
Up to 5000 Block Storage volumes per account
Sources (1) →Sources ↓
- Volume Limits | DigitalOcean Documentation ↗
“You can create up to 5000 volumes per account. If your workload requires more volumes, contact support.”
Read 2026-09-05 · official docs
Max request duration
The maximum timeout is 15 minutes. This includes initialization and function execution.
Sources (1) →Sources ↓
- Functions Limits | DigitalOcean Documentation ↗
“The maximum timeout is 15 minutes. This includes initialization and function execution.”
Read 2026-09-05 · official docs
Execution
Managed connection pooling
Supported
Sources (1) →Sources ↓
- How to Manage Connection Pools for PostgreSQL Database Clusters ↗
“DigitalOcean's PostgreSQL database clusters use PgBouncer for connection pooling. Clusters provide 25 connections per 1 GiB of RAM. 3 connections per cluster are reserved for maintenance, and all remaining connections can be allocated to connection pools.”
Read 2026-09-05 · official docs
Deployment
Git deployment
Supported
Sources (1) →Sources ↓
- App Platform | DigitalOcean Documentation ↗
“App Platform is a fully managed Platform-as-a-Service (PaaS) that deploys applications from Git repositories or container images.”
Read 2026-09-05 · official docs
Docker deployment
Supported
Sources (1) →Sources ↓
- How to Deploy from Container Images | DigitalOcean Documentation ↗
“App Platform currently supports deploying public and private images from DigitalOcean Container Registry, Docker Hub, and GitHub Container Registry.”
Read 2026-09-05 · official docs
Containers
Supported
Sources (1) →Sources ↓
- How to Deploy from Container Images | DigitalOcean Documentation ↗
“Web services, workers, and jobs run in containers from a repository or container image.”
Read 2026-09-05 · official docs
Scheduled jobs
Supported
Sources (1) →Sources ↓
- How to Schedule Functions | DigitalOcean Documentation ↗
“To run functions on a schedule, you can create a function trigger and then specify a schedule using standard cron syntax.”
Read 2026-09-05 · official docs
Infrastructure
Persistent processes
Supported
Sources (1) →Sources ↓
- Droplets | DigitalOcean Documentation ↗
“DigitalOcean Droplets are Linux-based virtual machines (VMs) that run on top of virtualized hardware.”
Read 2026-09-05 · official docs
Persistent storage
Supported
Sources (1) →Sources ↓
- Volumes Block Storage Features | DigitalOcean Documentation ↗
“Volumes are network-attached block storage. You can use them with Droplets or Kubernetes clusters, move or resize them, and create snapshots at any time. When attached to a Droplet, Volumes function like local block devices.”
Read 2026-09-05 · official docs
Managed databases
Supported
Sources (1) →Sources ↓
- Managed Databases | DigitalOcean Documentation ↗
“DigitalOcean Managed Databases are a fully managed, high performance database cluster service.”
Read 2026-09-05 · official docs
Edge network
Limited
Sources (1) →Sources ↓
- Spaces Features | DigitalOcean Documentation ↗
“Spaces includes an optional built-in CDN, a globally distributed network of edge servers that cache and deliver content from locations closest to your users.”
Read 2026-09-05 · official docs
Autoscaling
Supported
Sources (1) →Sources ↓
- How to Scale Apps | DigitalOcean Documentation ↗
“Autoscaling automatically adds or removes containers based on workload. [...] Request-based autoscaling monitors HTTP traffic metrics, such as requests per second or P95 request duration, and works with both shared and dedicated CPU plans.”
Read 2026-09-05 · official docs
Regions
NYC1, NYC2, NYC3 (New York City, United States); AMS3 (Amsterdam, the Netherlands); SFO2, SFO3 (San Francisco, United States); SGP1 (Singapore); LON1 (London, United Kingdom); FRA1 (Frankfurt, Germany); TOR1 (Toronto, Canada); BLR1 (Bangalore, India); SYD1 (Sydney, Australia); ATL1 (Atlanta, United States); RIC1 (Richmond, United States); MKC1 (Kansas City, United States); MEM1 (Memphis, United States)
Sources (1) →Sources ↓
- Regional Availability | DigitalOcean Documentation ↗
“NYC1 New York City, United States nyc1 / NYC2 New York City, United States nyc2 / NYC3 New York City, United States nyc3 / AMS3 Amsterdam, the Netherlands ams3 / SFO2 San Francisco, United States sfo2 / SFO3 San Francisco, United States sfo3 / SGP1 Singapore sgp1 / LON1 London, United Kingdom lon1 / FRA1 Frankfurt, Germany fra1 / TOR1 Toronto, Canada tor1 / BLR1 Bangalore, India blr1 / SYD1 Sydney, Australia syd1 / ATL1 Atlanta, United States atl1 / RIC1 Richmond, United States ric1 / MKC1 Kansas City, United States mkc1 / MEM1 Memphis, United States mem1”
Read 2026-09-05 · official docs