Cloudflare

Figures published on the about page: Cloudflare says it serves "an average of 102 million HTTP requests per second", proxies "roughly 20% of the web's traffic", and serves "data from 335 cities in over 125 countries". The same page says Cloudflare was "founded in 2009", and that on "13 September 2019" it "made its debut on the public market" and "became a publicly traded company (NYSE: NET)".

Cloudflare is bought online rather than as a local trade. Customers sign up on the website, and larger buyers contact the sales team for a quote. Published plan prices and usage rates sit on the pricing page at https://www.cloudflare.com/plans/. The pages read here publish no business hours, no appointment or booking process, and no per-customer service area.

Other addresses on the same list include San Francisco (HQ) at 101 Townsend St. San Francisco, CA 94107, described as "Where Cloudflare was founded in 2009 - and where it all started"; New York City at 1 World Trade Center, 88th Floor, New York, NY 10007; Washington DC at 900 19th Street, N.W., Suite 375, Washington, DC 20006; Champaign at 301 N Neil St Suite 440, Champaign, IL 61820; and offices located in Mexico City, London, Paris, Lisbon, Munich, Brussels, Dubai, Bengaluru, Singapore, Beijing, Tokyo, Seoul and Sydney.

What the site does not publish should be stated plainly rather than guessed. The Austin location is listed only as an office address in a hiring context. The page gives no phone number, no email address and no opening hours for the Austin office, does not describe it as a walk-in or customer-facing site, and does not define an Austin or Texas service area, coverage map or list of areas served. Cloudflare's services are delivered over its network - the about page says the company serves "data from 335 cities in over 125 countries" - and are not tied to a customer's distance from any office. Anyone wanting an in-person meeting or a local contact should ask the sales team rather than assume the Austin address is open to visitors.

Lists Austin, Paris, Champaign, New York City, Lawndale, San Francisco, and Enterprise as a location. Names New York, Washington, and United States as a service area. Areas beyond these are not published.

SASE / Zero Trust plans. Free: "$0 forever", described as for "Teams under 50 users or enterprise proof-of-concept tests", with a "50 users" limit, "Community forums + Discord" support and log retention "Up to 24 hours". Pay-as-you-go: "$7 /user/month", for "Teams over 50 solving narrow SSE use cases without enterprise support", with "No limit" on users, "Chat and ticket support" and retention "Up to 30 days". Contract: "Custom", "Annual price per user", with "Phone, chat, ticket; professional services available (add-on)" support and retention "Up to 6 months; Logpush to SIEM/cloud storage".

The page carries its own qualifier on usage rates: "Prices listed are for monthly billing. Discounts are available for annual upfront commitments." A Contract plan has no listed price - the cost is quoted by Cloudflare's sales team, so ask them for an estimate rather than assuming a figure.

Beyond the fixed plan prices, Cloudflare's pricing page lists usage-based rates per product. These figures are quoted from https://www.cloudflare.com/plans/ as read on 30 August 2026 and are the monthly-billing rates; the page notes "Prices listed are for monthly billing. Discounts are available for annual upfront commitments." Confirm current prices on that page before relying on them.

Workers

free allowance "100k / day" requests and "10 ms / request" CPU time; paid "$0.30 / million requests" and "$0.02 / million CPU ms". Durable Objects: "100,000 requests / day" free, then "$0.15 / million requests". R2: "10 GB-month" free storage, then "$0.015 / GB-month", with Class A operations "$4.50 / million requests" and Class B "$0.36 / million requests". Workers KV: 1 GB stored free then "$0.50 / GB-month"; reads "100,000 / day" free then "$0.50 / million requests"; write, delete and list "1,000 / day" free then "$5.00 / million requests". D1: "5 GB (total)" free then "$0.75 / GB-month"; rows read "5 million / day" free then "$0.001 / million rows"; rows written "100,000 / day" free then "$1.00 / million rows". Queues: "$0.40 / million operations". Workers AI: "10,000 neurons / day" free then "$0.011 / thousand neurons". Images: 5,000 transformations a month free then "$0.50 / thousand".

Listed add-on costs

Argo Smart Routing, Load Balancing and Stream each "Starting at $5/mo"; Automatic Platform Optimization "$5/mo (Free plan); included with Pro/Biz/Ent"; Advanced Certificate Manager "$10/mo"; Client-Side Security "$0.099/1k requests"; Log Explorer "$1/GB ingested; first 10 GB free"; Cache Reserve "Usage-based"; Cloudflare Registrar "Starting at $7.85". For anything not on the rate card, the fees come from a sales quote.

Self-serve customers do not need to contact anyone: the site's call to action is "Start building for free - no credit card required", with sign-up at https://dash.cloudflare.com/sign-up and the dashboard at https://dash.cloudflare.com/. Support channels differ by plan; the pricing page lists "Community forums + Discord" on the free tier, "Chat and ticket support" on pay-as-you-go, and "Phone, chat, ticket; professional services available (add-on)" on a contract. The site navigation also carries an "Under attack?" link to https://www.cloudflare.com/under-attack-hotline/.

The pages read here publish no general contact email address, no office opening hours, and no online appointment, booking or scheduling tool for a sales call - the enquiry form and the regional phone numbers are the published options.

• Run serverless inference on GPUs – ship models that respond in under 100 ms worldwide, without managing clusters.
• Build agents and MCP servers – use the Cloudflare Agents SDK and Model Context Protocol (MCP) so Workers can coordinate tools, schedule tasks, and reason toward goals.
• Store training data – keep training data in R2 object storage for egress-free, multi‑cloud access to GPUs.

Cloudflare presents this as proven infrastructure, stating that it is the same end‑to‑end AI stack used for Cloudflare's own products and traffic at scale.

Components of the AI Cloud stack

