<- all tokdocs
2026.10.01@isaacdyor

Cloudflare would need $1,404 a share to be worth $500 billion; its own filings say $105.5 billion, and the Dynamic Workers the video calls the future cap you at four concurrent sandboxes

Finance
Watch on TikTok

View on TikTok ->

The artifact is a 104.277007 s MP4 (container mov,mp4,m4a,3gp,3g2,mj2, format id bytevc1_1080p_421227-1) running 5,490,593 bytes at an overall 421,231 bps, confirmed by ffprobe rather than metadata alone: the video stream is HEVC Main, level 150, yuv420p, 1080x1920, 30/1 fps, 3,126 frames, 350,683 bps, and the audio stream is AAC HE-AACv2, 44,100 Hz, stereo, 64,101 bps, 2,249 frames, with the video stream running 104.200 s against the container's 104.277007 s. The timestamp field is epoch 1790841270, which is 2026-10-01T07:54:30Z. The uploader is isaacdyor (uploader_id 7236064524410373166, nickname "Isaac Dyor"), the audio credit is "original sound" by Isaac Dyor, and the 78-character description reads "Cloudflare will be a $500 billion company. Here's the tech that gets it there." At the capture time recorded by the mtime of metadata.json, 2026-10-19 06:08:33 local, the counters read 1,587 views, 87 likes, 3 comments and 6 reposts. I read 16 of the 52 extracted frames (001, 004, 008, 012, 016, 020, 024, 025, 026, 028, 032, 036, 041, 045, 049, 052, at 2 s intervals starting at 0 s) plus four extra stills pulled at 48.6 s, 49.2 s, 49.3 s and 49.4 s to catch an animating counter, against a 369-word transcript in 21 segments. Frame 001 (0 s) shows a black motion-graphics card reading "Cloudflare will be a / $500 billion company." over a "Cloudflare, Inc. / NYSE: NET" stock chart tooltip reading "158.04 USD May 23, 2025", with a hand-drawn black arrow extrapolating upward past the green price line, and the speaker in a brown hoodie with white wired earbuds in a picture-in-picture box. Frame 004 (6 s) overlays two props on that chart: a terminal titled ~/my-ai-app reading "$ npx wrangler deploy / Uploading... done / ✓ Live on 330+ cities", and a document card reading "FORM 10-Q · Q2 2026 / Quarterly financials" stamped "NEVER OPENED". Frame 008 (14 s) is a locked five-card grid labelled "5 REASONS", "the default cloud for AI", "REASON 01 LOCKED" through "REASON 05 / THE BIG ONE". Frame 012 (22 s) is headed "REASON 01 / 05 · ISOLATES" with a "LAMBDA" row stamped "COLD START", "ready", "1,000 ms", and a "WORKERS" row showing "0.0 ms". Frames 016 and 020 (30 s and 38 s) are headed "REASON 02 / 05 · CPU BILLING" with a 0 s to 30 s scrubber labelled "1 AI request", then "waiting on the model…", "97% WAITING", and "AWS bills 30.0 s" stamped "ALL OF IT". Frames 024, 025 and 026 (46 s, 48 s, 50 s) are headed "REASON 03 / 05 · R2" and animate an "Amazon S3 / 100 TB / month" card with "EGRESS · $0.09 / GB" counting from $308 to $7,919, against a "Cloudflare R2 / 100 TB / month" card reading "EGRESS · $0 / GB" and "$0". Frames 028, 032 and 036 (54 s, 62 s, 70 s) are headed "REASON 04 / 05 · DURABLE OBJECTS" and show an "agent · user_8f3a" card marked "AWAKE" with "OWN SERVER", "BUILT-IN DB" and a "MEMORY" panel ("prefers: aisle seat", "todo: book flights ✓"), then a grid captioned "328,529 agents". Frames 041, 045 and 049 (80 s, 88 s, 96 s) are headed "REASON 05 / 05 · DYNAMIC WORKERS" and show an "app.js · written by AI" editor stamped "⚠ UNTRUSTED" containing const h = await env.DB.get("habits"); return render(h), a padlocked sandbox panel reading "running", "~5 ms", "↺ same isolates as 01", check pills reading "way faster" and "way cheaper", and a finished "Habits / ISAAC / 12 day streak" mini app. Frame 052 (102 s) closes on a card reading "The future of software." above five green check pills: "Isolates", "CPU billing", "R2", "Durable Objects", "Dynamic Workers". Spoken, the argument is that five primitives the speaker has used but never financially modelled, isolates, CPU-time billing, free R2 egress, Durable Objects and Dynamic Workers, will make Cloudflare the default cloud for AI and carry it to a $500 billion valuation. The transcript's last segment is timestamped 101.68 s to 107.44 s, which ends 3.16 s past the 104.277007 s of real audio; the words "this is the future of where software is heading" start inside the audio, so the text is real and only the closing timestamp overruns, but nothing timestamped after 104.277 s should be quoted as spoken.

