Cloudflare-first, measured

Run your app on Cloudflare.

The supported Creator Hub reference runs on two Workers, two D1 databases and one R2 bucket. There is no server to patch, no database host to run and no separate CDN to configure. The owner still controls the source, the data and every release decision.

Observed 12 October–12 November 2026 in the operator’s Cloudflare account. This page separates Cloudflare’s published precedent, our measured reference and illustrative growth assumptions. It is not a Cloudflare partnership, endorsement or official integration.

The supported shape

The supported Creator Hub setup

One scenario · measured in production

The Creator Hub reference is two independently owned applications. Here / there receives and moderates contributions; Linkarooie curates the public profile and reads approved items through a service binding. Each app has its own Worker, source repository and database. Only Here / there stores uploaded media.

A typical self-managed stack

You operate the plumbing

  • ComputeVM or container host
  • ApplicationWeb server and process manager
  • DatabaseDatabase server, backups, failover
  • MediaObject storage plus a separate CDN
  • Background workQueue, worker pool and scheduler
  • OperationsLogs, metrics, alerts and patching

App Composer on Cloudflare

You own the product

  • ComputeWorkers, managed by Cloudflare
  • ApplicationOne Worker per independently owned app
  • DatabaseD1 with versioned migrations in source
  • MediaR2 behind a Worker binding, free egress
  • Background workCron trigger or no schedule at all
  • OperationsWorkers observability, /healthz, release receipts
The comparison is about operating responsibility, not identical feature parity. A team with unusual runtime, network or data-residency needs may still require a different architecture. Cloudflare’s limits, pricing and service behaviour remain part of the design.
2Workers
2D1 databases
1R2 bucket
1service binding
1daily cron
2custom hostnames

There are no Queues, Workflows, Durable Objects or KV namespaces in this pair. The only scheduled work is Here / there’s existing daily maintenance trigger. Both apps are production deployments; the reference is operator-owned, not a customer-owned onboarding proof.

Externally sourced precedent

What Cloudflare measured at another company.

Baselime · Cloudflare estimate

Cloudflare’s published Baselime case study describes a much larger observability workload moving from AWS to Cloudflare. The numbers below are Cloudflare’s estimate for a comparable paying customer, not an independently audited saving and not an App Composer result. Baselime was acquired by Cloudflare in 2024.

Baselime’s reported daily infrastructure estimate (USD)
WorkloadAWS beforeCloudflare estimate
Compute$650 Lambda$25 Workers
CDN$140 CloudFront$0
Streaming and analytics$1,150 Kinesis / EC2$300 Workers Analytics Engine
Total daily$1,940$325
Annualised$708,100$118,625

Reported difference: roughly 83% lower estimated infrastructure cost, about $589,475 per year in this case. Source:Cloudflare’s Baselime case study, published 31 October 2024.

Do not read this as “83% cheaper with App Composer”. Baselime’s workload is not a WordPress site, a hobby app or a typical Creator Hub. Its value here is the architectural argument: fewer managed services can remove real operating work. Our own scenario is measured separately below.

App Composer’s own observed result

Measured Creator Hub usage

12 Oct–12 Nov 2026 · 31 days

This is the supported two-app reference atcreator-hub.loftwah.com andcreator-hub-guestbook.loftwah.com. The readings come from Cloudflare’s Workers and D1 analytics for the production scripts, plus the live D1 and R2 metadata. The source revisions served during the window wereb7cd3b3 for Linkarooie and 36797b8 for Here / there.

Observed reference usage and the applicable Cloudflare allowance
MeasureObservedIncluded on Workers Paid
Worker requests1,660 across both apps10,000,000 per month
D1 rows read2,84125,000,000,000 per month
D1 rows written13850,000,000 per month
D1 stored data249,856 bytes (about 0.25 MB)5 GB
R2 stored data2 objects, about 0.12 MB10 GB-month free
R2 egressNot separately measuredFree
Scheduled invocationsOne daily maintenance triggerBilled as Worker requests

What this cost

At the observed request and storage volumes, the usage attributable to this pair is $0 above the account’s US$5 monthly Workers Paid minimum. We do not claim the pair costs $5 in isolation: the account also contains App Composer and other services, and Cloudflare bills the account minimum once.

Excluded from this comparison: domain registration and renewal, Cloudflare plans beyond Workers Paid, Cloudflare Access / Zero Trust seats, agent or model usage, developer and maintenance labour, taxes, backups, support and every other resource in the account. A different app, traffic pattern or retention policy can change the result. The source data and commands are in thereview evidence.

Assumption-labelled model

What changes as it grows.

Workers only · D1/R2 excluded

Cloudflare’s current Workers Paid plan includes 10 million requests and 30 million CPU milliseconds per month. The rows below use Cloudflare’s own published examples for request and CPU charges. They do not include D1, R2, Access, domains or agent usage, so they are a lower bound rather than a whole-project quote.

