Skip to content

Case study

Ralink

A production file sharing system with expiring share links — engineered on Cloudflare's edge platform with a lean SvelteKit frontend.

Visit Ralink Back to work

Edge runtime

Cloudflare Workers

Storage

R2 object storage

Status

Production

Product screenshots coming soon

Problem

Files needed to be shared securely over the web with time-limited access — without running servers or managing idle infrastructure.

Approach

We architected the backend first on Cloudflare Workers, R2, and D1 — APIs, file storage, and link metadata with expiration — then built a lean SvelteKit frontend on Pages.

Architecture

Workers API → R2 storage → D1 metadata → SvelteKit UI — a lean edge stack with no idle servers.

  1. Workers API
  2. R2 storage
  3. D1 metadata
  4. 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 UI.

  • Cloudflare Workers, D1 & R2
  • SvelteKit

Outcome

Ralink runs in production on Cloudflare's edge — share files with expiring links, globally distributed and cost-efficient.

Building something similar? Let's scope it together.

Get in touch