The $500 billion figure is a stated opinion, and Cloudflare's own 10-Q puts the baseline at about $105.5 billion

At 0.08 s the video opens with "cloudflare is going to be a 500 billion dollar company i have never looked at the financials". Frame 004 turns that into a joke prop, stamping a "FORM 10-Q · Q2 2026" card "NEVER OPENED". Take the speaker at his word and treat the number as a forecast rather than a fact, because it is one. Here is the baseline he skipped.

The cover page of Cloudflare's Form 10-Q for the quarter ended June 30, 2026 reports 322,618,775 shares of Class A common stock and 33,460,940 shares of Class B common stock outstanding as of July 21, 2026, for a combined 356,079,715 shares. Third-party market data put NET's close on Friday, October 16, 2026 at $296.30, which multiplies out to roughly $105.5 billion of market capitalisation. That price is the one weak link in the chain, since I could not reach a first-party quote source, so treat the close as third-party and the share count as primary. Trackers reporting market cap directly land at about $104.7 billion for the same date, which is consistent.

Against the share count in the filing, a $500 billion market capitalisation requires $1,404.18 a share, a 4.74x move from the October 16 close. On revenue the gap is wider. Cloudflare's August 6, 2026 release guides full-year 2026 revenue to $2,864.0 million to $2,870.0 million. At the midpoint, today's market capitalisation is about 36.8 times guided revenue, and $500 billion would be about 174 times it. The underlying business is growing fast and losing money: second-quarter revenue of $696.061 million, up 36% year over year from $512.316 million, GAAP gross profit of $499.517 million at 71.8% margin, a GAAP loss from operations of $205.7 million (29.6% of revenue), a GAAP net loss of $170.0 million, and free cash flow of $56.4 million. The 10-Q attributes growth to paying customers above $100,000 of annualised revenue rising to 4,698 from 3,712 a year earlier, on a dollar-based net retention rate of 120%. Cash and equivalents stood at $1,663,773 thousand with $2,499,025 thousand of available-for-sale securities as of June 30, 2026.

None of that makes $500 billion impossible. It does mean the claim is a 4.7x re-rating of a company still posting a GAAP operating loss, presented as settled.

Isolates do start in milliseconds, but Cloudflare's own docs never say five, and Chrome separates tabs with processes

At 19.28 s the video says "on aws your code runs in a container that has to boot up before it does anything which should take up to a second cloudflare runs it in an isolate", and at 23.36 s, "the same thing that chrome uses to keep your tabs separate which starts in five milliseconds". Frame 012 renders this as "LAMBDA ... 1,000 ms" against "WORKERS ... 0.0 ms".

The direction is right and Cloudflare's own documentation supports it, in looser terms. The Workers "How Workers works" page describes isolates as "lightweight contexts that provide your code with variables it can access and a safe environment to be executed within" and says "any given isolate can start around a hundred times faster than a Node process on a container or virtual machine", adding that "on startup isolates consume an order of magnitude less memory". The September 26, 2025 Code Mode post says "an isolate can start in a handful of milliseconds using only a few megabytes of memory" and that "isolates are far more lightweight than containers". No Cloudflare page I fetched states five milliseconds. The specific number in the transcript and the "~5 ms" badge in frame 045 are the video's, not Cloudflare's.

