Skip to content
← Public packages

@kentcdodds/cloudflare-connect-personal-software-ecosystem

I Built Your Personal Software Ecosystem: Kent C. Dodds's Cloudflare Connect 2026 lightning talk deck (Reveal.js). How Kody gives every user one of everything on Cloudflare.

FollowForkOpen app

Files

05-one-of-everything.html

21 lines · 1.5 KB · HTML
<section id="one-of-everything" data-slide="one-of-everything" data-title="One of everything, per user">
	<h2>One of everything, per user</h2>
	<ul class="per-user">
		<li><span class="pu-own">Your own npm registry</span><span class="pu-cf">D1 + Workers KV</span></li>
		<li><span class="pu-own">Your own GitHub</span><span class="pu-cf">Artifacts</span></li>
		<li><span class="pu-own">Your own cron</span><span class="pu-cf">Durable Object alarms</span></li>
		<li><span class="pu-own">Your own email address</span><span class="pu-cf">Email Routing</span></li>
		<li><span class="pu-own">Your own database</span><span class="pu-cf">Durable Objects + SQLite</span></li>
	</ul>
	<aside class="notes">
		This is the abstract's opening line, and every row is real. Registry: the package index
		lives in D1, published bundles live in Workers KV keyed by commit, and Vectorize powers
		search. GitHub: every package, job and app is its own Artifacts Git repo, and agents can
		clone and push to it. Cron: one JobManager Durable Object per user schedules jobs with
		alarms. Email: Email Routing delivers to your own address, a Mailbox Durable Object per
		user holds the metadata, R2 holds the raw mail, and Email Sending handles outbound.
		Database: package storage is a StorageRunner Durable Object with its own SQLite.
		Isolation is the rule: per-user Durable Objects use idFromName(userId), D1 rows carry
		user_id, and Vectorize uses one namespace per user. Next: how an agent finds any of it.
	</aside>
</section>