Pricing (16)·续

Example 1

This example represents a simple Durable Object used as a co-ordination service invoked via HTTP.

  • A single Durable Object was called by a Worker 1.5 million times
  • It is active for 1,000,000 seconds in the month

In this scenario, the estimated monthly cost would be calculated as:

Requests:

  • 1.5 million requests - included 1 million requests = 500,000 billable requests.
  • (rounded) 1,000,000 requests x $0.15 / 1,000,000 = $0.15.

Compute Duration:

  • 1,000,000 seconds * 128 MB / 1 GB = 128,000 GB-s.
  • 128,000 GB-s is within the 400,000 GB-s included allocation = $0.00.

Estimated total: $0.15 (requests) + $0.00 (compute duration) + minimum $5/mo usage = $5.15 per month

Example 2

This example represents a moderately trafficked Durable Objects based application using WebSockets to broadcast game, chat or real-time user state across connected clients:

  • 100 Durable Objects have 50 WebSocket connections established to each of them.
  • Clients send approximately one message a minute for eight active hours a day, every day of the month.

In this scenario, the estimated monthly cost would be calculated as:

Requests:

  • 50 WebSocket connections * 100 Durable Objects to establish the WebSockets = 5,000 connections created each day * 30 days = 150,000 WebSocket connection requests.
  • 50 messages per minute * 100 Durable Objects * 60 minutes * 8 hours * 30 days = 72,000,000 WebSocket message requests.
  • 150,000 + (72 million requests / 20 for WebSocket message billing ratio) = 3.75 million billing request.
  • 3.75 million requests - included 1 million requests = 2,750,000 billable requests.
  • (rounded) 3,000,000 requests x $0.15 / 1,000,000 = $0.45.

Compute Duration:

  • 100 Durable Objects * 60 seconds * 60 minutes * 8 hours * 30 days = 86,400,000 seconds.
  • 86,400,000 seconds * 128 MB / 1 GB = 11,059,200 GB-s.
  • 11,059,200 GB-s - included 400,000 GB-s = 10,659,200 GB-s
  • (rounded) 11,000,000 GB-s x $12.50 / 1,000,000 = $137.50.

Estimated total: $0.45 (requests) + $137.50 (compute duration) + minimum $5/mo usage = $142.95 per month.

Example 3

This example represents a horizontally scaled Durable Objects based application using WebSockets to communicate user-specific state to a single client connected to each Durable Object.

  • 100 Durable Objects each have a single WebSocket connection established to each of them.
  • Clients sent one message every second of the month so that the Durable Objects were active for the entire month.

In this scenario, the estimated monthly cost would be calculated as:

Requests:

  • 100 WebSocket connection requests.
  • 1 message per second * 100 connections * 60 seconds * 60 minutes * 24 hours * 30 days = 259,200,000 WebSocket message requests.
  • 100 + (259.2 million requests / 20 for WebSocket billing ratio) = 12,960,100 requests.
  • 12,960,100 requests - included 1 million requests = 11,960,100 billable requests.
  • (rounded) 12,000,000 requests x $0.15 / 1,000,000 = $1.80.

Compute Duration:

  • 100 Durable Objects * 60 seconds * 60 minutes * 24 hours * 30 days = 259,200,000 seconds
  • 259,200,000 seconds * 128 MB / 1 GB = 33,177,600 GB-s
  • 33,177,600 GB-s - included 400,000 GB-s = 32,777,600 GB-s
  • (rounded) 33,000,000 GB-s x $12.50 / 1,000,000 = $412.50

Estimated total: $1.80 (requests) + $412.50 (compute duration) + minimum $5/mo usage = $419.30 per month

Example 4

This example represents a moderately trafficked Durable Objects based application using WebSocket Hibernation to broadcast game, chat or real-time user state across connected clients:

  • 100 Durable Objects each have 100 Hibernatable WebSocket connections established to each of them.
  • Clients send one message per minute, and it takes 10ms to process a single message in the webSocketMessage() handler. Since each Durable Object handles 100 WebSockets, cumulatively each Durable Object will be actively executing JS for 1 second each minute (100 WebSockets * 10ms).

In this scenario, the estimated monthly cost would be calculated as:

