Simple, predictable pricing

Shared container instances are typically recommended for applications such as low traffic websites, blogs, discussion forums, and CMS.
Dedicated container instances are generally recommended for applications with higher performance requirements or more consistent resource needs, such as ecommerce, SaaS, gaming, and AI/ML workloads.
For optimal performance, we highly recommend testing your application with both shared and dedicated instances. In some cases, smaller dedicated instances may provide better performance than shared instances.
This guidance is similar to droplet recommendations for shared vs. dedicated. Learn more here.

At a high level, an app is either free (only using static site components) or paid (using container instances).

• Free Tier: Only using static site components
  • 3 apps with static sites are free
  • 1GiB allowance per app
  • Additional apps are billed at $3.00 per app


• Paid: Apps with jobs, web services, workers or static sites.
  • Container pricing with bandwidth allowance by container allowance.
  • Static sites in a paid app are $0 and have no bandwidth allowance.


• Additional charges include the following:
  • Bandwidth usage beyond the allocated allowance is billed at $0.02 per GiB.
  • Paid features: Additional paid features include development databases ($7.00) and dedicated IPs ($25.00).


• To illustrate with an example, let's consider a paid app with the following components on a paid app:
  • 2 static sites components
  • 1 worker with 2 instances using the $10 container plan
  • 1 service with 1 instance using the $20 container plan


• The monthly cost for this app would be:
  • Static sites: $0 (no charge)
  • Worker: 2 instances x $10 = $20
  • Service: 1 instance x $20 = $20
  • Total monthly cost: $40 + any additional bandwidth overages

The amount of outbound data transfer included with your App Platform app depends on the number and size of the container instances your app is using.

Each container instance comes with a specific amount of data transfer allowance based on its size. For example, a dedicated container instance with 1 vCPU/0.5 GiB of RAM includes 100 GiB of outbound data transfer per month. If your app is using 5 instances of the 1 vCPU/0.5 GiB dedicated container size, your total data transfer allowance would be:
100 GiB × 5 instances = 500 GiB (or 0.488 TiB) per month, assuming all 5 instances were running continuously throughout the month.

It's important to note that the data transfer allowance is prorated on a per-second basis, just like with Droplets. This means that if you scale your app's instances up or down during the month, your data transfer allowance will be adjusted accordingly.

Each container instance in the DigitalOcean App Platform comes with a generous amount of egress data transfer allowance. To calculate the total outbound data transfer available to your app, we sum up the data transfer allowance for all container instances within that app. If you have multiple apps, we calculate the total data transfer allowance by summing up the data transfer quotas for all your apps. This becomes your overall data transfer limit.

Any data transfer exceeding this limit is considered overage and will be billed at a rate of $0.02 per GiB.

It's important to note that data transfer for the App Platform is calculated separately from data transfer for Droplets. These two should not be combined or confused when assessing your data transfer usage and limits.

App Platform Free Tier allows you to:
Build and deploy up to 3 apps with static sites for free
Each free app includes 1 GiB of outbound data transfer per month
Additional apps with staticsites only are charged at $3.00 per month
Outbound data transfer exceeding the allowance will be charged at $0.02 per GiB
The Free Tier is ideal for trying out App Platform, hosting personal websites, portfolios, or small projects.

We have simplified the App Platform pricing structure based on customer feedback. The Basic and Professional Tiers have been removed to provide users with more flexibility and control over their app's resources.
Instead of tiers, you now have the freedom to choose your app's resources and container instance types according to your specific needs. This means you can select the appropriate instance size and number of instances for each component of your app, without being restricted by predefined tier limits.
Additionally, egress data transfer allowance is now attached directly to the container instances, rather than being determined by the tier. Each container instance comes with its own egress allowance, which is calculated based on the instance size.
This new pricing model allows you to have more granular control over your app's performance and costs. You can scale your resources up or down as needed, and you only pay for what you use.
We believe this simplified approach will provide a more intuitive and user-friendly experience for deploying and managing apps on the App Platform.

A development database has 512 MiB RAM. It has more limited capabilities than a Managed Database. It can only be used from the app it belongs to, it is not backed up by default, it does not support multi-database creation - and if the app is destroyed, the development database is destroyed with it. Currently, the development database only supports PostgreSQL.

Dedicated egress IP assigns a pair of static IP addresses to your app. Note that it is billed at $25.00/app. It is because app platform provisions 2 droplets under the hood, assigns IP addresses and manages the whole life-cycle for you, while providing a highly available egress connection from your app.

No. Autoscaling is only available on dedicated instances. Shared instances work great, but given the very nature of sharing a vCPU between applications, the utilization may be sometimes influenced by factors like noisy neighbors. Therefore autoscaling is available on dedicated instances only.