Case study
Ralink
A production file-sharing system with time-limited links, built on Cloudflare’s edge platform with a focused SvelteKit frontend.
Edge runtime
Cloudflare Workers
Storage
R2 object storage
Status
Production
Product screenshots coming soon
Problem
Files needed to be shared securely on the web with time-limited access — without dedicated servers or idle infrastructure.
Approach
We designed the backend first on Cloudflare Workers, R2, and D1 — APIs, file storage, and link metadata with expiration — then built a focused SvelteKit frontend on Pages.
Architecture
Workers API → R2 storage → D1 metadata → SvelteKit UI — a compact edge architecture with no idle servers.
- Workers API
- R2 storage
- D1 metadata
- SvelteKit UI
Stack
Cloudflare Workers for API logic, R2 for file storage, D1 for link metadata and expiration, and SvelteKit on Cloudflare Pages for the web interface.
- Cloudflare Workers, D1 & R2
- SvelteKit
Outcome
Ralink runs in production on Cloudflare’s edge: share files with expiring links, distributed globally and efficient to operate.
Building something similar? We can help define the scope.
Contact us