There was an error while loading. Please reload this page.
Correct the free-tier claim: Workers Paid is required Measured in workerd: the PBKDF2 settings this app uses cost 66 ms of CPU to hash a password and 65 ms to verify one. The Workers free plan allows 10 ms per request. So signing in does not work on the free plan, and nor does creating the first account. The page said a small deployment costs nothing, which is wrong: $5 is the floor, not an upgrade. The R2 and D1 free tiers still apply on top. 600,000 iterations is OWASP's floor for this KDF, so the answer is the plan rather than weaker hashing.
Say that switching stores is free, and when it is worth it R2 egress is free, B2 ingress and API calls are free, and the two peer, so moving 10 TB between them costs nothing. That is the fact that makes an assisted migration worth building: there is no lock-in to escape, only time. Includes the savings table and the floor below which the advice is to do nothing, because Cloudflare's free tier already covers it.
Factor the free tiers into the numbers A small deployment costs nothing: 10 GB R2, 10M reads, 1M writes, 100k Workers requests a day and D1's allowances all compose. The earlier tables quoted $5 plus storage as though it always applied, which overstated the entry cost. The first thing to break is R2 storage at 10 GB, since one master can exceed it. The request budget may break sooner for a busy team, but that is unmeasured and is flagged as such.
Cheaper storage, and realistic volumes in the comparison B2 is $6.95/TB against R2's $15, with free egress to Cloudflare under the Bandwidth Alliance and free API calls. The blob store is a port, so this is an implementation away rather than a redesign, and it is the same SigV4 work as presigning R2. Also drops the 30 TB row, which nobody actually stores, and adds the four levers worth pulling: cheaper bucket, cold originals in Infrequent Access on a lifecycle rule, dedup on the content hash already computed, and an explicit option not to keep originals at all.
Add the Frame.io comparison and where the crossover sits Onelight's advantage grows with seats and its disadvantage grows with storage, because Frame.io bundles 2 TB per seat and Onelight charges for storage alone. Includes the uncomfortable number: Frame.io's marginal storage is $7.50/TB against R2's $15/TB. Storage is not where this wins, and saying otherwise would not survive a spreadsheet.
Rewrite pricing and benchmarks, add encoding Both pages were overwritten prose. Rewritten as tables and short statements. Adds the Workers free tier, which the rates table had left out, and an Encoding page: Cloudflare Containers can run ffmpeg, cap at 4 vCPU and 20 GB disk with no GPU, and the disk cap blocks the current design because the worker downloads whole sources.
Add pricing and benchmark pages Pricing is derived from Cloudflare's published rates, read 2026-08-03 and linked, with the arithmetic kept simple enough to redo. Everything that is an assumption says so, and the four numbers that need measuring before the request and CPU terms mean anything are listed rather than guessed at. Benchmarks is a methodology with no results yet, on purpose: it says what to measure and which conditions have to be recorded with each number, so the first real run lands somewhere with its context attached.