Skip to content
← Public packages

@kentcdodds/cloudflare-connect-pse-hyperframes

I Built Your Personal Software Ecosystem: Kent C. Dodds's Cloudflare Connect 2026 talk deck, built with HyperFrames. How Kody gives every user one of everything on Cloudflare.

FollowForkOpen app

Files

14-cloudflare-runtime.html

35 lines · 2.9 KB · HTML
<section data-id="cloudflare-runtime" data-label="One user's Kody: runtime" class="slide rt">
	<style>
		.rt .src { flex-direction: row; gap: 16px; min-width: 380px; --accent: var(--sky); }
		.rt .fleet { min-width: 340px; padding: 30px 40px; }
		.rt .svc { width: 470px; align-items: flex-start; text-align: left; gap: 4px; padding: 20px 32px 22px; border-color: color-mix(in srgb, var(--accent) calc(45% + var(--glow) * 55%), var(--line)); }
		.rt .svc .t { font-size: 42px; gap: 16px; }
		.rt .svc .t .ico { font-size: 44px; }
		.rt .svc .d { font-size: 32px; padding-left: 60px; }
	</style>
	<h2 data-enter>One user's Kody: runtime</h2>
	<div class="stage" data-enter>
		<svg class="wires" aria-hidden="true">
			<path class="wire" data-name="in" data-from="src" data-to="fleet"></path>
			<path class="wire" data-name="loaders" data-from="fleet" data-to="loaders" data-route="hvh"></path>
			<path class="wire" data-name="workflows" data-from="fleet" data-to="workflows" data-route="hvh"></path>
			<path class="wire" data-name="queues" data-from="fleet" data-to="queues" data-route="hvh"></path>
			<path class="wire" data-name="email" data-from="fleet" data-to="email" data-route="hvh"></path>
		</svg>
		<div class="node src" data-node="src" style="left: 230px; top: 370px"><span class="t"><span class="ico ico-claude" data-src-icon></span><span data-src-label>Your agent</span></span></div>
		<div class="node fleet cf" data-node="fleet" style="left: 780px; top: 370px"><span class="t"><span class="ico ico-cloudflare"></span>Workers</span><span class="d">the Kody fleet</span></div>
		<div class="node svc cf" data-node="loaders" style="left: 1400px; top: 85px"><span class="t"><span class="ico ico-cf-workers"></span>Worker Loaders</span><span class="d">run your code</span></div>
		<div class="node svc cf" data-node="workflows" style="left: 1400px; top: 275px"><span class="t"><span class="ico ico-cf-workflows"></span>Workflows</span><span class="d">long-running work</span></div>
		<div class="node svc cf" data-node="queues" style="left: 1400px; top: 465px"><span class="t"><span class="ico ico-cf-queues"></span>Queues</span><span class="d">events, webhooks</span></div>
		<div class="node svc cf" data-node="email" style="left: 1400px; top: 655px"><span class="t"><span class="ico ico-cf-email"></span>Email Routing</span><span class="d">your address</span></div>
	</div>
	<p class="brand">kody.codes</p>
	<aside class="notes">
		Cloudflare is the whole platform. Your agent, from any MCP host, talks to the Kody worker
		fleet on Workers: the main worker plus the platform, runtime and jobs workers, joined by
		service bindings. Worker Loaders mint the Dynamic Workers that run execute calls and
		package apps. Workflows carry long-running work through workflows.create. Queues fan out
		webhook dispatch, package events and email delivery events. Email Routing gives every
		user a real address, and Email Sending handles outbound.
	</aside>
</section>