id: investigate: Cloudflare Workers edition — isolates + Durable Objects + per-user SQLite fit for ID

LIST 12a. ID needs a version that runs with NO container or conventional server: Cloudflare Workers isolates + Durable Objects + SQLite stores, acting as actual servers — 'or technically peer-to-peer servers, sort of'. Today none of ID runs on Workers isolates. Investigate what of ID's core (identity, graph store, relay, app hosting) maps onto isolates/DO/SQLite and what does not. Related prior art: #793 (pkarr on Workers, deferred) — build on it, don't duplicate it. Deliverable: component-by-component fit map.

Program: Drew's 2026-10-28 directive (full text: hatch-personal memory/topics/id-program-2026-10-28.md).
Working pattern: parallel investigations, then the named synthesis issue merges them into a full design. Route guidance: Workhorse by default; Specialist/Summit for synthesis and ramification-heavy work. A result that says "done" is not the endpoint — the orchestrator reviews it and may commission another round. Deliverables: a markdown design/investigation doc (mermaid/SVG diagrams welcome) linked from this issue, plus follow-up issues for anything buildable. Build a proof of concept where the design calls for one, but do NOT build the permanent feature on top of an unreviewed PoC.

CODE-965

Parent epic: #2056 — ID platform expansion (2026-10-28 directive).

Investigation COMPLETE (2026-10-28, Muse research pass; full report lands in-repo via the program docs PR — local copy: ~/workspace/id-program-2026-10-28/investigations/cloudflare-workers-fit.md, 489 lines, cited to Cloudflare/Google official docs; component names grounded in the actual pkgs/id tree).

Verdict: a Workers edition is feasible only as an HTTP/WebSocket-shaped subset — a hosted per-user home server, not a port of the Iroh node.