The Lambda side is understated rather than overstated. AWS's SnapStart documentation says initialization operations "can sometimes take several seconds to complete during the initial invocation" and positions SnapStart as a way to "reduce this latency from several seconds to as low as sub-second". So "up to a second" is optimistic for a cold Java or .NET function. The same page notes AWS sells a fix: provisioned concurrency "keeps Event Functions initialized and ready to respond in double-digit milliseconds".

The Chrome analogy is the part that is wrong. Chromium's Site Isolation design document states the goal plainly: "our goal is to ensure a renderer process can be limited to contain pages from at most one web site", using "a site-per-process policy ... to improve Chrome to use sandboxed renderer processes as a security boundary between web sites". Chrome does run V8 isolates, but what keeps one site's pages away from another's is an operating-system process boundary, not the isolate. The video attributes tab separation to the wrong mechanism.

One more omission matters for the framing. Cloudflare sells containers too. Its changelog entry dated April 13, 2026 announces that "Cloudflare Containers and Sandboxes are now generally available" on the Workers Paid plan, and the Containers platform documentation states that "container cold starts can often be in the 1-3 second range, but this is dependent on image size and code execution time, among other factors". The 1,000 ms cold start the video uses to attack AWS is also what Cloudflare's own container product documents, and worse.

The CPU-billing claim is correct and the docs say so plainly, but Durable Objects bill wall-clock time

At 27.60 s the video says "aws charges you for the whole time your code is running even if it's just sitting there waiting and that's most of what ai apps do", and at 42.56 s, "on cloudflare you only pay for the tiny amount of time that you're actually making the request". Frames 016 and 020 animate this as a 30-second AI request, "97% WAITING", and "AWS bills 30.0 s" stamped "ALL OF IT".

Both halves check out. AWS Lambda's pricing page defines the metered unit as follows: "Duration is calculated from the time your code begins executing until it returns or otherwise terminates, rounded up to the nearest 1ms", at $0.0000166667 per GB-second for x86 on-demand in the first tier. That is wall-clock time, so a function blocked on a model response is billed for the block.

Cloudflare's Workers limits page states the opposite rule in one sentence: "CPU time measures how long the CPU spends executing your Worker code. Waiting on network requests (such as fetch() calls, KV reads, or database queries) does not count toward CPU time." The Workers Paid plan bills 10 million requests per month plus $0.30 per additional million, and 30 million CPU milliseconds per month plus $0.02 per additional million CPU milliseconds, with a default 30-second CPU limit per invocation configurable to five minutes.

The problem is that the video then recommends Durable Objects for exactly the waiting-heavy agent workload, and Durable Objects are billed the other way. The Durable Objects pricing page states that "duration is billed in wall-clock time as long as the Object is active and not eligible for hibernation", and that "pending I/O operations keep an object in memory for up to 15 minutes each. The object incurs duration charges during that time." An agent Durable Object sitting on an open fetch to a model provider has pending I/O, is therefore not eligible for hibernation, and is billed wall-clock GB-seconds at $12.50 per million GB-seconds after 400,000 included per month. The CPU-billing advantage the video sells in reason 02 does not survive contact with the primitive it sells in reason 04.

R2 egress really is free, and the graphic's own counter uses AWS's tiered math its label contradicts

At 47.28 s the video says "aws charges you every time someone downloads a file from s3 cloudflare's version r2 charges zero for that so object storage is way cheaper on cloudflare".

The egress half is verified. Cloudflare's R2 pricing page lists "Egress (data transfer to Internet) | Free" for both Standard and Infrequent Access classes and states that "egressing directly from R2 ... does not incur data transfer (egress) charges and is free".