Illustrative Workers charges under the current published price schedule
Monthly assumptionRequestsCPU per requestWorkers charge
Observed reference1,660Not measured$0 usage; $5 account minimum
Small supported app1,000,00010 ms$0 usage; $5 account minimum
Cloudflare’s 15M example15,000,0007 ms$8.00 including the $5 minimum
Cloudflare’s 100M example100,000,0007 ms$45.40 including the $5 minimum

The 1M row is our assumption, not a measured run. The 15M and 100M rows reproduce Cloudflare’s published pricing examples. At higher volume, add D1 rows and storage, R2 operations and storage, Access seats and any other product you choose. Current sources:Workers pricing andD1 pricing, reviewed 12 November 2026.

Model inference

Estimate a text task on Workers AI

Published rates · 19 Nov 2026

Suppose your app extracts structured records from text. This estimate prices 1,000 attempts, each with 2,000 uncached input tokens and 500 billed output tokens. Both model versions require Workers Paid or prepaid AI Gateway credits.

Estimated inference at published rates (USD)
Workers AI modelInput per million tokensOutput per million tokensEstimated total
GLM-5.3
@cf/zai-org/glm-5.3
$1.40$4.40$5.00
DeepSeek V4.1 Flash 1017
@cf/deepseek-ai/deepseek-v4.1-flash-1017
$0.30$1.20$1.20

Multiply billed input and output by their respective per-million rates and add the two amounts. Cloudflare hosts and meters these calls. Your coding agent uses its own provider or local runtime. AI Gateway can also route to external providers, with billing determined by the route and account setup.

This is a list-price estimate before any allowance. It covers the stated attempts and excludes additional retries, plan fees, hosting, storage and tax. Quality, latency and cost per successful record need an actual run. See Cloudflare’s current Workers AI pricing.

Cloudflare lists GLM-5.3 Flash for retirement on 20 November 2026 and points to GLM-5.3 for frontier workloads. Check the Cloudflare model retirement noticebefore choosing an endpoint.

The operating difference

What the owner and Cloudflare operate

Responsibility comparison
Who performs each operating job in the two models
JobTypical self-managed stackCreator Hub reference
RuntimeProvision and patch a VM or container hostCloudflare runs the Workers runtime
DatabaseRun the database server, backups and failoverD1, with migrations committed to source
MediaBucket, CDN and credential rotationR2 behind a Worker binding, free egress
Admin accessVPN, SSO proxy or IP allowlistCloudflare Access in front of native EmDash
Background workQueue, worker pool and scheduler hostOne existing Cron Trigger; no queue in this pair
DeploymentBuild host, release scripts and rollback procedureGuarded repository release with an exact Worker version
ObservationInstall and maintain an observability stackWorkers observability, /healthz and release receipts

What the owner still does

  • Owns the GitHub repositories and reviews source changes.
  • Approves contributions before they become public.
  • Holds the Cloudflare account, domain, Access policy and owner credentials.
  • Chooses when to deploy and checks the live result.
  • Decides retention, backups and what data may be exported.

What Cloudflare operates

  • The Workers runtime, D1, R2, KV and the network path.
  • The custom-domain certificate and edge routing.
  • The scheduled trigger’s invocation.
  • Access enforcement at the edge.
  • Usage metering and the published service limits.

Claim discipline

What this page does not claim.

Known limits stay visible

Supported and verified

  • Two independently owned Workers, two D1 databases and one R2 bucket in production.
  • One service binding, two custom hostnames and one existing daily Cron Trigger.
  • Cloudflare Access in front of native administration; anonymous requests refuse.
  • A guarded production release with exact source and Worker identity.
  • Preview isolation: distinct D1/R2/KV, no services, no routes and no cron triggers.

Unverified or unsupported

  • No universal saving, “zero infrastructure cost” or automatically lower bill.
  • No Cloudflare partnership, endorsement or official integration.
  • No customer-owned onboarding, physical-device acceptance or external participant proof.
  • No authenticated agent/MCP journey in this review, and no hosted Get Ready API.
  • No claim that every workload fits Workers, D1 or R2.

Next three technical risks

  1. Preview is a public, stale operator deployment.It has isolated data and no production services, routes or cron, but it still answers on workers.dev. Refresh or retire it deliberately rather than treating it as a sandbox.
  2. 88 undeclared Worker scripts remain in the account.Their retention, traffic and rollback role are unverified. No deletion is safe from a name or tag alone.
  3. The exact-source gate is conservative.A docs-only commit on a maintained app makes its live/build.json stale until the app is redeployed. That is safe, but it means readiness can refuse a runtime-identical release.

Technical review pack:Cloudflare review, 12 November 2026. Release history: verified outcomes. Access model:Cloudflare Access documentation. Architecture:how App Composer fits together.

Choose your next step

Get Ready establishes the supported environment before asking for an app idea. The Creator Hub is a real, inspectable example of what comes next.