itlinux.cc / Demo Factory ← All demos AI Gateway DemoBot

Cloudflare Demo Factory

Describe any business in plain English. In about 30 seconds Cloudflare generates and actually deploys a branded microsite on its own subdomain — AI-written copy, a generated logo and hero image, a chatbot, and a real security rule. Nothing is mocked: every step is a live API call you can verify in the dashboard afterwards.

Build workflow01 Define02 Generate03 Review04 Publish
Choose build time & complexity

More time means more complexity, detail and connected demo data. Quick Site and Standard App generation are available now; Showcase generates now as a separate application path.

What this demonstrates
🤖 Workers AICopy, logo and hero art generated at the edge for a branded microsite.
🛡 AI GatewayThe site chatbot is proxied through AI Gateway with DLP + Guardrails.
🔑 Zero TrustPublishing requires Cloudflare Access; the public microsite does not.
⚡ Workers + KVOne Worker serves the tenant site with a live subdomain and security demo.
Quick is the live microsite path: describe a business, generate its branded site, and verify the security rule in the dashboard.

Work at Cloudflare? Request access.

Submitting this form sends no email. After approval, open the login page and click Send login code; Cloudflare Access then emails the one-time code to the approved mailbox.

Use your exact @cloudflare.com address and tell Remo what you want to build. Submitting a request does not itself grant access. Remo reviews and approves each address individually.

Why access is required: building can consume AI inference, store demo data, and change Cloudflare configuration when an approved site is published. Public examples and previews remain available without access.

Request guardrails: rolling exact-email and source limits are enforced by the D1 campaign runtime. Permit creation still fails closed unless the complete D1, Workflow, OTP, and exact-email Access policy prerequisites pass live readiness. Denials stay generic so they do not reveal whether an email or request exists.

Retention policy that will apply: approved non-owner demos normally remain live for 7 days after publication. A site created under a 2-hour permit remains live only until that original permit expires. Owner sites remain until manually deleted. Current simple tenant records do not expose retention metadata, so no countdown is shown.

Manual access requests require an @cloudflare.com address. External recipients need a campaign keyword or a direct permit from an approver. Manual requests are reviewed in the protected Factory portal; no approver-notification email is configured.

Did Remo give you a campaign keyword? Skip manual approval

The keyword replaces prior email approval, not mailbox verification. Use any valid email address. After the permit is created, continue to Cloudflare Access and click Send login code; Cloudflare Access then emails a one-time code to that exact mailbox.

AI Keyword Studio: AI suggests the memorable phrase theme only; the Worker adds the secret random suffix locally. AI never sees a keyword and never approves access.

AI suggests stem onlyHMAC stored2h hard ceiling
Recipients submit here: enter the exact email, full keyword and a reason. The response stays generic. A successful reservation creates only an exact-email, OTP-required permit.
Manage campaigns (approvers)
Awaiting approval
Loading…
All run on Cloudflare Workers AI — swap providers (Meta, Mistral, Google, Qwen, DeepSeek, Stability, Black Forest Labs…) without changing a line of app code.
Checking identity…
Choose Factory mode

Pick 1–3 here, then use the action directly below.

What gets built
AI-written copyGenerated logoLive subdomainAI Gateway chatDLP + GuardrailsBlock → redirect rule
build bespoke-showcase-1

Sites built with Factory

Every public site generated and published through this Factory, newest first.

Loading published Factory sites…

Cloudflare services used by Factory

The platform foundation is live today. Each mode adds application depth; unfinished reusable generators are labeled planned rather than presented as active.

Live · reference · planned

Quick

Live today
≤2 minutes

Generates and publishes a branded microsite with governed AI chat and a real security demonstration.

Live services
Cloudflare WorkersWorkers AIAI GatewayDLPGuardrailsCloudflare AccessKVCustom DomainsRedirect Rules

Standard

Live today
2–4 minutes

Adds a focused 2–3-page public read-only frontend with 1–2 personas, synthetic data, generated hero and supporting imagery, a workspace overview and one workflow. The brief explicitly opts into persistent D1 data and authenticated editor controls when records, filtering, cross-page state or durable workflows need to survive requests.

Live services
Quick foundationPublic read-only frontendGenerated hero + 2–3 supporting imagesPublic DLP-protected chatStatic synthetic dataOptional persistent D1 + editor controlsCloudflare WorkflowsWorkers AIAI GatewayOptional protected Access backendOptional MCP tool

Showcase

Generates now
Typical observed analysis: 2-5 minutes; Typical observed post-accept build: 2-4 minutes. Server/profile ceiling: 16-30 minutes.

Showcase analysis takes approximately 2–5 minutes. After acceptance, the post-accept build takes approximately 2–4 minutes on the observed path.

Planned service set
Application foundationD1 at scaleR2Cloudflare WorkflowsMCP toolsetWorkers AIAI GatewayDLPGuardrailsCloudflare Access
Status note: planned does not mean enabled. Quick and Standard are live reusable generators; Showcase generates now as a separate application path. Factory access campaigns separately use D1, Cloudflare Workflows and exact-email One-time PIN policies.