AI Engineer

Why Eval++ Is the Next Great Compute Primitive — Sunil Pai & Matt Carrie, Cloudflare

3818 summary words 17 min summary Watch video

Start with the signal

17 min read

Summary

At-a-Glance

  • Verdict: Watch fully
  • Core thesis: Dynamic Workers (eval++) and Durable Objects provide a fundamentally better compute primitive for AI agents by enabling stateful serverless execution with secure code generation, making problems like resumable streaming, multiplayer AI, and MCP server deployment trivial instead of complex distributed systems engineering.
  • Why it matters: Cloudflare claims to have solved core AI agent infrastructure problems (state, sync, sandbox, MCP deployment) with a novel architecture that costs ~$5/month for production SaaS, unlocking a 30-year unexplored branch of the tech tree by making eval() safe and scalable.
  • Best use: Watch for architectural paradigm shift in agent infrastructure; attend their follow-up talks for code mode details (5:40pm same day, next day); evaluate if Durable Objects + Dynamic Workers replace your current agent stack (especially if you need multiplayer, resumability, or code execution).

Executive Summary

Sunil Pai and Matt Carrie from Cloudflare's agent team present their bet that Durable Objects + Dynamic Workers form the next great compute primitive for AI agents. Durable Objects are stateful serverless units: a class that spins up once per ID and persists across requests, providing sub-15ms latency globally. This solves the classic serverless hit-counter problem without databases, and turns out to be ideal for agents—addressable, long-running, hibernating, persistent, with WebSocket support. They've built a full agent SDK on top, providing React hooks, scheduling, and the world's best backend for Vercel's AI SDK (their claim).

Dynamic Workers are the second pillar: a worker that can execute untrusted code strings (from users or LLMs) in isolated sandboxes with zero filesystem, no env vars, and explicit capability grants (e.g., only fetch to GitHub.com). This is 'eval++', a security-first approach starting from nothing and adding permissions, unlike VMs that start permissive and try to lock down. They call this 'code mode' and argue it unlocks generative UI (render React/HTML directly, not JSON), extensions, and plugins without WordPress-style security incidents. Cloudflare's new CMS (M-Dash) uses this for plugins; their agent harness (in development) will use it for skill generation.

