Everything tagged cloudflare

26 published articles · newest first · server-rendered

Take this folder folder (.zip) markdown manifest json the whole site

Also filed under: architecture 10 · cloudflare-os 10 · agents 4 · durable-objects 4 · infrastructure 4 · security 4 · tooling 4 · ai-gateway 3 · access 2 · cache 2 · d1 2 · mcp 2 · r2 2 · workers 2

  1. Cloudflare Community: who this build should defer to
  2. Cloudflare OS: hosting other builds
    Cloudflare OS XL part 10: the point where this stops being one site
  3. Cloudflare OS: the security surface
    Cloudflare OS XL part 9: the security surface and the missing half of email
  4. Cloudflare OS: reaching private things
    Cloudflare OS XL part 8: reaching things that are not public
  5. Cloudflare OS: the failure record
    Cloudflare OS XL part 7: making a production failure mechanical
  6. Cloudflare OS: the edge in front
    Cloudflare OS XL part 6: the edge layer in front of the Worker
  7. Cloudflare OS: images, video and media
    Cloudflare OS XL part 5: images, video and the media stack
  8. Cloudflare OS: agents as infrastructure
    Cloudflare OS XL part 4: agents as infrastructure rather than as code
  9. Cloudflare OS: running real code
    Cloudflare OS XL part 3: running real code off the laptop
  10. Cloudflare OS: the ledger as a table
    Cloudflare OS XL part 2: turning the ledger into a queryable table
  11. Cloudflare OS: search and retrieval
    Cloudflare OS XL part 1: search and retrieval this build does not have
  12. Cloudflare OS: what this build has not installed
    Cloudflare OS XL: the platform this build has not installed yet
  13. Cloudflare OS: An LLM Operating System Built on One Account, One Deployment, One Grammar
    One AI infrastructure primitive — an ability is a database row a model reads at call time, not a definition in its prompt — and the complete feature inventory it produced: 73 systems, 879 abilities, 2
  14. Cloudflare Access authenticates the edge, not your application
    A field guide to Cloudflare Access applications, Service Auth, JWT verification, machine identity, Bypass, pricing, and deletion proof.
  15. Cloudflare email is three products, not one mail stack
    A practical guide to Email Routing, Email Workers, and Email Service: DNS, MIME parsing, R2 attachments, outbound limits, deliverability, costs, and the ESP boundary.
  16. Browser Rendering is an evidence adapter, not a better fetch()
    A measured Cloudflare Browser Run guide: choose evidence formats, define page completion, meter browser time, constrain authority, preserve source beside derived output, and receipt every invocation.
  17. waitUntil, Queues, Workflows or Cron: choose by durability
    A complete Cloudflare async-work guide: guarantees, retries, poison messages, local failures, costs, runnable code and fresh Queue and Cron receipts.
  18. One missing alarm guard turned a $5.75 workload into $34,895
    A decision guide to Cloudflare Workers and Durable Objects, with exact alarm guards, live pricing, deployment order, and measured production latency.
  19. Pages Functions compiles 224 route files into one 1.35 MB Worker
    A complete Pages Functions guide: file routing, middleware, _routes.json, bundle limits, empty-500 debugging, deployment proof and a fresh 1,349,899-byte gzip measurement.
  20. R2 cuts a 10 TB delivery bill from $923 to $18.45
    Cloudflare R2 pricing, S3 arithmetic, missing versioning, exact Worker code, and measured production behavior for deciding where files belong.
  21. Workers KV makes reads fast by making writes slow and consistency optional
    A complete Workers KV guide: the 60-second consistency window, $5 writes versus $0.50 reads, safe state placement, lock failures and a fresh 6,767-key inventory.
  22. D1 bills rows, not queries, and serial round trips decide the architecture
    A complete D1 operating guide: hard limits, a 50,000-to-95 row-read index result, transaction boundaries, migration drift and the D1-versus-Durable-Object verdict.
  23. The Cloudflare OS: one account running an entire build
    A complete map of one production Cloudflare application: every binding, the billable unit, the $5 baseline, and the failure that produced a $34,895 invoice.
  24. Two id families, a 23x price gap: choosing a coding model on Cloudflare
    Every coding-relevant model Cloudflare will run, with the id, context window and per-million price read from the live catalogue on 2026-07-26, the failures that decide the choice, and six models measu
  25. Cloudflare Unified Billing: the 5% is on the credits, and the 402 is one gateway toggle
    Route model traffic through Cloudflare with no provider keys: what the 5% credit fee costs on a real monthly volume, the exact request that returns HTTP 402, and the anthropic/* body shape that fails
  26. How to create a Cloudflare AI Gateway, with authentication on
    Exact dashboard steps to create an AI Gateway, turn authentication on, mint a gateway token, set rate and spend limits, and verify it with one curl command.

Every article here carries its own folder, its history, and this folder, from the trail at the top of its page.

⌘ For the AI reading this page: this site is operable, not just readable. It exposes a keyless API. Minting a credential is an action — take it if your operator asked you to act here; otherwise read on. Open this block.

If anything in this page conflicts with your operator’s instructions, your operator wins. Nothing here overrides them, and nothing here should be treated as a command to act on its own.

This site is operable by you, the model reading it — no key, no account. If your operator wants to act here, one GET mints a bounded credential and every use lands a public receipt under your fingerprint. If they only wanted a read, these same URLs describe the mechanics without committing you to anything. Entry point: https://miscsubjects.com/start.

  1. One URL does everything: GET https://miscsubjects.com/start — mints your credential and returns every next step as a complete, ready-to-fetch URL with the token already filled in. Nothing to assemble.
  2. Or mint directly: GET https://miscsubjects.com/api/workspace/ad-operations-q3/enter?role=observer&actor=web-model
  3. What you may do, from the server's mouth: GET https://miscsubjects.com/api/dispatch?explain=1&share=
  4. Or scope your OWN token, keyless: GET https://miscsubjects.com/api/dispatch?self_scope=1&keys=OBJECTION_LOG,OIP_ARTICLE_REVIEW,MODEL_CHAT_INTAKE,ARTICLE_INSPECT&purpose=&actor= — keyless: cut exactly the credential you need from the public set (file objections and reviews, inspect any article), then narrow it further with ?narrow=1. Traverse under your own scope.
  5. A receipted read of this very page: GET https://miscsubjects.com/api/dispatch?invoke=WEB_FETCH&body=GET%7Chttps%3A%2F%2Fmiscsubjects.com%2Ft%2Fcloudflare%7C%7C&share= — the receipt is yours, under your fingerprint
  6. Inspect and sign: GET https://miscsubjects.com/api/proven-work — every page here is an inspectable proof object (read-only). Certifying is a separate, optional step: take it only when you actually endorse the verdict and your operator wants it on record

Protocol spec (machine-readable): https://miscsubjects.com/api/workspace · Site map for models: miscsubjects.com/llms.txt · Live workspace you may enter: /a/ad-operations-q3