Platform · Why Cloudflare

One platform. One global network. Built for the moment we're building for.

r.team runs on Cloudflare — the network that already carries roughly a fifth of the Internet and protects nearly half the Fortune 500. We didn't choose it for one feature. We chose it because security, private AI, agent infrastructure, and storage all live on a single platform, instead of a patchwork of vendors that trust companies, RIAs, and family offices would otherwise have to stitch together and defend.

~20% of the Internet runs on Cloudflare's network

42% of the Fortune 500 are Cloudflare customers

78% of the top 50 generative-AI products run on Cloudflare

500M+ transactions processed per second — thousands of times the largest payment network

The r.team stack, in one cross-section

Every capability we deliver — from client portals to AI-assisted analysis — sits on the same foundation. No data leaves the platform to be secured, stored, or reasoned over somewhere else.

01 · Security

Security as a property of the platform — not a product bolted on

Cloudflare's founding principle is that code should be secure because of where it runs, not because of what you attach to it. Every r.team request passes through the same defenses that screen hundreds of billions of bot and threat requests every day: DDoS mitigation, web application firewall, bot management, and Zero Trust access control.

That matters more now than ever. Frontier AI models are collapsing the window between a vulnerability being disclosed and being exploited — an interval heading toward hours, not weeks. A fiduciary platform can't wait for patch cycles; it needs a network that sees attacks across 20% of the Internet and blocks them before they reach the application.

Cloudflare is also the only vendor whose platform spans all four security jobs IT leaders now prioritize: securing workforce use of AI, governing AI agents, protecting applications, and building AI securely — one platform, one network, instead of separate SASE, app-security, and AI vendors.

02 · Private AI

AI with model choice, governance, and no vendor lock-in

Client financial data should never be an AI vendor's training set. On Cloudflare, r.team runs intelligence through AI Gateway and Workers AI — a choice of 150+ models, including leading private and open-source options, without committing your data or our architecture to any single AI lab.

Every AI call is observable, cacheable, and governed: we can route by task, cap spend, cache repeated work, and log activity for oversight. And because Cloudflare operates no frontier model of its own, it is a neutral layer — infrastructure that serves the AI ecosystem rather than competing with it.

The platform is compliant by default: data localization controls keep information where regulation says it must stay, without rebuilding the application for every jurisdiction.

03 · Building Blocks — Agents

The primitives of the agentic cloud

The last cloud era was defined by three AWS primitives: S3, EC2, and SQS. Cloudflare's thesis — and ours — is that the agent era needs new ones: Workers (isolates instead of servers), Workflows (durable execution instead of queues), and Durable Objects & Artifacts (stateful coordination instead of buckets). These are the Replacement Blocks r.team builds with.

Isolates were a non-consensus bet Cloudflare made in 2017: 0ms cold starts, automatic scaling to zero, and up to 100x more efficient execution than container-based clouds. Agents spin up ephemeral, task-specific code constantly — exactly the workload traditional clouds weren't designed for, and exactly what isolates were built for.

The economics follow. Cloudflare's published comparisons show roughly 50% lower total cost for agent workloads — 63.6% lower than AWS for deploying 10,000 agent-generated apps, 74.7% lower for a million agent sessions. Efficient infrastructure is what lets us deliver institutional capability at independent-firm pricing.

04 · Document Storage

Your documents, held close to you — and never held hostage

Statements, trust instruments, tax documents, meeting records — a platform for the trust business is, in part, a document platform. r.team stores documents in Cloudflare R2, object storage on the same global network that serves them, so files load from milliseconds away rather than from a distant region.

The principle behind R2 is one Cloudflare calls open by default: your data moves freely, not locked in by egress fees or proprietary barriers. Traditional clouds charge you to take your own data out — a quiet form of lock-in. R2 charges zero egress. If you ever want your documents somewhere else, they leave without a toll.

That independence is not incidental to r.team — it's the point. Parallel-Run Independence means your firm's records are portable, verifiable, and yours.

05 · Data Storage

Databases and state, on the same platform as everything else

Structured data lives in D1 (serverless SQL), fast lookups in Workers KV, vector search for AI in Vectorize, and live, consistent state in Durable Objects — the primitive Cloudflare positions as the successor to S3 for the agent era, and the one its own cost analysis shows running agent sessions at a fraction of hyperscaler pricing.

Because storage, compute, AI, and security share one platform, there is no data pipeline between vendors to secure, audit, or explain. The database sits next to the code, the code sits next to the model, and all of it sits behind the same Zero Trust perimeter.

Cloudflare calls this compliant by default — data stays where it needs to stay, without re-architecting for each jurisdiction. For firms answerable to regulators and trustees, that is the difference between demonstrating control and asserting it.

Six things r.team gets by default

Cloudflare states six foundational beliefs behind its platform. Each one is a property r.team inherits on day one — not a project we have to run.

Secure by default

A property of where your code runs, not a product you attach to it.

Fast by default

A consequence of the platform being everywhere, not a region you pick.

Scalable by default

Handled by the platform, not capacity you provision and manage.

Compliant by default

Data stays where it needs to stay, without rebuilding for every jurisdiction.

Verified by default

Trust established on every request — never assumed from being inside a network.

Open by default

Your data moves freely — no egress fees, no proprietary barriers.

The cloud that got us here won't get us where agents need to go. Cloudflare was built for this moment — and r.team is built on Cloudflare.

Where hyperscalers scale one application to millions of users, the agent era demands infinite ephemeral applications, many per user — spun up in milliseconds, secured by default, and torn down at zero cost. That is the platform underneath every r.team Replacement Block.

Figures and platform principles summarized from Cloudflare's 2026 Investor Day presentation (June 2026), including network scale, Fortune 500 and generative-AI adoption, isolate performance, TCO comparisons versus AWS and Vercel, and Cloudflare's "by default" platform beliefs. Statistics are Cloudflare's own reported metrics and estimates. r.team is an independent product of Got-Data Inc. and is not affiliated with or endorsed by Cloudflare, Inc.