R2 is not free, though, and the video never says what you do pay. Standard storage is $0.015 per GB-month, Class A operations are $4.50 per million requests and Class B operations are $0.36 per million, with a free tier of 10 GB-month of storage, one million Class A and ten million Class B operations per month. A read-heavy AI workload pays R2 on operations even while paying nothing on bandwidth.

The on-screen graphic deserves credit the narration does not claim. Frames 024 and 025 label the S3 card "EGRESS · $0.09 / GB" over "100 TB / month", and the counter animates from $308 at 46 s through $7,919 at 48 s. Pulling extra stills, it reads $7,580 at 48.6 s and $7,984 at 49.2 s before the card scrolls away at about 49.3 s. A flat $0.09 per GB across 100 TB would be $9,216. AWS's own S3 pricing page bands internet egress as "First 10 TB / Month", "Next 40 TB / Month", "Next 100 TB / Month" and "Greater than 150 TB / Month", with the first 100 GB per month free; the pricing feed that page loads returns $0.09, $0.085, $0.07 and $0.05 per GB for those bands in US East (N. Virginia). Applying those tiers to 100 TB at 1,024 GB per TB gives $7,987.20, which is where the counter was heading. The animation ran correct tiered math under an incorrect flat-rate label.

Durable Objects do hibernate for free, with a 10 GB ceiling, single-threaded execution and a soft 1,000 request-per-second limit

At 53.44 s the video calls Durable Objects "the best way to deploy agents period", and at 58.80 s says each agent "gets its own tiny server with a database built in it remembers everything sleeps for free when nobody's using it and wakes up instantly", then at 64.72 s, "they're also infinitely scalable because every new agent is just a new do you don't have to scale server".

The sleeping claim is accurate. Cloudflare's Durable Objects pricing page states that "Durable Objects that are idle and eligible for hibernation are not billed for duration, even before the runtime has hibernated them", and that "the WebSocket Hibernation API can dramatically reduce duration-related charges for Durable Objects communicating with clients over the WebSocket protocol, especially if messages are only transmitted occasionally at sparse intervals". The built-in database is the SQLite backend, and storage is billed separately from duration at $0.20 per GB-month after 5 GB, $1.00 per million rows written after 50 million, and $0.001 per million rows read after 25 billion. Requests are $0.15 per million after one million. Sleeping is free on duration; the data the agent remembers is not free.

"Infinitely scalable" needs three caveats the video omits, all from Cloudflare's own limits page. Storage per Durable Object is capped at 10 GB, with a maximum string, BLOB or table row size of 2 MB. CPU per request defaults to 30 seconds and is configurable to five minutes. And each object is a serial bottleneck: "each individual Object is inherently single-threaded", with a soft ceiling around 1,000 requests per second per object before overload errors. The number of objects is unlimited, so the architecture does scale horizontally, which is the video's actual point. Any single agent, though, is one 10 GB single-threaded box, and that is a design constraint, not a footnote.

Dynamic Workers reached open beta in March 2026 and allows four concurrent in-flight sandboxes, not "tons"

At 75.44 s the video names "dynamic workers" as the most interesting primitive, at 80.32 s describes them taking "untrusted code written by ai and run it in its own isolated sandbox in milliseconds", and at 96.48 s concludes "your agent can spin up tons of different mini applications just for you".

The product is real. The Worker Loader API behind it appeared in the Code Mode blog post of September 26, 2025, which said "the Dynamic Worker Loader API is in closed beta". Cloudflare's changelog entry of March 24, 2026 announced that "Dynamic Workers are now in open beta for all paid Workers users", describing a Worker that can "spin up other Workers, called Dynamic Workers, at runtime to execute code on-demand in a secure, sandboxed environment" and claiming they "start in milliseconds". So as of the video's October 1, 2026 post date this was open beta on paid Workers, not generally available. The sandboxing claim is supported: the Dynamic Workers overview says you can "securely sandbox code you do not trust" and control "which bindings it receives, whether it can reach the network, and more", and the Code Mode post argues that bindings "hide API keys ... This means that the AI cannot possibly write code that leaks any keys".

