Simple, predictable pricing

Previously, only functions deployed via App Platform were being counted toward your monthly free allowance. Starting August 1, functions deployed via the developer console and CLI will also count towards your monthly free allowance of 90,000 GiB-seconds for your account/team. This means the same pricing will apply to functions regardless of how they are deployed.

The monthly free allowance includes 90,000 GiB-seconds for the account/team. These are not prorated, do not roll over, and can be used on any apps under the same team.

GiB-seconds is used to indicate the amount of memory allocated to a task per second. For functions, GiB-seconds are the number of seconds your function runs for, multiplied by the amount of RAM memory consumed. It's a measure of resources used by your function.

After you exceed your free allowance, additional GiB-seconds are charged at $0.0000185. Usage is pooled at the account level.

At the end of each billing period, we aggregate usage and charge for the amount of GB-seconds in excess of the free allowance at the rate of $0.0000185 per GB-seconds. In the invoice, you'll see two items depending on your usage:

• GiB-seconds used from the free allowance
• GiB-seconds used in excess of free allowance and charge for that

No, the free monthly allowance is not rolled over to next month.

Yes, functions can be added as components of apps built on any tier of App Platform.

You can set up billing alerts in aggregate across all their DO resources, but not for Functions directly. As a workaround, you can set up an alert on the metric 'GiB-seconds' which roughly maps to your spend on Functions.

Minimum runtime is the minimum duration we'll charge you for. Function runtime will be rounded up to the nearest 100 ms.

We give you 90,000 GiB-seconds of free DigitalOcean Functions usage. Calculate the number of free Functions invocations you get with this formula:

Number of free function invocations = 90,000 GiB-seconds / (RAM Memory in GiB * Function run-time in seconds)

For example, a Function that runs for 100 ms and has 256MiB RAM dedicated to it, you can invoke this Function: 90000 GiB-seconds / (100/1000 seconds * 256/1024 GiB) = 3.6 million times before you are charged for Functions use.

We accept Visa, Mastercard, American Express, Discover, PayPal, Google Pay, and Apple Pay. Apple pay requires a Safari browser. For additional payment options, including wire transfer, purchase orders, and ACH, please contact us. Note that when you add a card, we may send a temporary pre-authorization request to the issuing bank. This pre-authorization charge is immediately released by DigitalOcean but may take a few days to clear from your card depending on the bank.

DigtalOcean billing cycles are monthly. Typically, on the first day of each month we invoice and automatically charge your account’s primary payment method for the previous month’s usage. In some cases, we might charge if your usage exceeds a threshold. You can also login and self pay the balance at any time.

No. Your card is only charged at the end of the billing cycle or upon exceeding a usage threshold. Pre-authorization charge: When you add a card, we may send a preauthorization request to the issuing bank. This is to verify that the card being added has been issued by the bank and that they will authorize any charges in future. These temporary pre-authorizations are typically $1 but can vary in range and are immediately canceled by us. Depending on your bank, it might take a few days for the charge to clear from the card.

We’re required by law to apply taxes in some countries. Click here to learn whether we collect taxes in your country, what the tax rate is, etc.

When you power off your Droplet, you are still billed for it. This is because your disk space, CPU, RAM, and IP address are all reserved, even while powered off. Therefore, charges are made until you destroy the instance.

Check out the docs to learn how to destroy Droplets, Kubernetes clusters, Managed Databases clusters (PostgreSQL, MySQL, Redis), Spaces, Volumes , Firewalls , and Load Balancers.

Yes, you can set up billing alerts and we will email you if the monthly spending exceeds an amount you specify.

You will never be billed more than the monthly cost of your Droplet. All Droplets are billed hourly up to a monthly cap of 672 hours (the number of hours in 4 weeks). If you use your server for fewer than 672 hours during the month, you will be billed for each hour that you used it. If you use your server for more than 672 hours that month, you will be billed at the monthly cost. For example, if you spin up a $10/mo Droplet and use it for 336 hours, then you would be charged $5 (going by the hourly rate). If you use that Droplet for 700 hours, then you would be charged $10 (capped at the monthly rate).

Our pricing is based on a single Droplet. You may have created additional resources and this could be the reason for the higher bill. You can check your bill in the control panel to get details on the various resources you are using. If you need help, please contact support.

Your card will be charged only after you have utilized the free credits. For example, if you received a $200 credit for 60 days, then that $200 credit is automatically applied to your account. If you spend $25 in that timeframe, then your card will not be charged. If you spend $300, then the $200 credit would be fully utilized and your card will be charged only $100. Since the credit is valid for 60 days, you won’t be able to use any remaining credit after 60 days.

We charge you for the underlying compute on which the 1-Click Apps runs.

To remove a saved payment method, visit the products billing page and click the … menu of the payment method, then click Delete. In the Confirm Delete Card window that opens, click Delete to remove the card. You cannot remove the default payment method on the account.

We charge you for the underlying compute on which the 1-Click Apps runs.

We do not offer refunds. If there are extenuating circumstances, contact support.

Our pricing calculator uses 672 hours (hours in a 28-day month month) to calculate the monthly cost for each provider. On-demand prices are shown. Prices are drawn from the following data centers: DigitalOcean: Prices consistent throughout all data centers GCP: US East (Iowa) AWS: US East (Ohio) Azure: US East (no state specified) The configurations we’ve used from other providers for this comparison are as follows: AWS- t3.micro, t3.small, t3.medium, t3.large, t3.xlarge, t3.2xlarge, m5.4xlarge, m5.4xlarge, m5.12xlarge, m5.12xlarge, m5.12xlarge, c5.large, c5.xlarge, c5.2xlarge, c5.4xlarge, c5.9xlarge GCP-f1-micro, g1-micro, n1-standard-4, n1-standard-8, n1-standard-16, n1-standard-32, n1-standard-64, n1-standard-96, n1-highcpu-4, n1-highcpu-8, n1-highcpu-16, n1-highcpu-32, n1-highcpu-64 Azure-B1S, B1MS, B2S, B2MS, B4MS, B8MS, A8m v2, A8m v2, D32 v3, D32 v3, F2s v2, F4s v2, F8s v2, F16s v2, F32s v2 The pricing calculator does not account for all available discounts. The pricing calculator does not include backups or snapshots, which incur an additional fee. DigitalOcean acknowledges that there is some variability and complexity in other providers’ pricing. If you wish to better understand the pricing for one of the providers included in our pricing calculator, we recommend you use the pricing calculators/lists from those providers. The pricing calculator was last updated on February 13, 2019.