Requests:

  • 100 WebSocket connections * 100 Durable Objects to establish the WebSockets = 10,000 initial WebSocket connection requests.
  • 100 messages per minute<sup>1</sup> * 100 Durable Objects * 60 minutes * 24 hours * 30 days = 432,000,000 requests.
  • 10,000 + (432 million requests / 20 for WebSocket billing ratio) = 21,610,000 requests.
  • 21,610,000 requests - included 1 million requests = 20,610,000 billable requests.
  • (rounded) 21,000,000 requests x $0.15 / 1,000,000 = $3.15.

Compute Duration:

  • 100 Durable Objects * 1 second<sup>2</sup> * 60 minutes * 24 hours * 30 days = 4,320,000 seconds
  • 4,320,000 seconds * 128 MB / 1 GB = 552,960 GB-s
  • 552,960 GB-s - included 400,000 GB-s = 152,960 GB-s
  • (rounded) 1,000,000 GB-s x $12.50 / 1,000,000 = $12.50

Estimated total: $3.15 (requests) + $12.50 (compute duration) + minimum $5/mo usage = $20.65 per month

<sup>1</sup> 100 messages per minute comes from the fact that 100 clients connect to each DO, and each sends 1 message per minute.

<sup>2</sup> The example uses 1 second because each Durable Object is active for 1 second per minute. This can also be thought of as 432 million requests that each take 10 ms to execute (4,320,000 seconds).

Frequently Asked Questions

When does a Durable Object incur duration charges?

A Durable Object incurs duration charges when it is actively executing JavaScript — either handling a request or running event handlers — or when it is idle but does not meet the conditions for hibernation. An idle Durable Object that qualifies for hibernation does not incur duration charges, even during the brief window before the runtime hibernates it.

Once an object has been evicted from memory, the next time it is needed, it will be recreated (calling the constructor again).

There are several factors that can prevent a Durable Object from hibernating and cause it to continue incurring duration charges.

Find more information in Lifecycle of a Durable Object.

Does an empty table / SQLite database contribute to my storage?

Yes, although minimal. Empty tables can consume at least a few kilobytes, based on the number of columns (table width) in the table. An empty SQLite database consumes approximately 12 KB of storage.

Does metadata stored in Durable Objects count towards my storage?

All writes to a SQLite-backed Durable Object stores nominal amounts of metadata in internal tables in the Durable Object, which counts towards your billable storage.

The metadata remains in the Durable Object until you call deleteAll().

Was this helpful?

YesNo

On this page

Pricing (16)·续 - 图1Docs

{"@context":"https://schema.org","@type":"TechArticle","@id":"https://developers.cloudflare.com/durable-objects/platform/pricing/#page","headline":"Pricing","description":"Durable Objects compute and storage billing, including pricing examples and free tier limits.","url":"https://developers.cloudflare.com/durable-objects/platform/pricing/","inLanguage":"en","image":"https://developers.cloudflare.com/durable-objects/platform/pricing/og.png?v=692e099f34a1b330","dateModified":"2026-10-18","publisher":{"@type":"Organization","name":"Cloudflare","description":"One platform for your apps, agents, and workforce. Build, secure, and scale without managing infrastructure","url":"https://www.cloudflare.com/","sameAs":["https://github.com/cloudflare","https://www.linkedin.com/company/cloudflare","https://x.com/cloudflare"],"logo":{"@type":"ImageObject","url":"https://developers.cloudflare.com/logo.svg"},"address":{"@type":"PostalAddress","streetAddress":"101 Townsend St","addressLocality":"San Francisco","addressRegion":"CA","postalCode":"94107","addressCountry":"US"},"contactPoint":[{"@type":"ContactPoint","contactType":"Customer Support","url":"https://support.cloudflare.com/","availableLanguage":["English"]},{"@type":"ContactPoint","contactType":"Sales","url":"https://www.cloudflare.com/contact/","availableLanguage":["English"]}]},"isPartOf":{"@type":"WebSite","@id":"https://developers.cloudflare.com/#website","name":"Cloudflare Docs","url":"https://developers.cloudflare.com/"}}

description: Storage and database options available on Cloudflare's developer platform. title: Choose a data or storage product image: https://developers.cloudflare.com/workers/platform/storage-options/og.png?v=abca508978294b6c

Skip to content

Documentation Index
Fetch the complete documentation index at: https://developers.cloudflare.com/workers/llms.txt
Use this file to discover all available pages before exploring further.