The limit the video omits is the one that bears directly on its closing argument. Cloudflare's Dynamic Workers limits page caps concurrent Dynamic Workers with in-flight requests at 4 from a Worker request context and 10 from a Durable Object context, noting that "multiple in-flight requests to the same Dynamic Worker count as one toward this limit". You can create many Dynamic Workers over time, and get(id, callback) caches one by ID so it stays warm across requests, but you cannot have an agent running "tons of different mini applications" in flight at once. Four, or ten inside a Durable Object, is the documented ceiling today. The video's most interesting primitive is also its most constrained.

Key Takeaways

  • Context: The $500 billion number is the speaker's forecast and he says so at 0.08 s ("i have never looked at the financials"). It is opinion, not a reported figure.
  • Correction: The Q2 2026 10-Q lists 356,079,715 shares outstanding as of July 21, 2026. At the October 16, 2026 close of $296.30, that is about $105.5 billion. $500 billion needs $1,404.18 a share, a 4.74x move, and about 174 times the midpoint of Cloudflare's own $2,864.0 to $2,870.0 million 2026 revenue guidance.
  • Correction: At 23.36 s the video calls isolates "the same thing that chrome uses to keep your tabs separate". Chromium's Site Isolation document says separation is enforced by sandboxed renderer processes under a "site-per-process policy", not by V8 isolates.
  • Partial correction: No Cloudflare source I fetched states a five-millisecond isolate start. The docs say "around a hundred times faster than a Node process on a container or virtual machine" and "a handful of milliseconds". The order of magnitude holds; the number is the video's.
  • Partial correction: "Up to a second" for a container cold start understates both sides. AWS says initialization "can sometimes take several seconds", and Cloudflare's own Containers docs, GA since April 13, 2026, say cold starts "can often be in the 1-3 second range".
  • Verified: Lambda bills wall-clock duration, "calculated from the time your code begins executing until it returns or otherwise terminates, rounded up to the nearest 1ms". Workers do not: "waiting on network requests ... does not count toward CPU time."
  • Correction: That advantage does not carry to the Durable Objects the video recommends for agents. Their pricing page says "duration is billed in wall-clock time as long as the Object is active and not eligible for hibernation", and pending I/O keeps an object billable in memory for up to 15 minutes.
  • Verified: R2 egress is free, and idle hibernation-eligible Durable Objects are not billed for duration. Both claims match Cloudflare's pricing pages verbatim.
  • Clarification: R2 still charges $0.015 per GB-month of Standard storage and $4.50 / $0.36 per million Class A / Class B operations. Durable Objects still charge $0.20 per GB-month of stored data. The video mentions neither.
  • Clarification: The S3 counter labelled "$0.09 / GB" reaches $7,984 at 49.2 s, matching AWS's tiered math ($7,987.20 for 100 TB), not a flat $0.09 per GB ($9,216). The animation is more accurate than its own label.
  • Clarification: "Infinitely scalable" at 64.72 s omits that each Durable Object caps at 10 GB, is "inherently single-threaded", and has a soft ceiling near 1,000 requests per second. Unlimited objects, bounded objects.
  • Correction: Dynamic Workers cannot run "tons of different mini applications" at once. Cloudflare caps concurrent Dynamic Workers with in-flight requests at 4 from a Worker request context and 10 from a Durable Object context.
  • Clarification: At the October 1, 2026 post date, Dynamic Workers were in open beta for paid Workers users per the March 24, 2026 changelog, not generally available. The underlying Worker Loader API was closed beta when introduced on September 26, 2025.
  • Unverified: The "328,529 agents" counter in frame 036 and the "158.04 USD May 23, 2025" tooltip in frame 001 are props with no cited source. I traced neither.
  • Context: The transcript's last segment ends at 107.44 s against 104.277007 s of audio, a 3.16 s overshoot. The words start inside the audio, so the text is sound and only the closing timestamp is a Whisper artifact.

Resources

Published October 1, 2026. Writeup generated from a favorited TikTok.