This idea now points to a reviewed repository. The original build proposal is preserved below.
By sardorml
screen recording and share links; editorial use-case mapping, feature parity not verified
Cloudflare Workers, D1 and R2 Standard have free allowances suitable for a small deployment only if its CPU, request, database and media usage fit those limits. A fresh zero-cost deployment has not been verified; paid usage may be needed.
The concept below is preserved for reference. Use the linked project above for its actual features, README and infrastructure.
Browse existing projects and remaining proposals →Async video sharing, transcripts, comments, embeds, and team libraries on Cloudflare.
Async video recording, sharing, transcripts, and comments.
A URL goes in, an API-ready result comes out. These are the stages the request flows through.
If you're paying Loom for any of these, the proposed build would let you stop.
What you'll be able to tune from day one.
Overview inferred from the listed Cloudflare services. Routes and connections have not been verified.
Track crawl jobs, pages, status, users, limits, and API keys.
Store raw HTML, screenshots, markdown output, and crawl artefacts.
Use Stream for the part of the owned app that needs this platform capability.
Public API, routing, auth checks, rate limits, and orchestration glue.
Classify pages and extract structured fields when deterministic parsing is not enough.
This candidate asks whether Loom can be replaced by a smaller owned workflow on Cloudflare without pretending to cover the whole enterprise product.
The core Loom workflow is record elsewhere or in-browser, upload, transcribe, share, comment, and embed.
Use D1, R2, Stream, Workers, Workers AI to cover the core workflow without adding rented infrastructure.
Good for simple async video libraries and internal demos. Browser recording polish and enterprise video collaboration should stay out of the first build.
Discussion · 0
sign in to comment →