DigitalOcean Basic 2 GiB: Billed per Second, 50 GiB SSD

We earn commissions when you shop through the links below.

๐Ÿ”„ Last updated: Prices checked Oct 1, 2026

Disclosure: This page contains affiliate links. If you buy or sign up through them, we may earn a commission at no extra cost to you.

DigitalOcean Basic 2 GiB is a Cloud VPS plan from DigitalOcean with 1 vCPU, 2 GiB of RAM, 50 GiB SSD storage and 2,000 GiB of bandwidth. According to the official pricing data, it is charged in USD per month, billed per second up to the monthly price and capped at 672 hours a month, with a flat monthly price and no intro discount. This page is written for a WordPress site owner who is leaving shared hosting and wants to understand what the data confirms about the plan, how the per-second billing works, and what changes once setup, security updates and backups become your own responsibility on a self-managed server.

Plan details (official data)

PlanDigitalOcean Basic 2 GiB
HostDigitalOcean
CategoryCloud VPS
Price (monthly)$12.00
Billing cycle1 month
BillingUSD per month; billed per second up to the monthly price (capped at 672 hours a month)
CPU1 vCPU
RAM2 GiB
Storage50 GiB SSD
Bandwidth2,000 GiB

Inclusions and features (official data)

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)

PlanHostPrice (monthly)Billing cycleBillingCPURAMStorageBandwidth
DigitalOcean Basic 2 GiB (this plan)DigitalOcean$12.001 monthUSD per month; billed per second up to the monthly price (capped at 672 hours a month)1 vCPU2 GiB50 GiB SSD2,000 GiB
DigitalOcean Basic 1 GiBDigitalOcean$6.001 monthUSD per month; billed per second up to the monthly price (capped at 672 hours a month)1 vCPU1 GiB25 GiB SSD1,000 GiB
Vultr Cloud Compute 2 GBVultr$10.001 monthUSD per month; billed hourly up to the monthly price1 vCPU2 GB55 GB SSD2 TB
Vultr High Frequency 2 GBVultr$12.001 monthUSD per month; billed hourly up to the monthly price1 vCPU2 GB64 GB NVMe SSD2 TB
Vultr High Performance AMD 2 GBVultr$12.001 monthUSD per month; billed hourly up to the monthly price1 vCPU2 GB50 GB NVMe SSD3 TB

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 official pricing page lists four resources for DigitalOcean Basic 2 GiB: 1 vCPU, 2 GiB of RAM, 50 GiB SSD storage and 2,000 GiB of bandwidth. The category is Cloud VPS, which means you receive a server rather than a hosting account with a prebuilt WordPress installer, and you decide what runs on it.

The only feature listed is Flat monthly price (no intro discount). The renewal price is listed as the same as the first-term price, so the figure in the price table is the amount that applies now and later, with no introductory rate that gives way to a different one.

The data does not describe a control panel, a preinstalled operating system, a backup feature, server locations, support channels or uptime figures. Treat those as unconfirmed and check them with DigitalOcean before signing up if any of them matters to your decision.

How per-second billing and the monthly cap work

The billing field reads 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 they stop growing once the monthly price in the table is reached. The term of 1 month is the billing cycle of that cap, not a commitment you sign up for in advance.

Because of this, the monthly price is a ceiling rather than a fixed amount deducted on a set day. A server that exists for part of a billing cycle is charged for that part; a server that exists for the full 672 hours is charged the monthly price and no more. The flat monthly price in the features means the ceiling itself does not change, and there is no intro discount that later expires.

The official data does not state what happens to charges when a server is powered off, resized or deleted. Do not assume that switching a server off reduces what you pay; confirm the exact rules with the provider before relying on them.

What changes when you move WordPress from shared hosting to a VPS

On shared hosting, the provider keeps the web server, PHP, the database and the operating system updated, and a control panel such as cPanel handles email, file management and SSL for you. On a self-managed Cloud VPS, none of that happens unless you do it. You choose and install the web server (Nginx or Apache), PHP, MySQL or MariaDB and WordPress itself, then keep each of them patched.

Security updates become a recurring task. Most Linux distributions offer automatic security updates that you enable once; after that, you still need to reboot occasionally and watch for kernel and PHP updates that require attention. WordPress core, themes and plugins also keep updating, and on a VPS the file permissions and database credentials are yours to get right.

Backups are the biggest change for a WordPress owner. Shared hosts often take nightly backups and offer a restore button; the official data for this plan does not list any backup feature, so plan on exporting the database and archiving the files yourself on a schedule and storing copies off the server. If you have WP-CLI installed on the server, a database export to your home folder looks like this: wp db export ~/backup.sql

Email is another gap to plan for. Shared accounts usually include mailboxes; a bare VPS does not, and running a mail server is a separate project. Most WordPress owners point MX records at a third-party email service instead and configure WordPress to send notifications through an SMTP plugin.

Who this plan suits

DigitalOcean Basic 2 GiB suits a WordPress site owner who is comfortable working over SSH, or willing to learn, and who wants a server with 2 GiB of RAM for a site that has outgrown a shared account. The 50 GiB SSD gives room for WordPress, uploads and local backup files, and 2,000 GiB of bandwidth covers a typical content site; whether it covers yours depends on your traffic, which the data cannot judge.

