DigitalOcean droplets explained: plans, limits and what the account controls

DigitalOcean built its reputation on removing decisions. There is one compute product, DigitalOcean droplets, with a short list of plans, and a control panel you can learn in an afternoon. That simplicity is real, and it hides two account level settings that matter more than any plan choice.

The DigitalOcean droplets plan families

Basic. Shared CPU. The entry tier, available in regular and premium variants, where premium means newer processors and NVMe storage for a small increase. Correct for web servers, small APIs, staging environments and anything without sustained CPU load.

General Purpose. Dedicated CPU with a balanced memory ratio. The first step up when a shared core stops being predictable.

CPU-Optimized. Dedicated CPU with less memory per core. Build servers, encoding, batch work.

Memory-Optimized. Dedicated CPU with a much higher memory ratio. Databases and caches.

Storage-Optimized. Large local NVMe attached. For datasets that need to sit next to the compute.

The shared versus dedicated distinction is the one that catches people. Basic droplets are excellent value and entirely adequate until the workload has a sustained CPU floor, at which point contention shows up as latency variance rather than as an obvious limit.

The droplet limit

Every account has a cap on how many droplets it may run at once. New accounts start low. It exists for abuse prevention rather than capacity reasons, and it is raised on request once an account has a payment history.

This matters if you are planning a fleet, a Kubernetes cluster with several node pools, or an environment per developer. The limit is on the account, so it applies across every region and every project inside it.

It is also why account listings quote a droplet number. That figure is the account’s current limit, which is the practical ceiling on what you can build without filing a request and waiting.

Outbound SMTP

DigitalOcean restricts outbound SMTP on new accounts. Ports 25, 465 and 587 are blocked until the account is established and access is granted on request. This is standard practice across providers and exists because cheap cloud IP space is otherwise a spam engine.

The practical consequence: if your application sends mail directly rather than through an API based provider, you need this lifted before the application works. It is an account property, which is why listings distinguish between accounts with the restriction in place and accounts where port 25 is open.

The policy across providers, and the alternatives to running your own SMTP path, are covered in outbound port 25 on cloud servers.

Bandwidth is pooled

Each droplet adds a transfer allowance to an account wide pool, and outbound traffic is charged only on what exceeds the total. Inbound is free. A fleet of mostly idle droplets therefore builds headroom for the one that is busy, which is a friendlier model than per instance metering.

Traffic between droplets on the same VPC network does not count against the pool, so keeping internal service traffic on private addresses is worth the small amount of configuration it takes.

What else is in the account

• Spaces. S3 compatible object storage with a bundled CDN, priced as a base subscription plus overage.
• Volumes. Block storage you attach to droplets, billed per gigabyte month.
• Managed Databases. PostgreSQL, MySQL, Redis compatible caching, MongoDB and Kafka, with backups and failover handled.
• App Platform. A managed deployment layer for containers and static sites.
• Load Balancers and Reserved IPs. Both billed separately, and a reserved IP left unattached still costs.
• Snapshots and backups. Backups are a percentage surcharge on the droplet; snapshots are billed per gigabyte and persist until deleted.

Where DigitalOcean fits

It suits teams who want a predictable monthly figure, a small surface area to learn, and documentation written for people rather than for compliance officers. It is a poor fit if you need a deep managed service catalogue, unusual regions or specialised hardware.

The natural comparisons are with Linode, which occupies almost the same position, and with Hetzner, which is cheaper again with a different regional footprint. Both are covered in DigitalOcean vs Linode and Hetzner vs DigitalOcean.