State (Durable Objects)

State keeps small values that stay put between requests and deploys: a counter, a lock, a flag, a rate-limit bucket. Every call goes to one place, in order, so two requests never both win. It runs on a Cloudflare Durable Object.

Use State when a value must be exact. A key-value store is faster to read from everywhere but is eventually consistent, so two requests that increment the same KV key can lose an update. State cannot.

State is available on every plan, on container apps and on SSR and hybrid apps.

Add State#

1. Open your app. On Overview, choose Add resource, then State.
2. Enter a Name, such as visits.
3. Choose Attach, then redeploy the app.

State is not created or shared like a bucket: it belongs to the app. Every State you add to one app shares the same set of keys. Adding two gives you two names for the same store. The data outlives deploys.

Use it from your code#

State answers the same paths on every runtime:

Container apps#

Call the private host. Copy the exact host from the State sheet's Connect tab. It looks like dply.my-app.visits.internal.

use Illuminate\Support\Facades\Http;

Http::withBody('hello', 'text/plain')->put('http://dply.my-app.visits.internal/greeting');
$value = Http::get('http://dply.my-app.visits.internal/greeting')->body();
$visits = (int) Http::post('http://dply.my-app.visits.internal/incr/visits')->body();

const host = 'http://dply.my-app.visits.internal';

await fetch(`${host}/greeting`, { method: 'PUT', body: 'hello' });
const value = await (await fetch(`${host}/greeting`)).text();
const visits = Number(await (await fetch(`${host}/incr/visits`, { method: 'POST' })).text());

Worker apps (SSR and hybrid)#

Call env.NAME.fetch() with a path. The host in the URL does not matter.

export default {
  async fetch(request, env) {
    const n = await (await env.VISITS.fetch('https://state/incr/visits', { method: 'POST' })).text();
    return new Response('Visit #' + n);
  },
};

The raw Durable Object namespace is available as env.NAME.namespace if you need it.

Try it#

State lives inside the running app and only the app can reach it, so the dashboard cannot read or write it. The sheet's Try it tab gives a command to run from the app instead:

curl -X POST http://dply.my-app.visits.internal/incr/visits
curl http://dply.my-app.visits.internal/

Pricing#

State bills every unit from the first:

Duration is the time the object is active, at 128 MB. Storage is the largest size during the month. Usage is collected daily and billed to your organization. This bills at the invoice line Workers CPU, Durable Objects, object storage and images.

Delete#

Choose Delete on the card, or Delete State in the sheet. The app loses this State on the next deploy, and code that calls it gets errors.

The keys are not wiped. Every State on the app shares one store, so another State on the app, or one you add later, sees the same keys again. They are deleted only with the app.

Related#

• Resources overview
• Key-value (KV)
• Usage & metering