DigitalOcean Basic 2 GiB / 2 vCPU: Per-Second, Same Price

Plan details (official data)

Inclusions and features (official data)

• Flat monthly price (no intro discount)

Prices were checked on DigitalOcean's official pricing page on Oct 1, 2026. The renewal price listed there is the same as the sign-up price (no intro discount). Prices change, so confirm on the official site before you buy.

Compare plans in this category (official data)

Swipe the table to see more →

All values in this table come from each host's official pricing page. This plan was checked on Oct 1, 2026; every compared plan was checked within the last 60 days.

What the official data lists for this plan

The pricing page lists four resources for DigitalOcean Basic 2 GiB / 2 vCPU: 2 vCPU, 2 GiB of RAM, 60 GiB SSD storage and 3,000 GiB of bandwidth. The plan sits in the Cloud VPS category and is a self-managed server, which means the operating system, web server, PHP, database and WordPress itself are installed and maintained by the person who rents it.

The only listed feature is Flat monthly price (no intro discount). Nothing in the data describes a control panel, operating system images, a snapshot or backup add-on, data center locations, support channels or a WordPress installer, so anyone who depends on those should confirm them on the provider's site before paying. SSH access is the normal way to work on a self-managed server, and the practical steps on this page assume it.

How per-second billing works on this plan

Billing is listed as USD per month; billed per second up to the monthly price (capped at 672 hours a month). In practice, charges build up second by second while the server exists and stop climbing once they reach the monthly price shown in the table. The term of 1 month is the billing cycle for that cap, not a commitment to keep the server for that long.

The feature list says Flat monthly price, but the billing field describes how the charge is actually calculated, so the monthly figure is a ceiling rather than an identical charge every month. A server that exists for a full month reaches the cap; one that is destroyed partway through accrues less. The data does not say which actions, such as powering a server off, reduce or stop charges, so that should be confirmed with DigitalOcean rather than assumed.

Because there is no intro discount, the renewal price in the table is the same as the first-month price. There is no promotional rate that ends later, which keeps the arithmetic simple for anyone comparing this plan with shared hosting offers that are structured around a discounted first period.

What changes when you move WordPress off shared hosting

On shared hosting, the host keeps the server patched, runs the web server and PHP, usually takes backups and gives you a control panel for email, databases and SSL. On a self-managed Cloud VPS, every one of those tasks moves to you or to tools you set up yourself. The plan gives you a blank server with 2 vCPU, 2 GiB of RAM and 60 GiB SSD; the stack that runs WordPress on top of it is your responsibility.

The usual path is to install a web server such as Nginx or Apache, PHP, and MySQL or MariaDB, then copy the WordPress files and import the database from the old host. Email hosting is also something to plan for, since a fresh server does not come with mailboxes and the data does not mention any email service; many site owners keep email with a separate provider rather than running a mail server themselves.

The upside is control: you choose PHP versions, caching layers and server tuning instead of accepting what a shared plan allows. The trade-off is that mistakes are yours to fix, so a WordPress owner making this move should set aside time to learn basic Linux administration or budget for someone who already has it.

Security updates, a firewall and backups you now own

Security updates on a self-managed server are not automatic unless you make them so. Most Linux distributions offer an unattended-upgrades style package that installs security patches on a schedule; turning that on early is one of the simplest ways to reduce risk. WordPress core, themes and plugins still need their own updates, exactly as they did on shared hosting.

A firewall is the second item. Allow SSH, HTTP and HTTPS and block everything else by default, and consider key-based SSH login rather than passwords. None of this is provided by the plan; it is standard server work that applies to any provider.

Backups are where shared hosting habits cause the most trouble, because people assume someone else is taking them. The data for this plan does not list an included backup or snapshot feature, so plan for your own. A WordPress backup needs both the files and the database; if WP-CLI is installed on the server, the database can be exported to your home folder, outside the public web folder, with this command, replacing the path if you prefer another location: wp db export ~/backup.sql. Copy backups off the server to separate storage, and test a restore at least once so you know the procedure works before you need it.

Who this plan suits

This plan fits a WordPress owner who has outgrown shared hosting, is comfortable with or willing to learn the command line, and wants a server where charges accrue per second up to a monthly cap with no intro discount to track. The 2 vCPU and 2 GiB of RAM are the listed resources; the data contains no benchmarks or traffic figures, so whether that is enough depends on your theme, plugins, caching and visitor load, and it is reasonable to start here and resize later if DigitalOcean allows it.

It suits less well anyone who wants the host to handle patches, backups and a control panel, or who expects a WordPress installer, since none of those are listed. For that reader, a managed WordPress host or a managed add-on from another provider may be a better match than a bare Cloud VPS.

What to check before signing up

Read the price table on this page for the monthly price that acts as the cap, and confirm with DigitalOcean how partial months, powered-off servers and extra services such as snapshots or additional storage are charged, because the data covers only the base plan. Check the bandwidth figure of 3,000 GiB against your current usage statistics from the shared host.

Confirm which operating systems are offered, which data center regions are available and how support works, since none of these appear in the official data. If you need IPv6, a floating IP or a managed database later, verify availability and cost before you migrate rather than after.

How it compares with the listed alternatives

DigitalOcean Basic 2 GiB, from the same provider, is listed with 1 vCPU, 2 GiB of RAM, 50 GiB SSD and 2,000 GiB of bandwidth, and uses the same per-second billing up to a monthly price capped at 672 hours a month. Within DigitalOcean's own units it offers less CPU, less storage and less bandwidth than the 2 vCPU plan, so it fits a smaller or lower-traffic WordPress site, while the 2 vCPU option gives more headroom for plugin-heavy sites or background tasks.

The three Vultr plans are billed hourly up to the monthly price and also carry a flat monthly price with no intro discount. Vultr High Frequency 2 GB / 2 vCPU lists 2 vCPU, 2 GB of RAM, 80 GB NVMe SSD and 3 TB of bandwidth with the feature High Frequency (3GHz+ Intel Xeon, NVMe SSD). Vultr High Performance AMD 2 GB / 2 vCPU lists 2 vCPU, 2 GB of RAM, 60 GB NVMe SSD and 4 TB of bandwidth with the feature High Performance (AMD EPYC, NVMe SSD). Vultr Cloud Compute 4 GB / 2 vCPU lists 2 vCPU, 4 GB of RAM, 80 GB SSD and 3 TB of bandwidth with the feature Regular Performance (previous-gen Intel, regular SSD).

The Vultr figures are published in GB and TB while DigitalOcean uses GiB, so the storage and bandwidth numbers are not directly comparable here and should be checked on each provider's site in matching units. In broad terms, a WordPress owner who wants more memory would look at the Vultr Cloud Compute 4 GB plan, someone who values the listed NVMe SSD and newer processor descriptions would look at the two Vultr High Frequency and High Performance plans, and someone who prefers per-second rather than hourly accrual, or who already uses DigitalOcean, would stay with the plan on this page. The data does not include speed or uptime measurements for any of them.