The per-second billing with a monthly cap fits people who want to experiment, for example by building the new server alongside the old shared account and only moving DNS when the site is ready, because the time before the move is charged for the seconds it actually runs.

It is a poorer fit for someone who expects a one-click WordPress installer, a backup button, included email or someone else to apply updates. Nothing in the official data promises those things, and a managed WordPress host is the simpler route if you want them.

How DigitalOcean Basic 2 GiB compares with the alternatives

DigitalOcean Basic 1 GiB is the smaller plan from the same provider with the same billing: USD per month; billed per second up to the monthly price (capped at 672 hours a month), the same term of 1 month, the same Flat monthly price (no intro discount) feature and 1 vCPU. It has 1 GiB of RAM, 25 GiB SSD and 1,000 GiB of bandwidth. For a WordPress site, the RAM is the figure to watch: 1 GiB is tight once PHP, a database and a web server run together, while 2 GiB leaves more room for caching and plugins.

Vultr Cloud Compute 2 GB, Vultr High Frequency 2 GB and Vultr High Performance AMD 2 GB all list 1 vCPU, 2 GB of RAM, a term of 1 month and a flat monthly price (no intro discount). Their billing field reads USD per month; billed hourly up to the monthly price, so charges accumulate by the hour instead of by the second, up to the same kind of monthly ceiling. Storage is listed as 55 GB SSD, 64 GB NVMe SSD and 50 GB NVMe SSD respectively; bandwidth is 2 TB, 2 TB and 3 TB.

The Vultr plans use GB and TB while DigitalOcean lists GiB, so the storage and bandwidth figures are not directly comparable and should not be ranked against each other. What the data does distinguish is hardware description: Vultr Cloud Compute 2 GB is labeled Regular Performance (previous-gen Intel, regular SSD), Vultr High Frequency 2 GB is labeled High Frequency (3GHz+ Intel Xeon, NVMe SSD), and Vultr High Performance AMD 2 GB is labeled High Performance (AMD EPYC, NVMe SSD). DigitalOcean Basic 2 GiB lists no hardware description.

Which fits which situation: if you want billing measured in seconds and are already building on DigitalOcean, the Basic 2 GiB plan matches. If a stated CPU generation or NVMe storage matters to you, the Vultr High Frequency and High Performance AMD plans state those details in their features. If you are unsure that 2 GiB is needed, DigitalOcean Basic 1 GiB is the smaller step from shared hosting, with the same billing model. Prices for all of them are in the table on this page.

What to check before signing up

Read the price table for the monthly cap and remember that the term of 1 month is the length of the billing cycle for that cap. Confirm with DigitalOcean how charges behave for a server that is switched off, resized or deleted, since the data does not say.

Ask about the items the data leaves out: available operating systems, data center regions, whether a backup or snapshot service exists and what it costs, and what support is available. Also check that you can reach your current shared host's files and database export before you commit, because the migration depends on it.

Finally, be honest about the time commitment. A self-managed server needs routine attention for updates, backups and certificate renewals. If that is not something you want to own, compare this plan with managed options rather than with the other VPS plans listed here.

Practical setup guide

  1. STEP 1Create the server and record its IP address

    After signing up, create a server on the Basic 2 GiB plan, choosing a Linux operating system you know and adding your SSH public key during creation if the provider offers that step. Note the server's public IP address and, if one is assigned, its IPv6 address. Log in over SSH, create a non-root user with sudo rights, and disable password logins for SSH.

  2. STEP 2Install the stack, apply updates and open the firewall

    Run the operating system's package update first and enable automatic security updates. Install Nginx or Apache, PHP with the extensions WordPress needs, and MySQL or MariaDB, then install WordPress in the web root. Configure a firewall that allows SSH, HTTP and HTTPS and blocks everything else.

  3. STEP 3Copy the WordPress site from the shared host

    Export the database and download the files from your shared hosting account using its control panel or phpMyAdmin. Upload the files to the new server's web root, import the database, and update wp-config.php with the new database credentials. Test the site by editing your computer's hosts file to point the domain at the new IP before changing public DNS.

  4. STEP 4Point DNS at the new server

    Once the copy works, update the domain's A record to the server's IP address and add an AAAA record if the server has an IPv6 address; if the domain's nameservers stay with the registrar or old host, edit the records there. Keep the old shared account active until you have confirmed the new server is answering, since you cannot issue a certificate until DNS resolves to it.

  5. STEP 5Issue the TLS certificate and schedule backups

    When the domain resolves to the new server, install Certbot and issue a Let's Encrypt certificate; for an Nginx setup, replacing the placeholders with your own domain, the command is: sudo certbot --nginx -d example.com -d www.example.com. Then set up a scheduled job that exports the database and archives the files, and copy those backups to storage outside the server, because the official data does not list a backup feature for this plan.

Frequently asked questions

โ†‘ Back to the price table and plan link

Found this helpful? Share this article.