Current through July 22, 2026

Cloudflare, deeply explained for non-developers.

A mobile-friendly field guide to the company, the platform, the business model, the security layer, the AI stack, and the products Outsource Access can build on top of it.

Plain English Source linked Mobile first
People & clientsIdentity + experience
Cloudflare edgeSecurity + compute
Data & intelligenceSQL + files + AI
WAF
Workers
R2
Agents
The strategic answer

Cloudflare can be the application foundation—not the replacement for every business tool.

Keep Google Workspace for communication and collaborative documents. Use Cloudflare for secure apps, client portals, databases, private files, workflows, AI orchestration, and the security perimeter.

Keep in Google Workspace

Communication and collaboration

  • Email and calendars
  • Google Chat
  • Collaborative Docs, Sheets, and Slides
  • Employee identity source
Add specialists where useful

Identity and advanced databases

  • Clerk, Auth0, WorkOS, or Supabase Auth
  • PostgreSQL through Hyperdrive
  • External model providers through AI Gateway
  • Independent backup and recovery destinations
From spam research to the agentic cloud

The evolution of Cloudflare

Cloudflare’s most important transition was not the IPO. It was becoming programmable: Workers turned a security and delivery network into a general application platform.

Revenue

2016–2025

$2.17B

Reported revenue in millions of US dollars.

Employees

2019–2025

5,156

Year-end reported headcount; 2026 restructuring makes the current figure fluid.

Capital history

Funding and the public offering

Founder-led governance

Leadership

Dual-class shares
Capability-led expansion

Acquisitions and teams

Cloudflare usually buys focused technology and talent, then turns it into a native capability on the same global network.

Recent strategic signals

What is changing now

2025–2026
The complete platform map

Explore all 128 named Cloudflare surfaces

Search by product name, category, or outcome. Open any card for a plain-English explanation and a concrete user experience example.

Turn ideas into architecture

What should your product use?

Select a product idea and optional needs. The builder translates your business experience into a practical Cloudflare stack.

1
Choose a product

Start with the experience

2
Add requirements

Adjust the stack

The Cloudflare agent stack

An AI agent is not one product. It is a secure chain of capabilities.

Cloudflare can provide the model, routing, knowledge retrieval, state, memory, browser, code execution, files, workflows, and private connectivity—but you still define permissions and human approval.

Treat an AI agent like a talented but distractible junior employee.

Give it narrow tools, no raw credentials, strict tenant boundaries, spending limits, complete logs, and human approval before sending, deleting, paying, publishing, or changing access.

Documented customer patterns

What real companies use Cloudflare for

These examples are based on Cloudflare customer stories or direct company statements. Product-logo appearances alone are not treated as proof of a specific configuration.

Why it feels unusually inexpensive

Model a self-service Cloudflare bill

Use the estimator for direction, not procurement. AI models, enterprise contracts, support, compliance, operations, logs, and engineering labor can materially change the real cost.

01

Shared global network

DNS, cache, WAF, compute, storage access, and Zero Trust reuse the same infrastructure.

02

Tiny marginal work

Many Worker requests use only milliseconds of CPU, so the incremental cost is extremely low.

03

Free is acquisition

The free tier creates adoption, traffic diversity, threat intelligence, and a future enterprise pipeline.

04

Enterprise pays for assurance

Large contracts add support, SLAs, compliance, logs, dedicated capacity, and commercial terms.

The competitive ecosystem

Cloudflare has no single competitor

It competes with hyperscale clouds, frontend platforms, databases, identity providers, CDN/security networks, SASE vendors, and AI infrastructure—while also integrating with many of them.

A particularly strong combination

Cloudflare + PostgreSQL + specialized customer identity

Use Cloudflare for the global application, security, files, workflows, and AI layer; PostgreSQL for complex relational data; and a dedicated identity provider for polished external login.

Cloudflare+Postgres+Identity
The shared-responsibility reality

Cloudflare gives you powerful controls. Your architecture determines whether they protect the right things.

A Cloudflare BAA or SOC 2 report can support your compliance program; neither automatically makes your application HIPAA compliant or gives Outsource Access its own SOC 2.

Cloudflare

Security of the platform

  • Global network and physical infrastructure
  • Covered platform controls and audits
  • DDoS, WAF, encryption, identity enforcement
  • Service reliability and incident response
Your team

Security in the application

  • Who may see or change each record
  • Tenant isolation and data minimization
  • Backups, retention, deletion, and audit evidence
  • AI permissions, approvals, and vendor choices
Interactive readiness checklist

Production security baseline

Your selections are stored only in this browser.

0%complete
Recommended path for Outsource Access

Build one reusable operating platform, then configure it into many products

The client portal, internal hub, Family Hub, lineup app, and Brad’s Command Center should share a secure core rather than become unrelated software projects.

Recommended default

The Outsource Access application standard

Employee identityGoogle Workspace + Access
Frontend and APIWorkers / Pages
Simple dataD1
Complex dataPostgreSQL + Hyperdrive
Private filesR2
Background workQueues + Workflows
AI controlAI Gateway
KnowledgeAI Search + Vectorize
Realtime stateDurable Objects
SecurityWAF + Turnstile + logs
ConfigurationTerraform
RecoveryIndependent exports + restore tests
Know the boundaries

What Cloudflare cannot—or should not—replace

The strongest architecture is Cloudflare-first, not Cloudflare-only.

01

Office suite

It does not replace Gmail, Calendar, Docs, Sheets, Slides, Chat, or Microsoft 365.

02

Finished business software

It gives you infrastructure to build a CRM, ERP, or portal; it is not HubSpot or Salesforce out of the box.

03

Every database

D1 is excellent, but it is not full PostgreSQL and is not ideal for every analytical or transactional workload.

04

Unrestricted servers

Workers are not arbitrary VMs. Containers close many gaps, but AWS, Azure, and Google Cloud remain broader.

05

Frontier model training

Cloudflare focuses on inference, routing, retrieval, and agents—not training the largest foundation models.

06

Compliance by default

Certifications and contracts support your program; your own controls, evidence, and behavior determine compliance.

07

Concentration-risk elimination

Cloudflare can have outages. Critical systems still need exports, backups, recovery procedures, and portability.

08

No-code magic

Agents still require data models, connectors, permissions, guardrails, monitoring, and thoughtful user experience.

Vocabulary translator

Cloud vocabulary in plain English

Trust the underlying evidence

Sources and methodology

This interface condenses official Cloudflare documentation, investor materials, SEC filings, customer stories, pricing pages, and selected external measurement sources. Live pricing, beta status, audit scope, and compliance coverage should always be rechecked before production or purchase.

How to interpret “128 capabilities”

It is the count of named entries in the Cloudflare developer-directory taxonomy used for this guide. It includes products, suites, administrative surfaces, APIs, and documentation collections—not 128 separately billed products.