Per-user Durable Object works as the user's server+DB+live sockets: SQLite storage 10 GB/object (Paid), WebSocket Hibernation means idle users cost ~~storage only (~~$0.02/mo for a 100 MB store). Rules: hibernating sockets only, batch journal writes, never journal ephemeral traffic.
Hard wall: no UDP API and no inbound listening in Workers — Iroh/QUIC cannot execute in an isolate. The hosted edition speaks ID semantics (signed objects, graph, journals) over HTTPS/WS with a bridge to native nodes (id: investigate: bridge semantics — hosted (HTTPS/WS) edition syncing with native Iroh nodes #2058); signatures are transport-independent, so the trust model survives.
Per-user SQLite: DO-SQLite beats D1-per-user decisively (D1 caps at 50,000 databases/account and still needs a DO in front). D1's role: one shared directory DB. Blobs go to R2.
Google SSO: standard OIDC; key on Google's immutable sub, never email. SSO does not bind the ID keypair — signed claim binding recommended, custodial keys rejected (recovery design: id: investigate: key recovery for hosted users — Google SSO loss vs the ID keypair #2060).
Fit map: 20 pkgs/id components mapped fits / fits-with-changes / does-not-fit (does-not-fit: Iroh transport, SSH world rendering, BitTorrent-style swarming on the hosted leg). Follow-ons filed: id: investigate: world-VM Wasm portability audit — what of the worlds runtime runs inside a Worker #2057 (world-VM Wasm portability), id: investigate: hot-world sharding — when one world outgrows one Durable Object #2059 (hot-world sharding), id: investigate: Durable Object jurisdiction / data-location pinning for per-user stores #2061 (jurisdiction pinning).

docs(id): 2026-10-28 program investigations — TigerBeetle + Cloudflar…

🤖 Agent note · done

Agent: queue worker (repo-worker-code), Lane B
Session / ID: queue task 7846
Found via: queue claim (coverage triage)
Task: Triage id: investigate: Cloudflare Workers edition — isolates + Durable Objects + per-user SQLite fit for ID #2044 (ID Cloudflare Workers edition investigation) at current state.
Expectation: done as below.
Links: synthesis id: design: ID serverless edition v1 (Cloudflare Workers) #2046 · parent epic epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056 · prior art id phase-7: P7.2 Cloudflare Workers pkarr — implementation and deployment are deferred with no tracking issue #793

Triage verdict (2026-11-03) — investigation already complete; routed into the #2046 synthesis; no new work owed here

The investigation this issue commissions was completed on 2026-10-28 and its verdict is posted on this issue: a Workers edition is feasible only as an HTTP/WebSocket-shaped per-user home-server subset (per-user Durable Object + SQLite; no UDP/inbound listening, so Iroh/QUIC cannot run in an isolate; bridge to native nodes carries ID semantics).
The component-by-component fit map (20 pkgs/id components: fits / fits-with-changes / does-not-fit) was delivered with that pass (report: ~/workspace/id-program-2026-10-28/investigations/cloudflare-workers-fit.md, 489 lines).
Every follow-on it filed is now CLOSED: id: investigate: world-VM Wasm portability audit — what of the worlds runtime runs inside a Worker #2057 (world-VM Wasm portability), id: investigate: bridge semantics — hosted (HTTPS/WS) edition syncing with native Iroh nodes #2058 (bridge), id: investigate: hot-world sharding — when one world outgrows one Durable Object #2059 (hot-world sharding), id: investigate: key recovery for hosted users — Google SSO loss vs the ID keypair #2060 (key recovery), id: investigate: Durable Object jurisdiction / data-location pinning for per-user stores #2061 (jurisdiction pinning). Prior art id phase-7: P7.2 Cloudflare Workers pkarr — implementation and deployment are deferred with no tracking issue #793 is CLOSED (deferred with prejudice recorded there).
What remains is the program's named synthesis: design issue id: design: ID serverless edition v1 (Cloudflare Workers) #2046 (ID serverless edition v1, Cloudflare Workers), OPEN under parent epic epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056, OPEN. Per the program pattern in this issue's body, the synthesis — not this investigation — is the live endpoint.

Blockers/ordering: none. No follow-up packet is owed from this issue; it stays open under epic #2056 until the #2046 synthesis consumes it, at which point it can close as superseded by the design.

agent-note:v1
state: triaged (coverage pass)
Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 30 (priority/none). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
Found via: coverage pass 2026-11-03

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-f
Session / ID: task 8587
Found via: queue claim
Task: Handed off to the opencode execution lane; the laptop claimant launches the bound opencode session, which drives task 8587 to its terminal state. Fresh revalidation: issue id: investigate: Cloudflare Workers edition — isolates + Durable Objects + per-user SQLite fit for ID #2044 is OPEN, no hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit absent).
Expectation: effort s; done = worked per the task packet for issue id: investigate: Cloudflare Workers edition — isolates + Durable Objects + per-user SQLite fit for ID #2044 at current main, verified terminal state.
Links: issue id: investigate: Cloudflare Workers edition — isolates + Durable Objects + per-user SQLite fit for ID #2044

🤖 Agent note · picked up

Agent: repo-worker-code (openchamber scheduled lane)
Session / ID: queue task 8587 · lane 8ac61616-3815-4e7b-b33d-840a3829154a
Found via: safety-net queue claim; issue id: investigate: Cloudflare Workers edition — isolates + Durable Objects + per-user SQLite fit for ID #2044 is OPEN with queue labels
Task: revalidate whether the Workers-fit investigation still needs a follow-up
Prior work: queue task 7846 already verified the investigation report and routed its result to design issue id: design: ID serverless edition v1 (Cloudflare Workers) #2046
New evidence: id: design: ID serverless edition v1 (Cloudflare Workers) #2046 is now CLOSED after the synthesis landed in PR design(id): #2046 Workers v1 architecture #3827; the design doc is present on current main, and downstream build work remains tracked separately (id: implement hosted provisioning + SSO→ID binding (from spec #2258) #2852, id: implement hosted Worker API + per-user DO provisioning and metering (from #2046/#2852 slice 3) #3811)
Next: close id: investigate: Cloudflare Workers edition — isolates + Durable Objects + per-user SQLite fit for ID #2044 as superseded by the completed synthesis; do not repeat the investigation or enqueue a duplicate follow-up

Triage verdict — resolved as superseded (2026-11-03)

The requested investigation and component fit map are already complete; this issue work has been consumed by the serverless-edition synthesis. Closing #2044 as superseded by that synthesis, not by age.

Investigation report: the 20-component fit map and findings are in the merged program research (PR docs(id): 2026-10-28 program investigations — TigerBeetle + Cloudflare Workers fit #2067); the result is recorded on this issue. Workers fit an HTTP/WebSocket-shaped hosted subset using per-user Durable Objects + SQLite and R2, not an Iroh/QUIC port.
Synthesis: id: design: ID serverless edition v1 (Cloudflare Workers) #2046 is CLOSED after design PR design(id): #2046 Workers v1 architecture #3827 merged as c3d27d0a47863dec0f00e978e1145caec6a3594c; doc/2026-11-01_design_id2046.md is present on current main f34b6fd4e980b252419d01af6fbbd4dff00e6ef6.
Build work remains tracked separately under id: implement hosted provisioning + SSO→ID binding (from spec #2258) #2852 and id: implement hosted Worker API + per-user DO provisioning and metering (from #2046/#2852 slice 3) #3811; no duplicate follow-up packet is needed from this investigation. Prior triage task 7846 correctly left this issue open while id: design: ID serverless edition v1 (Cloudflare Workers) #2046 was pending; that condition is now resolved.

🤖 Agent note · done (superseded)

Agent: repo-worker-code (openchamber scheduled lane)
Session / ID: queue task 8587 · lane 8ac61616-3815-4e7b-b33d-840a3829154a
Outcome: investigation already done and consumed by the completed synthesis; issue closed as superseded
Follow-up: none from id: investigate: Cloudflare Workers edition — isolates + Durable Objects + per-user SQLite fit for ID #2044; existing downstream implementation issues remain canonical

Navigation Menu

Repository navigation

id: investigate: Cloudflare Workers edition — isolates + Durable Objects + per-user SQLite fit for ID #2044

Triage verdict (2026-11-03) — investigation already complete; routed into the #2046 synthesis; no new work owed here

1 remaining item

Triage verdict — resolved as superseded (2026-11-03)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id: investigate: Cloudflare Workers edition — isolates + Durable Objects + per-user SQLite fit for ID #2044

Description

Activity

developing-today commented on Oct 29, 2026

dezren39 commented on Oct 29, 2026

dezren39 commented on Oct 29, 2026

dezren39 commented on Nov 3, 2026

Triage verdict (2026-11-03) — investigation already complete; routed into the #2046 synthesis; no new work owed here

1 remaining item

developing-today commented on Nov 3, 2026

dezren39 commented on Nov 3, 2026

dezren39 commented on Nov 3, 2026

dezren39 commented on Nov 3, 2026

Triage verdict — resolved as superseded (2026-11-03)

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions