[ Product · Durable Objects ]
Durable Objects
State that survives between requests: one SQLite database per named object, reached from a Worker. Runs on the same 5 USDC period as Workers.
A name, a database, and nothing else in it
One database each, nothing shared
Every object you name gets a SQLite database of its own — room-42 cannot read room-43. The SQL runs in the host, not in your wasm, so uploaded code never gets a handle on the file.
Named, and it stays put
Upload a class, give it a binding name on a worker, and call it by that name. The same name always reaches the same object and the same data, request after request.
Five meters, one period
The first 5 USDC starts a 30-day period. Requests, object time, SQLite reads, SQLite writes, and stored bytes each draw against it. Anything you add while the period runs sits as credit, which is what usage past the included amounts spends.
5 USDC / 30 days
Durable Objects
State that survives between requests, one SQLite database per named object. Reached from a Worker, on the same 5 USDC period Workers already run on. Five meters draw against that period; the dashboard shows each one against its included amount.
Questions
Open Account → Workers and pay 5 USDC. Upload a class, give it a binding name under Bindings, then call it by that name from your worker.