The AI Cloud page groups the main components used to build AI agents and applications:

Workers AI model catalog

• Access to models such as Llama 3, Gemma 3, Whisper, text‑to‑speech, and LoRA‑fine‑tuned variants.
• Models are deployed across 190+ locations on Cloudflare's global network.

Agents SDK

• A TypeScript SDK for building goal‑driven agents that can call models, APIs, and scheduled tasks from a single interface.
• Includes built‑in state management so each agent can track its own state and store data in an associated SQL database.
• Supports multi‑modal interfaces, including real‑time updates via WebSockets and support for chat and other interactive experiences.
• Designed to run on Cloudflare Workers for global, low‑latency execution.

Remote MCP servers

• Cloudflare‑hosted, OAuth‑scoped endpoints that expose tools and data sources to agents without the customer having to self‑host an MCP server.
• Includes OAuth 2.1 provider functionality so developers can add authorization to their MCP servers.
• Cloudflare provides an "MCP playground" for testing remote MCP servers and an "MCPAgent" built on Durable Objects to handle transport and memory for agents.

AI Search and Vectorize

• AI Search – managed retrieval‑augmented generation (RAG) workflows with automatic indexing and support for shipping AI search and chat in one instance.
• Vectorize – a globally replicated vector database that pairs with Workers AI for RAG in a few lines of code.

R2 for training and application data

• R2 object storage for training data, checkpoints, and user uploads.
• The page highlights that data stored in R2 can be moved to other clouds with $0 egress from R2 (see the main R2 documentation and pricing page for the current terms).

AI Gateway

• A gateway layer in front of AI inference calls.
• Provides caching, rate limiting, model fallback, and observability for AI traffic.

How developers work with Cloudflare AI

• Cloudflare directs developers to try AI features in the Cloudflare AI Playground and dedicated "Agents" tooling.
• AI capabilities are part of the broader Cloudflare developer platform, alongside Workers, Durable Objects, D1, R2, KV, Queues, and other services listed on the products and pricing pages.

The pages read here describe these products and capabilities at a high level; they do not publish per‑model performance guarantees, per‑customer scaling limits, or detailed compliance commitments. For specifics on supported models, limits, SLAs, and regulatory requirements, Cloudflare tells customers to consult the current documentation or contact sales.

Storage

Artifacts, Cache Reserve, D1 ("Serverless SQL"), Data Platform, Hyperdrive ("Global databases"), KV ("Ultra-fast key-value storage"), Queues and R2 ("Egress-free storage").

AI

Agents ("Build stateful AI agents"), AI Gateway, AI Search, Vectorize ("Vector database"), Web3 and Workers AI ("Edge AI models"). Media: Images, RealtimeKit and Stream.

Security

Bot Management, Client-Side Security, DDoS Protection, Magic Transit, Network Firewall, Rate Limiting, SSL, Turnstile ("A CAPTCHA Replacement Solution") and WAF ("Web Application Firewall").

Network

Advanced Certificate Manager, Analytics, API Shield, Argo Smart Routing, CDN ("Faster delivery and caching"), China Network, Custom Domain Protection, DNS, Email Routing, Keyless SSL, Load Balancing, Log Explorer, Network Flow, Network Interconnect, Page Shield, RDP, Spectrum, TURN / SFU and Waiting Room.

SASE / Zero Trust

Access, AI Security for Apps, Browser Isolation, CASB, Data Loss Prevention, Email Security, Gateway ("Web filtering"), Mesh, Secure Web Gateway and WAN.

This is the catalogue of services the site publishes; it is not a statement of what any of them will achieve. For what a given product costs, see the pricing page; for scoping and a quote, contact sales.

The solutions overview lists the following workload‑focused areas:

• AI – build intelligent applications with AI at the edge.
• AI Security – "Secure and control AI adoption without slowing innovation."
• Frontends – deploy frontend applications globally in seconds.
• Network – global network services for performance and reliability.
• Platforms – build platforms on Cloudflare's infrastructure.
• Security – protect applications from threats.
• Workflows – orchestrate complex multi‑step processes.

An "Agentic Commerce" solution page is also referenced on the solutions listing.

Each of these areas links to its own solution page, which explains how relevant Cloudflare products (such as CDN, WAF, Zero Trust, Workers, R2, and AI services) are combined for that use case.

Solutions by industry and sector

The same solutions navigation calls out several industries and sectors, including:

• Financial services – secure digital infrastructure for modern financial services.
• Healthcare – secure and accelerate healthcare delivery.
• Public sector – enhance cyber resilience, accelerate performance, and advance AI innovation.
• Retail – build secure, high‑performance retail experiences with Cloudflare's unified cloud platform.
• Airlines and travel – SASE for airlines is listed as a specific Zero Trust solution.
• SASE for retail – a dedicated solution for retail organizations adopting SASE.

These entries signal that Cloudflare provides reference architectures and guidance for each sector. The pages read here do not publish industry‑specific pricing, service areas, or regulatory guarantees; instead they point buyers towards solution content and sales for detailed scoping.

What is *not* stated on the solutions pages

From the pages read:

• There are no published industry‑specific SLAs beyond the general uptime SLAs listed on the pricing page.
• There are no per‑industry implementation timelines or guarantees of outcomes.
• Compliance, data residency, and regulatory coverage are not detailed at the solutions‑overview level; those topics are handled in product‑specific documentation and legal pages.

Customers evaluating Cloudflare for a particular use case or industry are directed to:

• Review the relevant solution pages on cloudflare.com for architectural guidance and product combinations.
• Check the pricing page for plan tiers, usage‑based rates and SLAs.
• Contact Cloudflare sales for a tailored scope of work and commercial terms.

Ask anyway — the agent will say plainly that it is not published rather than guess.