A live, monetised SaaS, built and run by one person, from empty repo to launch in 3 weeks

Every agency knows the routine. Big files go through a transfer service, folders through a cloud drive, the rest by email. Then you chase the client for their logo, their copy, their photos, and the paid tools that would fix it put a sign-in wall in front of the very person you need files from.

How files change hands todaythe problem

sending

risk: One tool for big files, another for folders, email for the rest

receiving

problem: Chasing the client by email until something arrives

client

problem: Paid tools ask your client to create an account first

pricing

risk: Per-seat subscriptions for something you use twice a month

lifespan

risk: Links that live forever unless someone remembers to delete them

The whole product is a single Worker in plain JavaScript, with no framework and no build step. The browser does the heavy lifting on the way in, and the edge streams on the way out, so neither a huge upload nor a 50 GB download ever needs a big server.

1. Step 1 (you): Drop a folder, browser unzips & slices. Rejected here: Over budget (sign-ups pause first).
2. Step 2 (automated): Multipart upload, parts checked on arrival.
3. Step 3 (automated): Private link, expires on its own. Rejected here: Abuse report (kill switch, link gone).
4. Step 4 (client): Client opens, no account.
5. Step 5 (client): Sends files back, inbox link.
6. Step 6 (automated): Email on arrival, to you.
7. Step 7 (live): Resumable download, any byte, any size.

1. agent://researcher

   Mapped how agencies hand work over today and where each tool forces an account or a subscription.

   Never allowed to: choose the positioning.

2. human://vegardHUMAN GATE

   Chose the product: one link out, one link back, a one-time licence instead of a subscription.

3. agent://architect

   Drafted the storage model and a separate content domain, so an uploaded HTML file can never touch the app’s login.

4. agent://builder

   Wrote the Worker, the browser-side slicer, the streaming download and the Stripe price ladder to spec.

5. agent://tester

   Drove a real local server through upload, expiry and purge end to end, and caught a cron bug on its first run.

6. human://vegardHUMAN GATE

   Measured the passkey library at 48% of the bundle and cut it. Evidence over features.

7. agent://watcher

   Guards spend, runs 8 rate limiters and sends a daily ops email.

   Never allowed to: let the bill run away: new sign-ups pause first, then new uploads.

8. human://vegardHUMAN GATE

   Ships every release from a clean, pushed commit. The deploy script refuses anything else.

There is no server to keep warm. Files sit in object storage and are streamed from the edge, and streaming a 50 GB folder as a TAR archive takes ~0.1 s of CPU. So the bill follows stored gigabytes, not visitors. A budget guard watches spend: at the limit it pauses new sign-ups, and if spend keeps rising it pauses new uploads, while every existing link keeps working.

CPU for a 50 GB downloadstream a 50 GB inbox download as TAR (vs ~91 s with ZIP's CRC-32)

~0.1 s

Edge rate limitersabuse and cost protection, before any code runs

8

Disposable-email domains blockedrefreshed weekly, so free accounts stay real

8,695

• The repositoryEvery line, with the release history: each live version is a pushed, diffable commit.
• Your Cloudflare accountWorkers, object storage, database, rate limiters and cron, in your name.
• Your Stripe accountPrices, the ladder logic and payouts go straight to you.
• A separate content domainSo files your users upload can never reach your app’s login.
• Ops email and runbookA daily report, the budget guard settings and the abuse kill switch, documented.
• The lifecycle testsUpload, expiry and purge, driven end to end against a real server.