They claim to have 'fixed MCP twice': first by making Durable Objects ideal for stateful MCP servers (PayPal, Sentry, Linear, Intercom all on Cloudflare), second by using code mode to expose 2,600 Cloudflare API endpoints in 1,000 tokens (Sunil's talk). Their vision: agents as multiplayer, resumable, stateful entities with sync across tabs/devices out of the box, delegating to containers/browsers when needed but using Workers as the nexus. They're building a Devin/Cursor-like coding agent harness on this stack, shipping 'imminently'. The conference is their distraction from 'burning tokens'.

The business model angle: Cloudflare's architecture (hardware near ISPs, bulk bandwidth, peering agreements) makes free/cheap tiers structurally viable, not marketing spend. Production SaaS run on $5/month accounts. They position themselves as infrastructure for the 'branch of the tech tree we haven't explored in 30 years' now that LLMs can write code. Announcements week coming up with more agent features; they're orange-pilling developers on Durable Objects as the stateful serverless primitive and Dynamic Workers as the safe eval primitive.

Key Takeaways

  • Claim: Durable Objects solve the fundamental state problem in serverless by providing a class instance that persists per ID, enabling stateful agents without databases or sticky sessions. | Evidence: Hit counter example: counter++ fails in Lambda-style serverless (counter always zero), requires database. Durable Object maintains state. TLDraw sync demo: open multiple phones on same screen, drawing syncs perfectly with <15ms latency (under 60fps frame budget of 16ms). | Caveat: They call it 'vendor lock-in' humorously but acknowledge it's Cloudflare-specific. Migration off Durable Objects would require rewriting core architecture. Also described as 'worst named technology'—branding confusion ('it's a database' / 'no, but it has a database'). | Implication: If you're building agents with real-time sync, resumability, or multiplayer features, Durable Objects remove the need for Redis/Postgres + sticky sessions + distributed systems expertise. Evaluate if the lock-in trade-off is worth architectural simplicity and cost savings (they cite multi-million dollar SaaS on $5/month). | Timestamp: 00:42
  • Claim: Dynamic Workers enable secure execution of LLM-generated code via 'eval++'—starting from zero permissions and granting explicit capabilities, unlike VM sandboxes that start permissive and try to lock down. | Evidence: No filesystem, no env vars, no fetch by default. Example: grant only fetch to github.com/XYZ and Math.random. Worker-bundler pulls NPM dependencies inside a worker, strips TypeScript/JSX, runs in Cloudflare cache. M-Dash CMS uses this for WordPress-style plugins without WordPress security incidents. | Caveat: Enterprise skepticism: one startup founder at MCP Dev Summit insisted no enterprise would run unseen generated code; counterpoint: Lockheed Martin rep said 'we love generating code'. Adoption requires mental model shift ('we told you not to use eval for 30 years'). Python support is first-class but rough edges still being polished; other languages compile to WASM (Zig preferred for tiny bundles vs Go/Rust). | Implication: Code mode obsoletes JSON-based tool calling and DSLs—agents can generate and run actual code (React, HTML, extensions) securely. This is the architectural bet for generative UI, agent skills, and plugins. If you're building agent tools, evaluate whether code generation + sandboxed execution beats JSON schema + server-side interpretation. | Timestamp: 08:15
  • Claim: Cloudflare fixed MCP deployment twice: (1) Durable Objects provide stateful connections MCP needs, solving the 'annoying' problem of deploying MCP servers to the cloud; (2) code mode exposes 2,600 Cloudflare API endpoints in just 1,000 tokens. | Evidence: Early MCP servers (PayPal, Sentry, Linear, Intercom, unnamed others) all on Cloudflare. Original MCP required stateful client-server connection, which Durable Objects trivially provide. Code mode talk (Sunil, 5:40pm) will demo 1,000-token access to full Cloudflare API surface. | Caveat: Details of the 1,000-token technique not explained in this session (teaser for follow-up talks). Second fix claim relies on code mode being adopted, which is still new. No external validation yet of 'we fixed MCP' claims—this is Cloudflare's framing. | Implication: If you're deploying MCP servers, Durable Objects may be the simplest production path (vs stateful container orchestration). If you're building tool-heavy agents, attend the code mode talk to understand how 1,000 tokens can replace thousands of lines of tool definitions—potential major efficiency gain in context window usage. | Timestamp: 05:20
  • Claim: Resumable streaming and multi-tab sync come 'out of the box' with Durable Objects, eliminating the need for databases, replication, and sticky sessions that would otherwise be required in serverless. | Evidence: Use case: user asks LLM for long story, hits refresh mid-stream. Durable Object reconnects and continues streaming from where it left off. Same agent state visible on phone and laptop simultaneously without extra engineering. React hooks provided for client sync. | Caveat: This only works within Cloudflare's infrastructure—cross-cloud or hybrid deployments would lose these benefits. No discussion of failure modes (what happens if Durable Object region fails, latency spikes, etc.). Multiplayer AI is positioned as 'should exist' but doesn't in ChatGPT—Cloudflare is building the primitive, not the full product. | Implication: If your agent UX needs resumability (think Cursor's multi-session continuity) or multiplayer (shared AI workspace), this architecture eliminates significant backend complexity. The fact that ChatGPT doesn't have shareable links is framed as a 'bigger problems' issue at OpenAI—Cloudflare is positioning infrastructure as the unlock, suggesting startups can leapfrog big labs on UX if using the right primitives. | Timestamp: 10:45
  • Claim: Cloudflare's agent SDK is the 'world's best backend' for Vercel AI SDK, with production-ready features (tool calls, resumability, cross-tab sync) that the base SDK lacks. | Evidence: First-class backend for AI SDK. Praise for Nico Albrecht (AI SDK creator, though 'we don't allow Vercel employees into our chat rooms'—joke). Agent SDK provides scheduling (e.g., 'every Friday 9pm, compile Git history + Notion, send to manager with typos so it looks like I wrote it'). | Caveat: No benchmarks or public comparisons provided for 'world's best' claim—this is marketing-flavored assertion. AI SDK is front-end focused; Cloudflare provides the stateful backend, but you could arguably achieve similar results with other stateful backends (though likely with more engineering). No mention of AI SDK's other backend integrations or how they compare. | Implication: If you're using Vercel AI SDK for agent front-ends, investigate Cloudflare Agent SDK as the backend—may provide production features (scheduling, resumability, tool orchestration) faster than building on raw Workers or other backends. The scheduling primitive is particularly interesting for autonomous agents (weekly reports, monitoring, etc.). | Timestamp: 04:30
  • Claim: Cloudflare is building a Devin/Cursor-style coding agent harness natively on Workers/Durable Objects, shipping 'imminently', leveraging code mode for skill generation and extensions. | Evidence: Sunil implemented extensions 'this morning' and says it 'works really well'. They're in active development, distracted by conference from 'burning tokens'. Reference to Cognition's Devin and mentions friendship with Mario (likely Windsurf/Codeium founder). Discussion of running Pi agent directly on Workers. | Caveat: 'Imminently' is vague (no date). This is a work-in-progress announcement, not a product launch. Unclear if it will be open-source or commercial. Extensions use case is clear (OpenClaw comparison: heartbeat, virtual FS, service connections, sandboxed code), but actual product details are TBD. Next week is 'agents week' with major announcements—likely the real launch window. | Implication: Cloudflare is entering the coding agent race with infrastructure-native advantages (state, sandboxing, cost). If you're building or evaluating coding agents, wait for their agents week (next week from recording date) for full details. Their architecture (stateful + code mode + cheap) could be a strong challenger to existing harnesses if execution matches vision. Consider whether your agent infra should migrate to this model before they dominate the narrative. | Timestamp: 14:20

Detailed Brief

Durable Objects: Stateful Serverless Primitive

  • Claims: Durable Objects are a class instance per ID that persists across requests, solving the serverless state problem; Sub-15ms global latency (vs 16ms for 60fps), enabling real-time sync like TLDraw collaborative drawing; Ideal for agents: addressable, long-running, hibernating, persistent, with background execution and WebSocket support; Enables resumable streaming without databases—reconnect to same object, stream continues; Multi-tab and multi-device sync comes 'out of the box' via persistent connection model
  • Evidence: Hit counter example: let counter = 0; counter++ fails in Lambda (always zero), needs database; Durable Object maintains state; TLDraw demo: multiple phones drawing on shared screen sync perfectly; Use case: LLM generates long story, user refreshes browser, stream resumes automatically; Agent SDK provides React hooks for client-side sync; background scheduling (e.g., 'every Friday 9pm, compile Git history'); Positioned as 'stateful serverless'—scales across Cloudflare's planetary network
  • Caveats: Humorously called 'vendor lock-in' and 'innovation' interchangeably—tightly coupled to Cloudflare; Described as 'worst named technology' with confusion ('it's a database' / 'no, but it has a database'); No discussion of failure modes, regional outages, or cold-start behavior; Only works within Cloudflare network—hybrid/multi-cloud deployments lose benefits
  • Implications: Eliminates need for Redis, Postgres, sticky sessions, and distributed systems expertise for agent state; Enables multiplayer AI and resumable experiences that ChatGPT currently lacks—potential UX differentiation; Startups can build production SaaS on ~$5/month (cited examples of multi-million dollar SaaS on this cost structure); Architecture forces commitment to Cloudflare ecosystem, but gains are significant if you stay

Dynamic Workers: Eval++ for Secure Code Execution

  • Claims: Dynamic Workers execute code strings (from LLMs or users) in isolated sandboxes, starting from zero permissions; Security model: no filesystem, no env vars, no APIs by default; explicit capability grants only; Enables 'code mode': generate React/HTML directly instead of JSON for generative UI; Replaces DSLs and JSON schemas with actual executable code—'the branch of the tech tree we haven't explored in 30 years'; M-Dash CMS uses this for plugins, avoiding WordPress-style security incidents
  • Evidence: Example: grant only fetch to github.com/XYZ and Math.random(); everything else blocked; Worker-bundler: pulls NPM dependencies, strips TypeScript/JSX, runs inside worker using Cloudflare cache; Claude Artifacts cited as example: generates HTML, runs in browser (people less concerned about browser sandbox than server sandbox); Sunil implemented OpenClaw-style extensions 'this morning'—heartbeat, virtual FS, service connections, sandboxed code; Dichotomy at MCP Dev Summit: startup skeptical of running unseen code vs Lockheed Martin rep saying 'we love generating code'
  • Caveats: Requires mental model shift: 'we told you not to use eval for 30 years'; Python first-class but rough edges still being polished; other languages must compile to WASM (Zig preferred for bundle size); Enterprise adoption uncertain—some orgs may resist running LLM-generated code even if technically secure; Limited to JavaScript/Python natively; Go/Rust WASM bundles are larger than Zig; If native execution required, must spin up container (Cloudflare has SDK for this, but adds complexity)
  • Implications: Generative UI can skip JSON intermediary—agents directly generate and render React components; Agent skills/extensions become executable code instead of declarative tool schemas, potentially more powerful and flexible; 1,000-token MCP fix (code mode talk) could massively reduce context window usage vs traditional tool definitions; Opens design space for user-generated agent workflows (like Zapier but with actual code, not visual flows); If code mode becomes standard, agent platforms without secure sandboxing will be at disadvantage

MCP, Agent Harness, and Production Features

  • Claims: Cloudflare 'fixed MCP twice': (1) Durable Objects solve stateful connection problem, (2) code mode exposes 2,600 APIs in 1,000 tokens; Major MCP servers (PayPal, Sentry, Linear, Intercom) deployed on Cloudflare; Building Devin/Cursor-style coding agent harness on Workers, shipping 'imminently'; Agent SDK is 'world's best backend' for Vercel AI SDK with production-ready tool calls, resumability, cross-tab sync; vNext (Next.js on Cloudflare) runs fully on Workers/Durable Objects
  • Evidence: Original MCP required stateful client-server connection, which was 'annoying' to deploy to cloud; Durable Objects trivially provide this; Code mode talk (Sunil, 5:40pm same day) will demonstrate 1,000-token technique for Cloudflare API access; Sunil implemented extensions 'this morning', references OpenClaw (heartbeat, virtual FS, service connections, sandboxed code); Friendship with Mario (Windsurf/Codeium); discussion of running Pi agent directly on Workers; Agent SDK provides scheduling (e.g., Friday 9pm Git history compilation), React hooks, first-class AI SDK backend
  • Caveats: 'Imminently' is vague—no ship date for coding harness; next week is 'agents week' with announcements; 'World's best backend' claim unsupported by benchmarks or external validation; 1,000-token MCP fix not explained in this session—teaser for follow-up talk; No details on whether coding harness will be open-source or commercial; vNext and other products are separate efforts—full Cloudflare agent ecosystem still emerging
  • Implications: If building MCP servers, Durable Objects may be simplest production deployment (vs container orchestration); Code mode could dramatically reduce context window usage for tool-heavy agents—watch Sunil's talk for details; Cloudflare is entering coding agent race with infrastructure advantages (state, sandboxing, cost); monitor agents week announcements; If you're on Vercel AI SDK, evaluate Cloudflare backend for production features vs building your own; Architecture vision: Workers/Durable Objects as nexus, delegating to containers/browsers as needed—assess if this matches your needs

Business Model and Ecosystem Positioning

  • Claims: Cloudflare's free/cheap tiers aren't marketing—it's structurally viable due to architecture (hardware near ISPs, bulk bandwidth, peering agreements); Production SaaS built on $5/month accounts; multi-million dollar businesses cited; 'Friends and family company'—free credits for account IDs (jokingly framed as bribes/protection money); Twice-yearly announcement weeks; next week (from recording) is agents week with major releases; M-Dash CMS, Cloudflare Sandbox SDK, and other products expanding agents ecosystem
  • Evidence: Infrastructure: hardware near ISPs, buy bandwidth from level-zero ISPs, peering agreements mean cross-boundary bytes are cheap/free; Free accounts aren't marketing spend—'just how the business is constructed'; Comparison to typical $5/month account running multi-million dollar SaaS; M-Dash CMS launched last week, runs fully on Workers/Durable Objects with Dynamic Workers for plugins; vNext (Next.js on Workers) ships this week; agents week coming with more announcements
  • Caveats: Vendor lock-in acknowledged humorously but real—migrating off Cloudflare infra is nontrivial; Cost advantage assumes Cloudflare's scale and peering agreements; not replicable at small scale; No discussion of enterprise pricing or support tiers beyond free/$5; Ecosystem still maturing—vNext, M-Dash, agent harness all recent/upcoming releases; 'Friends and family' framing is playful but suggests pricing may be opaque or relationship-driven for some customers
  • Implications: If cost is a constraint, Cloudflare's structural advantages could enable business models competitors can't match; Lock-in risk is real, but if you're all-in on their stack, the integration and cost benefits may outweigh; Monitor agents week (next week from recording) for major product launches—likely the real 'go-to-market' moment; If building agent infrastructure, evaluate whether Cloudflare's ecosystem (Workers, Durable Objects, Dynamic Workers, M-Dash, Sandbox SDK) covers your needs vs stitching together AWS/GCP/Azure services; Sunil and Matt's talks (same day 5:40pm, next day) are required viewing for full technical details—this session was a high-level pitch

Notable Concepts & Terms

  • Durable Objects: Cloudflare's stateful serverless primitive: a class instance per ID that persists across requests, with sub-15ms latency globally, enabling real-time sync and stateful agents without databases or sticky sessions.
  • Dynamic Workers: Cloudflare's secure sandbox for executing LLM-generated or user-provided code strings, starting from zero permissions and granting explicit capabilities, enabling 'code mode' and avoiding VM-style security vulnerabilities.
  • Code Mode: Cloudflare's term for generating and executing actual code (React, HTML, extensions) instead of JSON, enabled by Dynamic Workers; positioned as unlocking a '30-year unexplored branch of the tech tree' now that LLMs can write code.
  • Eval++: Rebranding of eval() as secure and scalable via Dynamic Workers; 'we told you not to use eval for 30 years, now here's a fast, secure, and cheap way to do it at scale'.
  • Stateful Serverless: Cloudflare's oxymoronic but descriptive term for Durable Objects: serverless (scales, no ops) but stateful (persists data and connections across requests), solving the classic Lambda state problem.
  • Resumable Streaming: Capability where an LLM stream continues from the exact point of interruption (e.g., browser refresh) without re-generating, enabled by Durable Objects maintaining persistent connection state.
  • Multiplayer AI: Cloudflare's vision of AI agents/chats that multiple users can interact with simultaneously (like ChatGPT shareable links, which don't exist); Durable Objects provide the multi-tab/multi-device sync primitive.
  • MCP (Model Context Protocol): Anthropic's protocol for LLM-tool integration; Cloudflare claims to have 'fixed it twice'—once by solving stateful server deployment with Durable Objects, again by using code mode to expose 2,600 APIs in 1,000 tokens.
  • Worker Bundler: Cloudflare tool that pulls NPM dependencies, strips TypeScript/JSX, and generates runnable code inside a Worker, using Cloudflare cache for dependencies to avoid NPM downtime.
  • M-Dash: Cloudflare's new CMS (launched week before recording) that runs fully on Workers/Durable Objects and uses Dynamic Workers for plugins, avoiding WordPress-style security incidents.
  • vNext: Cloudflare's version of Next.js that runs fully on Workers/Durable Objects, positioned as a platform-agnostic (though Cloudflare-native) alternative to Vercel's Next.js.
  • @cloudflare/shell: Cloudflare package providing a full virtual file system layered on Durable Object SQLite (small files) and R2 (large files), enabling agents to have persistent storage without manual wiring.
  • Orange-pilled: Cloudflare community slang for developers who've adopted Durable Objects (orange = Cloudflare brand color), akin to 'red-pilled' but for their tech stack.

Operator Notes / Why Ken Should Care

  • Durable Objects + Dynamic Workers represent a genuine architectural shift for agent infrastructure: stateful serverless + secure eval. If your agent systems need state, sync, resumability, or code execution, this stack eliminates entire categories of distributed systems problems.
  • Code mode (Dynamic Workers) could obsolete JSON tool schemas and DSLs—agents generate and run actual code securely. This matters for content/business workflows (generative UI, plugins) and investing/GTM (WordPress-scale security without WordPress-scale risk).
  • Cloudflare's cost structure (free/$5 for production SaaS) is structural, not promotional—hardware near ISPs, bulk bandwidth, peering agreements. If you're building agent businesses, this could enable pricing/margin strategies competitors can't match.
  • MCP 'fixes' claim: (1) Durable Objects solve stateful server deployment trivially, (2) code mode exposes 2,600 APIs in 1,000 tokens. If true, the second fix could dramatically reduce context window costs for tool-heavy agents—attend Sunil's code mode talk for details.
  • They're building a Devin/Cursor-style coding harness on this stack, shipping 'imminently' (agents week next week). If successful, this could be a strong challenger to existing harnesses due to infrastructure advantages (state, sandboxing, cost). Monitor their announcements.
  • Resumable streaming and multi-tab sync out of the box—this is a UX unlock for agent products. ChatGPT doesn't have shareable links; Cloudflare is positioning this as a 'bigger problems at OpenAI' issue that infrastructure can solve for startups.
  • Vendor lock-in acknowledged but positioned as 'innovation'. If you go all-in on Workers/Durable Objects, migration off would be nontrivial. However, if the stack matches your needs, the integration depth and cost savings may justify it.
  • Watch Sunil's talk (same day 5:40pm) and Matt's talk (next day) for full technical details—this session was high-level pitch. Agents week announcements (next week from recording) are the real product launch window.
  • M-Dash (CMS with Dynamic Workers for plugins), vNext (Next.js on Workers), Sandbox SDK, and worker-bundler indicate a maturing ecosystem. If building agent products, evaluate whether Cloudflare's stack covers your needs vs stitching AWS/GCP/Azure services.
  • The 'branch of the tech tree we haven't explored in 30 years' framing (eval was taboo, now it's safe/scalable) is a strong narrative hook. If code mode becomes standard, agent platforms without secure sandboxing will be at disadvantage—watch for adoption signals.

Watch Map

  • 00:00: Intro: Matt and Sunil, Cloudflare agents team, based in London/Lisbon/Newcastle. 'Friends and family company' joke re: free credits.
  • 00:42: Durable Objects intro: stateful serverless, hit counter example, TLDraw sync demo, 'worst named technology'.
  • 04:30: Agent SDK overview: extends Durable Objects, React hooks, scheduling (Friday 9pm Git history), 'world's best backend' for Vercel AI SDK.
  • 05:20: MCP and code mode teaser: Durable Objects solve stateful connection, code mode exposes 2,600 APIs in 1,000 tokens (Sunil's talk for details).
  • 08:15: Dynamic Workers deep dive: eval++, zero permissions by default, explicit capability grants, M-Dash CMS plugin example, MCP Dev Summit anecdote (startup skepticism vs Lockheed Martin adoption).
  • 10:45: Resumable streaming and multi-tab sync: LLM story refresh example, multiplayer AI vision, ChatGPT lack of shareable links.
  • 12:30: Q&A: Mapping existing work to Cloudflare stack, generative UI (React not JSON), Claude Artifacts analogy.
  • 14:20: Coding agent harness teaser: building Devin/Cursor-style on Workers, extensions implemented 'this morning', OpenClaw comparison, shipping 'imminently'.
  • 16:50: Python/language support: JavaScript and Python first-class, WASM for others (Zig preferred), worker-bundler for NPM dependencies.
  • 18:00: @cloudflare/shell intro: virtual FS on SQLite + R2, usable today, 'dramatic' project history on Sunil's Twitter.
  • 19:30: M-Dash CMS launch: runs on Workers/Durable Objects, Dynamic Workers for plugins, WordPress security contrast.
  • 20:15: Business model: free/cheap tiers structurally viable (hardware near ISPs, bulk bandwidth, peering), $5/month for multi-million dollar SaaS, 'friends and family' free credits.
  • 21:30: Agents week tease: next week (from recording), major announcements coming. Booth on expo floor, Sunil's talk 5:40pm same day, Matt's talk next day.
  • 23:00: Closing: agents.cloudflare.com, github.com/cloudflare/agents, 'have your clanker talk to our clankers'.

Source/Metadata

  • Title: Why Eval++ Is the Next Great Compute Primitive — Sunil Pai & Matt Carrie, Cloudflare
  • Transcript words: 5448
  • Duration seconds: 1490
  • Timestamp note: Timestamps manually created from transcript analysis; video duration 1490 seconds (24:50). Transcript includes some repetition at end (likely transcription artifact).
Search this video Resume transcript at 0%
Full transcript 4676 words · 24 min read
0:00

[SPEAKER_01] Yeah, well, welcome. I'm Matt and this is Sunil. We work on agents at Cloudflare.

0:14

SPEAKER_01

This thing. So yeah, maybe you want to introduce yourself a little bit better than me. This is Matt Carey. I only hire my friends for our team. Say something, make sure it's on the microphone. Yeah, yeah. Is mine on? I keep thinking about Cloudflare as a friends and family company. We love doing favors. [SPEAKER_00] All our closest friends, no one pays for Cloudflare bills, which is already dirt cheap, by the way. It's ridiculous.

0:40

SPEAKER_00

So we started building out AI agents seriously a little over a year ago and it's gone remarkably well. How many folks here are orange-pilled? Which is to say, durable objects. Okay, yeah. Worst named technology, but incredible, right? Everyone's like, it's a database. I'm like, no, but it has a database. [SPEAKER_01] And I'm like, ugh, but we started using that and it turned out to work out really well. There's some unique capabilities about it.

1:07

SPEAKER_01

[SPEAKER_00] Some might call it vendor lock-in, some might call it innovation.

1:15

SPEAKER_00

But, and ever since then, the team has grown. We are based in, most of us are in London. Well, you're British, but you just moved to Lisbon, which is amazing, by the way. Folks, you spend your days drinking wine and you do fish, potatoes, bread. It's just king's life. I live in Newcastle. The weather is way worse, but I do like it. I tried watching Geordie Shore and I regret doing that. I will, no, that's not what I think of. Anyway, so we've been building agents and... Back on topic. Sorry, yes, of course. And I don't know, we can tell you about our journey so far, some of the tech we're using, some of the new upcoming stuff.

1:49

SPEAKER_00

Thankfully, none of this is recorded, so we can tell you about some secret features that are coming out. But I'd love to put it out there for a couple of minutes if you have any questions. Otherwise, we have five topics we thought would be interesting to talk about. But what do you want to know about Cloudflare and AI agents? Tell us about this. Amazing. So it starts with durable objects. Okay, so you know how everyone believes the way you build servers nowadays is you write a function that takes a request and returns a response. Right? Simplest model. And you decide you want to build a hit counter for your website.

2:32

SPEAKER_00

So what you do is you say let x equals zero or let counter equals zero and for every request you say counter plus plus. And it works locally and you deploy it. And it immediately fails. Why does it fail? There's no state. It spins up and does the thing and it disappears. Counter will always be zero. Most times at least. On traffic it might reuse the isolate. So now you have to use a database to store state. You need to do a whole bunch of things. Instead, for a given ID, what if you could have a class that spun up once for a given, spun up once and then every future request, every WebSocket connection lands in the same place.

3:02

SPEAKER_00

So we call this stateful serverless, which is the most confusing thing because servers are stateful. But it works serverless in that it scales across the planet. And because of the Cloudflare magical planetary network, it means in London, you get 15 millisecond latency. For contrast, 60 FPS is 16 milliseconds, a little over 16 milliseconds, which means if you are using, if you folks have used TLDraw, it's built on this tech. [SPEAKER_01] If you open up a bunch of phones on the same shared screen and you start drawing on it, you'll see perfect sync on all phones.

3:44

SPEAKER_01

[SPEAKER_00] I know I'm biased, but so good. Anyway, so it turns out that that's the perfect compute unit for building AI agents as well.

3:52

SPEAKER_00

They're addressable. You can run long running things in it even if there are no requests going to it. They can run in the background. They hibernate. They go to sleep. They have persistence. And they can connect to everything else. So that was the original bet we made. And I wonder if I can scroll down. I wonder if the API is available on this page. Something, something. Marketing, marketing, marketing. Oh yeah, see that's what it looks like. [SPEAKER_02] You basically make a clock. You import from agents. Please don't ask us how much we paid for this NPM package.

4:28

SPEAKER_02

[SPEAKER_00] You extend it and you can add. You're, oh, when it starts up, schedule these things.

4:35

SPEAKER_00

You can make little callables. So agents also comes as a full stack thing. We give you React hooks and, it doesn't have to be React, but I assume. We have plain JavaScript clients as well. You can define things that are actually called from clients. You can run things in the background. There's scheduling is my favorite thing. Because it means you can say stuff, every Friday at 9 PM, look through my entire Git history and my wiki and the Notion. Compile it and send it to my manager. Make sure you mess up the spelling so it looks I wrote it. So you can do all of this. It's nice. And you can, it spins up to millions, trillions, some absurd Cloudflare number.

5:17

SPEAKER_00

That's where it starts. And over the last year, we have built a bunch of things. So we have a first class backend for Vercel's AI SDK. And it turns out the AI SDK is great. Is Nico around here somewhere? No. Anyway. We don't allow Vercel employees into our chat rooms. So it turns out there's a lot more to make it production ready, to do tool calls, to do synchronize, to do resumability, things across tabs. So we have the world's best backend for the AI SDK. I'm saying a lot of things. So we have that. We have, I want to talk to you about code mode, which is, by the way. About maybe this point in the journey, MCP got mega popular around April last year.

6:01

SPEAKER_00

And so it turns out DurableObjects are actually a great way to do MCP servers. Because if you know anything about MCP, when it was originally launched, you needed to have a stateful connection between client and server. And this is one of the most annoying things about deploying MCP servers to production, to the Cloud. And DurableObjects maintain a stateful connection, very, very easy. That's the whole point. And so we jumped on that really early. We had some of the first MCP servers, PayPal, Century. All the big ones are on this. Linear, Intercom, name it. Yeah, all of them. Some we can't name. And yeah, so it turns out that MCP was really, really good for this.

6:43

SPEAKER_00

And this led us down very many more rabbit holes, really, where I think this is our lead into code mode, really. Sure, yeah. Yeah, and then, so then we have, so we have DurableObjects. We have workers, which is a serverless function as a service. And so we jumped on that really early. We had some of the first MCP servers, PayPal, Century. All the big ones are on this. Linear, Intercom, name it. Yeah, all of them. Some we can't name.

7:10

SPEAKER_00

And yeah, so it turns out that MCP was really good for this. And this led us down many more rabbit holes, really, where I think this is our lead into code mode, really. Sure, yeah. Yeah, and then so we have DurableObjects. We have workers, which is a serverless function as a service. A Lambda, you think. Imagine a Lambda was designed 10, 15, 20 years later, something like that. It's better. Then we have this new primitive, which we're calling dynamic workers, where it's a worker, but instead of having to deploy the worker to the Cloud, you can go from one worker and be like, I have this string of code that a customer sent me, or a user sent me, or an LLM generated.

7:55

SPEAKER_00

And I'm going to run that piece of code in its own isolated worker. So from a string, you can run the code. And this breaks a lot of people's brains. I was at MCP Dev Summit last week, and there was a startup next to me. And this guy was just trying to convince me that no enterprise environment would allow people to run generated code that they've never seen. And then someone from Lockheed Martin came up to me and was like, oh, we love code. We love generating code. And the dichotomy was really funny. But basically, you can run people's code that they generate in this thing called a dynamic worker. And we think it's a very good sandbox in the sandbox use of the world.

8:32

SPEAKER_00

Not a VM, not a full, it doesn't have a full file system. It doesn't have all of the VM heaviness, but it is an isolate that you can spin up and you can spin up billions of them. On demand. So that's cool. So anywhere where you want to have user generated code or you previously would use something like a DSL, you would have some JSON file that was generated or was built from some frontends, from some big form. And then you would take that and you would come back to code. Now, just write code. At least I hope this is it. Yeah. So I hate being that guy who's like, oh, you should read my blog. But you should read our blog, by the way.

9:06

SPEAKER_00

The Cloudflare blog, really nice, incredibly technical. The only part where we try to sell you something is where the marketing folks ask us to put a CTA at the very bottom. You can ignore that bit, but everything else is good. We go into details about this. So you know how sandboxes start from a VM or a container and then you try to add security around it. We start the complete opposite way. The only thing you can run is JavaScript in it, but it has no access to fetch, no APIs, nothing. And from the outside you can decide, okay, here are four APIs. And only outgoing fetches to GitHub.com are allowed. GitHub.com slash XYZ or Math.random. I don't know.

9:36

SPEAKER_01

[SPEAKER_00] Some requests fail. [SPEAKER_00] You can write code that does it. [SPEAKER_00] And the way we recommend it is, no, just block outgoing fetches. [SPEAKER_00] You give the sandbox explicit capabilities that you can run in. [SPEAKER_00] No environment variables exposed to any of this code. [SPEAKER_00] You should check this out. Should I do a demo of the MCP server? Can I show the MCP server a bit?

9:53

SPEAKER_00

[SPEAKER_01] No, no, no, no. [SPEAKER_01] Because I'm going to do it in my talk.

9:54

SPEAKER_01

We can tease our talks now. Okay, we get to tease our talks. So basically using this, we claimed that we fixed MCP, not once, maybe twice. And that is both of our talks. [SPEAKER_00] Yours is soothing. 5:40 p.m. I'm giving a talk about code mode, what we call code mode. I have the hat. For people who are asking where you can get code mode hat, we have a careers page on cloudflare.com. And I'm going to talk tomorrow about how you can use code mode in your MCP server to give access to all 2,600 API endpoints of Cloudflare in just 1,000 tokens. So code mode, this idea of being able to generate code that you then run is super powerful.

10:40

SPEAKER_01

I don't think we have enough time here to fully explain how that works. So I would just ask to come to our talks. Yeah, you should have. So the way I've been telling it to people is for the last 30 years, 20 something odd years, you go to being such an old guy in the room so fast. They've told you never to use eval in code. In fact, on Cloudflare workers, eval, you don't have eval. It's dangerous. But we took it and dynamic workers are eval plus plus. So I think about it how there's an entire branch of the tech tree that we haven't explored in 30 years. And now we're giving you a fast, secure, and cheap way. Is there such a thing as fast, good, fast, and cheap? Yeah.

11:15

SPEAKER_01

Maybe it's not good. I don't know. You have to try it out and let us know. It's definitely fast. And you get to reconsider the way you build interfaces and how things happen, especially in a world where all your users can write code. Right? So that's dynamic workers. That's really cool, man.

11:36

SPEAKER_00

[SPEAKER_01] I've been having a lot of fun playing with this. [SPEAKER_01] It's very new. [SPEAKER_01] Should we tease some stuff? [SPEAKER_01] Or do you want to talk about, we had some other releases previously, recently. Go on. Yeah, question. Just a quick one, because I think it sounds like you guys are super, you know, maybe this is just me. I'm struggling to find a way to map all the things that I'm building to this world. I hope I, whether it's just be, I'm trying to find a bridge. So I just want to hear some of what do you think people are building in the industry that they really shouldn't be building it that way. They should be building it this way.

12:03

SPEAKER_00

[SPEAKER_01] Or do you want to talk about some other releases we had recently? Go on. Yeah, question. Just a quick one, because I think it sounds like you guys are obviously super focused, but maybe this is just me. I'm struggling to find a way to map all the things that I'm building to this world. I hope I can find a bridge. So I just want to hear some examples of what you think people are building in the industry that they really shouldn't be building it that way. They should be building it this way. I've got a good anecdote that would be very helpful too. Oh, I'd love to give examples. Okay. Let's give examples.

12:14

SPEAKER_01

[SPEAKER_00] We do one each. [SPEAKER_00] We'll do five each. [SPEAKER_00] Go ahead.

12:23

SPEAKER_00

Okay. So we are here to shill, bro. That's...

12:25

So my favorite example is there's a big thing going around about generative UI at the moment. And people are basically generating JSON, but then you render. Have you heard of JSON render? [SPEAKER_00] Yeah. You're generating JSON, but then you render. Why are you generating JSON? Why don't you just generate HTML or even generate React and then just render that? Well, why can't you do that? [SPEAKER_00] Well, some platforms don't have a primitive to render untrusted code. Well, what happens if you did? You could literally get your users, get your customers, get your agents living in the cloud to generate code that they run that then is rendered in a UI.

12:39

SPEAKER_00

[SPEAKER_01] Like, anyone tried Claude Artifacts? [SPEAKER_01] That's basically... [SPEAKER_01] Yeah, that's it, right? It's just HTML, but it's rendered on your browser.

12:51

SPEAKER_01

So people don't care so much about that security. [SPEAKER_00] What they care about is when they're rendering it on their servers. That's when it starts getting a little bit dodgy. And now they're like, right, you need JSON. You don't need JSON anymore. You could render React. And this is how you build it. So this is one fun thing here. [SPEAKER_00] Yeah, do you want to go to the next one? [SPEAKER_00] Which feature? [SPEAKER_00] Dynamic workers.

13:00

SPEAKER_00

[SPEAKER_04] Dynamic workers. Yeah, yeah, yeah. I'll go a little simpler. Okay, so because our agent thing is more the execution environment than the library you use, like you can use Langchain, AI SDK, anything without agent SDK. We give you that. But because it's this durable object model, it means let's say you wanted to build resumable streaming. Okay, so you tell the LLM, give me a long story. And you hit refresh in the middle of it. How do you make sure it continues streaming? In a serverless world, okay, now you need to do a database, you need to do replication, you need to do sticky sessions.

13:07

SPEAKER_00

[SPEAKER_01] In the durable objects world, in the agent SDK world, you just reconnect to it. And if there's a stream going on, it just says, well, here's the beginning of the stream, and I'm just going to continue giving you bytes. It means that you automatically get multi tabs, multi browser sync.

13:08

SPEAKER_00

[SPEAKER_02] Like you're looking at your phone and the laptop, same time. All of these things come out of the box for you. In fact, the killer use case where we started with durable objects was for building real-time collaborative sync. Now, I'm a believer that AI should be a multiplayer game. Have you noticed, why can I not share a link to my ChatGPT chat with you and both of us work in the same conversation? And it's because OpenAI hasn't built that and they're like, oh, we have bigger problems to solve. Half our people quit every three weeks or something like that.

13:09

SPEAKER_00

[SPEAKER_01] It turns out with primitives like this, you don't have to patch it in user land and become this crazy distributed systems engineer. You make it Cloudflare's problem. [SPEAKER_02] Our problem. Well, I say our problem, but we take credit for the people who actually build it. [SPEAKER_01] We do the JavaScript on top of it. So I really like that. The fact that you get sync streaming, etc. out of the box, it means you can play with, you can build your, you can focus on the things that you care about.

13:18

SPEAKER_04

[SPEAKER_01] That's the killer demo, isn't it?

13:18

SPEAKER_00

I like it so much. Just showing the sync is so fun. Because then it unlocks, they're like, oh, okay, fine. If you can do that, I'm going to worry about making money. It's a fun thing to do. [SPEAKER_01] So would it be fair to say you could rebuild Coda in the phase? [SPEAKER_01] Should we start leaking secrets? [SPEAKER_01] Yeah, we can start leaking secrets. [SPEAKER_01] Okay. Um, yes. Yes. Yes. Yes. Yeah.

13:31

SPEAKER_00

[SPEAKER_01] So there's some cool things you can do here. Because imagine an agent loop that ran in the agent SDK that did the back end of Coda. Now you have a server that runs that's persistent, and you can connect to it from any client. So a terminal, from a chat, from a phone, from an iOS app, from a web app. It doesn't really matter. Everything is synced between all of your clients. Everything is reasonable. Everything is stateful. [SPEAKER_01] So I guess it's up to Cloudflare to now build a harness, right? A coding agent that runs purely on workers and you're, hmm, should we build that? Should we be building this?

13:37

[SPEAKER_01] We're building it, just so we're clear. If I wasn't obvious enough, we hope to ship it imminently. It's just the conference is taking my time away from burning tokens, is what it is. As quickly as I can go back to that. [SPEAKER_01] But no, we believe in that world. Look, everyone's building a harness. And everyone's leaning into the benefits of their infrastructure or their philosophy. This is ours. [SPEAKER_01] A coding agent that runs purely on workers and you're, should we build that? [SPEAKER_01] Should we be building this? We're building it, just so we're clear. If I wasn't obvious enough, we hope to ship it imminently.

14:02

SPEAKER_01

It's just the conference is taking my time away from burning tokens, is what it is. As quickly as I can go back to that.

14:09

SPEAKER_02

[SPEAKER_01] No, but we believe in that world. [SPEAKER_00] Look, everyone's building a harness. [SPEAKER_00] And everyone's leaning into the benefits of their infrastructure or their philosophy. [SPEAKER_00] This is ours. [SPEAKER_00] Where not only do you have these spin-up, spin-down stateful agents, but with capabilities of generating code on the fly and running it instantly. [SPEAKER_00] Really fast. [SPEAKER_00] Resumability, et cetera, out of the box.

14:41

SPEAKER_01

[SPEAKER_00] And if you want to delegate to a big container, you should absolutely be able to do that.

14:49

SPEAKER_02

[SPEAKER_00] We have, our team also handles Sandbox, Cloudflare Sandbox SDK.

14:51

SPEAKER_00

You want to run it in a browser, we have a browser. You really have to use our stuff.

14:55

SPEAKER_01

[SPEAKER_00] You want to use Daytona, a great product, by the way, love their Sandbox stuff. [SPEAKER_00] You want to use browser use, or you want to run, what's the, LightPanda?

14:58

SPEAKER_00

Is that what it's called? You can do that.

15:08

SPEAKER_01

[SPEAKER_00] But workers and our agents SDK becomes the nexus of where it connects to all of the things.

15:10

That's the vision we have. It's happening sooner than later. [SPEAKER_00] How would you then create a cloud flow, particularly one that can create its own skills? [SPEAKER_00] Because I think that, for me, is the thing I love the most. [SPEAKER_00] To be able to just say, send it a voice message, and it starts, I've got a cron, that's a really great thing now. [SPEAKER_00] So we have a bunch of storage solutions. [SPEAKER_00] We have one in the durable object, so we have SQLite directly in the durable object. [SPEAKER_00] So you can store stuff there, you can store stuff in R2, and all of that at the moment you have to kind of wire up.

15:32

SPEAKER_01

[SPEAKER_00] But imminently you won't. [SPEAKER_00] All right, so here's the thing. [SPEAKER_00] What is OpenClaw? [SPEAKER_00] You want a thing that has a heartbeat, you want a thing that has a virtual file system, and you want a thing that's connected to services. [SPEAKER_00] And then control secrets, I can say. [SPEAKER_00] Exactly. [SPEAKER_00] And you want extensions, which means you want to generate code that's run in a safe sandboxed environment. [SPEAKER_00] Exactly. [SPEAKER_00] I implemented extensions this morning. It works really well on our thing. [SPEAKER_00] By the way, I'm friends with Mario. [SPEAKER_00] Hi, Mario. [SPEAKER_00] And yeah, 100%.

16:07

SPEAKER_01

[SPEAKER_00] We love Pi, by the way, the Pi coding agent. [SPEAKER_00] In fact, we want to run Pi directly on workers as well. [SPEAKER_06] We've been talking to him about it, because why not? [SPEAKER_00] But this is the future. Yes, we are working nonstop on this right now. If it wasn't for you people, I'd be burning tokens. Do you have any more questions? [SPEAKER_06] How much time do we have? [SPEAKER_06] I don't even know how long. [SPEAKER_06] I think we're maybe done.

16:41

SPEAKER_00

[SPEAKER_06] There's a lot of JavaScript and React now. [SPEAKER_01] What about other languages? [SPEAKER_01] Would you want Python? [SPEAKER_01] Sure. [SPEAKER_01] Amazing. [SPEAKER_01] So we'll do Python as well. [SPEAKER_01] Dynamic Workers, and workers itself supports Python. [SPEAKER_01] They just need to spend a little time polishing the rough edges. [SPEAKER_01] First class? [SPEAKER_01] Python is first class. JavaScript is first class. Everything else is WASM. The thing we've been playing with lately is Zig. Our boy here is one.

17:24

SPEAKER_00

I think you're the first person to bring Zig into production in Cloudflare Workers for a bunch of things that we actually cannot talk about today. But the nice thing about Zig is the WASM bundles are tiny compared to Go and Rust. So other languages do WASM. Or if it is that important to you to run it natively, you spin up a container instead. Again, we have a first class SDK that lets you spin it up and do things. That being said, brother, your LLM is writing code at this point. Why does it matter, right? Whether it's JavaScript or not. That's my point as well. If you write whatever it wants. Yeah. Yeah, yeah.

18:13

SPEAKER_00

So the infrastructure right now first class is JavaScript Python. And as you could tell, I'm a React programmer. So I'm, Python too hard. But no, we'll polish off those rough edges and we'll do that as well. Hell, we have a thing which lets you run a bundler inside a worker right now. It's literally called worker bundler.

18:33

SPEAKER_01

[SPEAKER_00] It pulls down dependencies from NPM, strips out types, JSX, TypeScript, all of that.

18:36

SPEAKER_00

And generates the thing that you would run inside it. [SPEAKER_07] So fun because then it uses the Cloudflare cache for dependencies instead of worrying about NPM downtime.

18:40

SPEAKER_00

[SPEAKER_07] It's quite nice. [SPEAKER_07] When you said you have to wire up the SQLite storage right now and soon you won't, what do you mean by soon you won't? [SPEAKER_01] No, it actually works.

18:46

SPEAKER_06

[SPEAKER_01] It's called at Cloudflare slash shell.

18:51

SPEAKER_00

[SPEAKER_01] The APIs shouldn't break, but it's usable today.

18:52

SPEAKER_01

It gives you a full file system inside layered on top of both durable object SQLite and R2 for bigger files. [SPEAKER_00] I see. [SPEAKER_00] It works today.

19:00

SPEAKER_06

[SPEAKER_00] You can use it today. [SPEAKER_02] Actually, that's just it. [SPEAKER_00] I don't want to talk about the history of the project. [SPEAKER_00] Anything else?

19:06

SPEAKER_01

[SPEAKER_00] If you search Sunil's name on Twitter, you'll find the history of that project. [SPEAKER_00] Yeah, it was a little dramatic. [SPEAKER_00] Anything else we can help you folks with? [SPEAKER_00] Anyone want free credits? [SPEAKER_00] Friends and family company. [SPEAKER_00] I don't know if you wanted to talk otherwise about the new CMS that we launched last week. [SPEAKER_00] It's called M-Dash. [SPEAKER_00] Great name for a product in this day and age. [SPEAKER_00] It runs fully on workers' durable objects, et cetera.

19:19

SPEAKER_00

And the nice thing about M-Dash is the plugin system is built fully on dynamic workers. So you know how WordPress has a bunch of security incidents because of its plugins? Well, you just lock down where you run the plugins and it just works out of the box. Anything else we can help you folks with? Anyone want free credits? As I said, friends and family company. I don't know if you wanted to talk otherwise about the new CMS that we launched last week. It's called M-Dash. Great name for a product in this day and age. It runs fully on workers' durable objects, etc. And the nice thing about M-Dash is the plugin system is built fully on dynamic workers.

19:54

SPEAKER_00

You know how WordPress has a bunch of security incidents because of its plugins? Well, you just lock down where you run the plugins and it just works out of the box. M-Dash otherwise deploys completely on any platform. It's not Cloudflare specific and we are working on other platform support for this dynamic worker bit that we have right now. Other things is vNext. [SPEAKER_04] We have a version of Next.js that runs fully on wheat and it's so fun to use. [SPEAKER_04] What else do we do? The problem is next week is our agents week. So you'll be seeing a lot from us next week. Twice a year we have these announcement weeks where we get really noisy.

20:15

SPEAKER_00

Next week's is going to be particularly noisy where we announce a bunch of fun stuff. Any more questions? [SPEAKER_03] Go on. How do you become friends in front of us across the—

20:30

SPEAKER_07

[SPEAKER_00] Send account ID and optionally bribes. [SPEAKER_00] You can consider it a bribe or protection money.

20:40

SPEAKER_07

[SPEAKER_00] I'm trying to develop a mafioso vibe around that relationship.

20:49

SPEAKER_01

[SPEAKER_00] The way that Cloudflare is constructed, the reason it's so cheap is because of decisions made 10 years ago. [SPEAKER_00] We don't build massive data centers. [SPEAKER_00] Instead we install hardware near ISPs. [SPEAKER_00] We buy bandwidth in bulk from level zero, top level ISPs.

21:03

SPEAKER_00

And we do agreements where bytes that cross boundaries you don't really pay for it. So our free accounts aren't marketing expenditure. It's just how the business is constructed.

21:07

SPEAKER_02

[SPEAKER_00] And I need more people to know that.

21:08

SPEAKER_00

I spent a bunch of time wondering how they give it out for so cheap. [SPEAKER_05] So it's otherwise $5 a month and we know people building multi-million dollar SaaS on top of that. [SPEAKER_05] But if you want less than $5, well, you'll become friends with us. Other fun stuff we have— We're at time. Is that time? Well, I guess we are at time.

21:27

SPEAKER_00

How's no one knocking at this? I'm so sorry. Especially after we made a thing about the previous session. Thank you so much. We have a booth on the expo floor. I'm speaking today at 5:40 pm. He's speaking tomorrow. [SPEAKER_03] You should watch both talks. I got a haircut for this, you guys. It's going to be fun.

22:10

SPEAKER_04

[SPEAKER_00] Also, just come hang with us. [SPEAKER_03] We love chatting with people. [SPEAKER_00] Agents.cloudflare.com or developers.cloudflare.com/agents for all the docs.

22:21

SPEAKER_00

GitHub.com/cloudflare/agents. You can file issues. We love that. [SPEAKER_01] Have your clanker talk to our clankers. And looking forward to seeing what you build. Thank you.

22:41

SPEAKER_03

Go on.

22:41

SPEAKER_00

How do you become friends in front of us across the- Send account ID and optionally bribes.

22:49

SPEAKER_00

See, you can consider it a bribe or protection money. Like I'm trying to also develop a little like mafioso vibe around that relationship. But no, dude, like we- The way that Cloudflare is constructed, the reason it's so cheap is because of decisions made 10 years ago. We don't build massive data centers. Instead we install hardware near ISPs. We buy bandwidth in bulk from level zero, like top level ISPs. And we do agreements where bytes that cross boundaries you don't really pay for it and stuff. So our free accounts aren't marketing expenditure. It's just how the business is constructed. And I need more people to know that.

23:29

SPEAKER_00

Like I spent a bunch of time, I was like how do they give it out for so cheap?

23:33

SPEAKER_05

So it's otherwise $5 a month and we know people building multi-million dollar like SaaS is on top of that. But if you want less than $5, well, you'll become friends with us.

23:48

SPEAKER_00

Other fun stuff we have- We're at time. Is that time? Oh, well, I guess we are at time. How's no one knocking at this? Oh, you are- I'm so sorry. Especially after we made a thing about the previous session. Thank you so much. We have a booth on the expo floor. I'm speaking today at 5.40 pm. He's speaking tomorrow.

24:06

SPEAKER_03

You should watch both talks.

24:08

SPEAKER_00

Like look at us. Like I got a haircut for this, you guys. It's going to be fun. Also, just come hang with us.

24:15

SPEAKER_03

We love just like chatting with people.

24:19

SPEAKER_00

Agents.cloudflare.com or developers.cloudflare.com slash agents for all the docs. GitHub.com slash cloudflare agents. You can file issues. We love that. That's just it.

24:29

SPEAKER_01

Like have your clanker talk to our clankers.

24:32

SPEAKER_00

And looking forward to seeing what you build.

24:49

SPEAKER_00

Oh, just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just to just

24:50

SPEAKER_00

Thank you.

Reading tools

Type to find a passage

Appearance
Ask this transcript

Notebook

Export Markdown

Add a note