DigitalOcean built its reputation on being the cloud that developers can actually
reason about. Where the hyperscalers expose hundreds of services and a pricing model
that needs a spreadsheet, DigitalOcean exposes a virtual machine called a Droplet at a
predictable monthly rate. If you want to buy DigitalOcean account access,
this page lists four configurations from $25 to $1,050.
Overview: Droplets and the DigitalOcean model
A Droplet is a Linux virtual machine. You choose a size, a region and an image, and
you get a server with a public IP. That is close to the whole mental model, and it is
why DigitalOcean remains popular with developers, agencies and small teams who want
infrastructure without a platform-engineering function.
The configurations below are denominated in Droplet count, which is the unit that
matters: how many separate servers the account can run. DigitalOcean’s
Droplet documentation
covers sizes and images in detail.
Available DigitalOcean account configurations
The table below is the complete list. Read it as the menu you choose from when you buy DigitalOcean account configurations on this page — each row is priced and specified independently, so nothing is bundled or assumed.
| Configuration | Price |
|---|---|
| DO 3 Droplet | $25 |
| DO 10 Droplet | $30 |
| 10 Droplet Open 25 Port | $550 |
| 25 Droplet Open 25 Port | $1,050 |
Two configurations are straightforward Droplet allocations at $25 and $30. Two are
higher-capacity configurations at $550 and $1,050 that additionally reference port 25.
DO 3 Droplet — $25
Three Droplets. Enough for a small production shape: an application server, a
database server, and one for staging or a worker process.
DO 10 Droplet — $30
Ten Droplets for $5 more than three. If you anticipate needing more than three
servers at any point, this is the better-value entry.
10 Droplet Open 25 Port — $550 and 25 Droplet Open 25 Port — $1,050
These carry the same Droplet counts plus port 25 availability. Port 25 is the
standard TCP port for SMTP between mail servers. Cloud providers block outbound port 25
by default on new accounts as an anti-abuse measure, because it is the port used to
deliver mail directly to other mail servers. An account with it open can run a mail
transfer agent that delivers directly rather than relaying through a third-party
service.
If you operate a mail server, this is the difference between a working configuration
and one that silently fails to deliver. It also carries real responsibility: outbound
mail infrastructure is governed by the provider’s acceptable use policy, and by anti-spam
law in most jurisdictions. Running it well means correct SPF, DKIM and DMARC records,
genuine recipient consent, and working unsubscribe handling. If your need is
transactional email rather than operating your own MTA, a managed service such as
Amazon SES is usually the better
architecture.
Key features
The points below summarise what distinguishes these options for anyone about to buy DigitalOcean account configurations for the first time.
- Four configurations from a 3-Droplet entry to a 25-Droplet allocation.
- Predictable per-Droplet model rather than composite per-service billing.
- Port 25 configurations for accounts that need to run their own mail transfer agent.
- A $25 entry point for small production shapes.
- Standard DigitalOcean tooling — API, CLI and control panel.
DigitalOcean services and tooling
Droplets
The core VM product, available in Basic, General Purpose, CPU-Optimized and
Memory-Optimized families. Basic Droplets use shared CPU and suit workloads that are
mostly idle; dedicated-CPU families suit sustained compute.
Managed Databases
PostgreSQL, MySQL, Redis and MongoDB as managed services with automated backups and
failover. Running a database on a Droplet is cheaper; running it as a managed service is
usually less work and safer.
Spaces and Volumes
Spaces is S3-compatible object storage, which matters because most existing S3 tooling
works against it unchanged. Volumes are block storage that attaches to a Droplet.
App Platform
A platform-as-a-service layer that builds and deploys from a Git repository without
your managing servers. Suited to standard web applications where operating a Droplet is
overhead you do not want.
Kubernetes
DigitalOcean Kubernetes provides a managed control plane with Droplets as worker
nodes, at a lower complexity than the hyperscaler equivalents.
Who should buy DigitalOcean account configurations
- Solo developers and small projects — DO 3 Droplet ($25).
- Agencies running several client sites — DO 10 Droplet ($30).
- Teams operating their own mail infrastructure — 10 Droplet Open 25 Port ($550).
- Larger multi-server estates with mail requirements — 25 Droplet Open 25 Port ($1,050).
Common use cases
Web application hosting
The classic shape: a Droplet running the application, another running the database,
and a load balancer if traffic warrants it. Predictable cost and full root access make
this straightforward to operate.
Agency and client hosting
Running multiple client sites on separate Droplets gives isolation without the
overhead of separate accounts. The 10-Droplet configuration at $30 is well matched to
this.
Development and staging environments
Spinning up environments that mirror production, then destroying them. Because
Droplets are billed by the hour up to a monthly cap, short-lived environments are cheap.
CI runners and background workers
Self-hosted build runners or queue workers on dedicated Droplets, avoiding the
per-minute pricing of hosted CI at volume.
Container workloads
Docker on a Droplet for simple cases, or DigitalOcean Kubernetes where orchestration
is genuinely needed.
Choosing the right configuration
Start with the honest Droplet count. Three is enough for a single small application
with a separate database and one spare. Beyond that the 10-Droplet configuration is only
$5 more, so the 3-Droplet option really only makes sense if you are certain three is
sufficient.
The port 25 configurations are a different decision entirely. They cost substantially
more and exist for a specific technical need — running your own outbound mail
server. If you are not doing that, the standard configurations are the right choice and
the extra spend buys you nothing.
Technical considerations
Regions
DigitalOcean operates datacentres across North America, Europe and Asia. Not every
product is available in every region, and Droplets cannot be moved between regions
directly — migration means snapshot and recreate. Choose deliberately.
Backups and snapshots
Automated backups are an opt-in paid feature; snapshots are manual. Neither is enabled
by default, which surprises people at exactly the wrong moment. Turn one of them on
before you have data worth losing.
Networking and firewalls
Cloud Firewalls apply rules at the network edge rather than on the Droplet. VPC
networking keeps inter-Droplet traffic private. Both are free and worth configuring from
the start.
Security basics
Use SSH keys rather than passwords, keep the OS patched, and avoid exposing databases
to the public internet. DigitalOcean’s
Droplet how-to guides
cover the standard hardening steps.
Sizing Droplets and planning capacity
The configurations state how many Droplets an account can run, not how large each one
is. Sizing is the decision that actually determines performance and cost, so it is worth
covering properly.
Shared versus dedicated CPU
Basic Droplets share physical CPU with other tenants. For workloads that are mostly
waiting — a small web application, a staging environment, a low-traffic API —
this is entirely adequate and considerably cheaper. For anything that holds the CPU busy
continuously, such as video encoding, sustained builds or a busy database, contention on
shared CPU produces inconsistent latency. Dedicated-CPU families exist precisely for
that case.
Memory as the usual first constraint
In practice teams run out of RAM before they run out of CPU. Databases cache working
sets in memory, and application runtimes hold objects there. A Droplet that starts
swapping to disk degrades sharply rather than gracefully, so it is generally better to
size memory with headroom and accept fewer, larger Droplets than to spread a workload
thinly across many small ones.
How many Droplets a shape actually needs
A single small application with a database and a staging copy fits comfortably in
three. Add a background worker, a cache and a separate staging database and you are at
six. Add per-client isolation for an agency and the count climbs quickly. This is the
reasoning behind the 10-Droplet configuration being the more common practical choice.
Operating a DigitalOcean estate
Backups, snapshots and recovery
Automated backups run on a schedule and cost a percentage of the Droplet price.
Snapshots are manual point-in-time images, useful before a risky upgrade. Neither is on
by default. The important distinction is that a backup protects against failure while a
snapshot protects against your own change — you want both habits, not one.
Worth testing restores occasionally. A backup that has never been restored is an
assumption, not a recovery plan.
Monitoring and alerting
DigitalOcean Monitoring provides CPU, memory, disk and bandwidth metrics with alert
policies, at no additional cost. Configuring alerts on disk utilisation in particular
prevents the single most common avoidable outage: a full disk on a server nobody was
watching.
Scaling patterns
Vertical scaling — resizing a Droplet to a larger plan — is simple and
requires a reboot. CPU and memory resizes can be reversed; disk resizes generally cannot
be reduced afterwards, so grow deliberately.
Horizontal scaling puts several Droplets behind a load balancer. This requires the
application to be stateless, with sessions in a shared store rather than local memory,
and uploads in Spaces rather than on local disk. Designing for that from the start costs
little; retrofitting it under load costs a great deal.
Automation
The DigitalOcean API and doctl CLI cover the full resource surface, and
there is a maintained Terraform provider. Once an estate exceeds a handful of Droplets,
defining infrastructure as code stops being an indulgence and starts being how you avoid
configuration drift between servers.
Cost thinking on a Droplet-based estate
DigitalOcean’s appeal is predictability: a Droplet has a monthly cap, so the bill does
not surprise you the way consumption-based pricing can. A few line items still sit
outside that cap and are worth knowing.
- Bandwidth beyond the included allowance. Each Droplet includes a monthly transfer allowance, pooled across the account. Media-heavy sites can exceed it.
- Block storage volumes, billed per gigabyte separately from the Droplet.
- Snapshots and backups, billed by stored size.
- Load balancers and managed databases, each with their own monthly rate.
- Reserved IPs that are allocated but not attached to a running Droplet.
Destroying a Droplet stops its billing; powering it off does not, because the
underlying resources stay reserved. That distinction catches people out regularly.
Getting started with a new DigitalOcean account
A sensible first-hour sequence on a fresh account:
- Add an SSH key and disable password authentication. Password logins on a public IP attract automated attacks within minutes.
- Create a VPC and place Droplets inside it so internal traffic never crosses the public internet.
- Configure a Cloud Firewall allowing only the ports you actually serve — typically 22 from your address, plus 80 and 443.
- Enable backups or set a snapshot routine before there is data worth losing.
- Set up monitoring alerts on CPU, memory and especially disk utilisation.
- Enable automatic security updates on the operating system.
- Create a non-root user with sudo access and stop using root for routine work.
Choosing an image
DigitalOcean offers plain distribution images alongside one-click applications that
arrive preconfigured — Docker, WordPress, LAMP and similar. The one-click images
save setup time and are a reasonable starting point, though for anything long-lived a
plain distribution plus your own provisioning script is easier to reproduce and to
audit.
Mistakes that cause the most trouble
Exposing a database to the public internet because it was quicker than configuring
private networking, leaving no backups configured, and running everything as root are
the three that account for most avoidable incidents. None takes long to prevent.
When DigitalOcean is the wrong choice
Being honest about fit matters. If a workload needs a deep managed-service catalogue,
fine-grained IAM across many teams, or specific accelerator hardware, a hyperscaler is
the better answer — see AWS,
Google Cloud or
Azure. DigitalOcean’s strength is that it does
a smaller number of things with much less ceremony, and that is exactly what makes it
the right tool for a large share of ordinary web workloads.
Documentation
The DigitalOcean product documentation
covers every product, and its community tutorials are among the better Linux and
server-administration references available anywhere, regardless of which provider you
end up using.
Important considerations
Droplet count is not capacity. The configurations state how many
Droplets, not what size each may be. Sizing, and therefore performance, is a separate
question — confirm anything your project depends on before ordering.
Port 25 carries obligations. Running outbound mail means complying
with DigitalOcean’s acceptable use policy and applicable anti-spam law, maintaining
correct DNS authentication records, and honouring unsubscribe requests. It is not a
shortcut around sending reputation — deliverability still depends entirely on
sending practice.
Provider terms apply. See DigitalOcean’s
Terms of Service
and Acceptable Use Policy.
Prices are per configuration, exactly as shown.
Frequently asked questions
Which configuration should I choose?
Match the configuration to the workload rather than to the price. Most people who buy DigitalOcean account configurations start from the smallest option that covers their current need and move up once real usage is measured, which avoids paying for headroom that never gets used. The comparison sections above set out the trade-offs; the FAQ page covers ordering questions.
Is it safe to buy DigitalOcean account configurations listed here?
Every configuration on this page states its specification and price exactly as supplied, and nothing is implied beyond what is written. Anything your project depends on that is not named should be confirmed on the contact page before you buy DigitalOcean account configurations.
What exactly is a Droplet?
A Linux virtual machine with a public IP, root access and a predictable monthly rate.
It is DigitalOcean’s core compute product.
Why is 10 Droplets only $5 more than 3?
That is how the two configurations are priced — $25 and $30 respectively. If
you expect to need more than three servers, the 10-Droplet option is the more sensible
starting point.
What does “Open 25 Port” mean?
Port 25 is the SMTP port used for server-to-server mail delivery. Providers block it
by default to limit abuse. These configurations reference it being available, which
matters only if you intend to run your own mail transfer agent.
Do I need a port 25 configuration to send email?
No. Most applications send through a managed API or relay on a different port, which
does not require port 25 at all. See Buy
Amazon SES Account for that approach.
How does DigitalOcean compare to Linode or Hetzner?
All three occupy similar developer-focused territory. See
Buy Linode Account and
Buy Hetzner Account to compare the
configurations available here.
Can I run Kubernetes?
Yes — DigitalOcean Kubernetes provides a managed control plane with Droplets as
worker nodes.
How many Droplets will I actually need?
A single application with a separate database and one staging server fits in three.
Adding a worker process, a cache and a staging database takes you to about six. Agencies
hosting separate client sites climb past ten quickly. Because the 10-Droplet
configuration is only $5 more than the 3-Droplet one, three is worth choosing only when
you are confident it is enough.
Can I resize a Droplet later?
Yes. CPU and memory resizes are reversible; disk expansion generally is not, so grow
storage deliberately rather than optimistically.
What is the difference between backups and snapshots?
Backups run automatically on a schedule and are a paid add-on. Snapshots are manual
images you take at a point in time. Backups protect against failure; snapshots protect
against your own changes. Neither is enabled by default.
Is DigitalOcean suitable for production workloads?
For a large share of ordinary web applications, yes. Where it becomes the wrong tool
is when you need a deep managed-service catalogue, fine-grained multi-team IAM, or
specific accelerator hardware — at that point a hyperscaler is genuinely the
better fit rather than merely the bigger one.
Does an Open 25 Port configuration guarantee my email will be delivered?
No, and it is important to be clear about this. Port 25 availability is a network
condition, not a deliverability outcome. Whether mail reaches inboxes depends on sending
reputation, correct SPF, DKIM and DMARC records, list hygiene and recipient engagement.
No configuration on this page changes any of that.
Can I run Docker or Kubernetes?
Both. Docker runs on any Droplet, and DigitalOcean Kubernetes provides a managed
control plane with Droplets as worker nodes for cases where orchestration is genuinely
warranted.
How does billing work if I destroy a Droplet mid-month?
Droplets bill hourly up to a monthly cap, so destroying one stops its charges.
Powering a Droplet off does not stop billing, because the underlying resources remain
allocated to you.
How do I order?
Select the configuration above, add it to the cart, and complete checkout. Payment is
handled by the cryptocurrency gateway configured on this site.
Where to buy DigitalOcean account configurations
Everything needed to buy DigitalOcean account configurations is on this page — the full list of 4 options, the price of each, and the specification each one carries.
Every configuration described above can be ordered directly from this page. Select the one you need in the selector at the top, add it to the cart and complete checkout — there are 4 configurations listed, $25.00 – $1,050.00. Checkout collects only a name and an email address, and payment runs through the cryptocurrency gateway configured on this site.
If you are unsure which option fits, describe the workload on the contact page before ordering rather than after — it is usually possible to narrow the list quickly. Common questions are collected on the FAQ page.
What you get when you buy DigitalOcean account
Every listing on this page is a specific, named configuration rather than an open-ended arrangement. When you buy DigitalOcean account here you are choosing one of the 4 configurations described above, at the stated price $25.00 – $1,050.00, with the specification exactly as written.
- The exact configuration named in the selector, with no substitutions.
- The price shown, with no added fees at checkout.
- A checkout that asks only for a name and an email address.
- Direct contact before ordering if you are unsure which option fits.
If you are comparing providers rather than configurations, the Cloud Accounts and Cloud Infrastructure categories list the alternatives side by side. If you already know what you need, you can buy DigitalOcean account configurations directly from the selector at the top of this page.
Related products
Compare with Linode,
Hetzner,
OVHcloud and
UpCloud in the
Cloud Infrastructure category.
For larger platform workloads see Buy AWS Account.
Reviews
There are no reviews yet.