The offer that fits · Chosen by buyers
A live, paid SaaS built and run by one person, from first line of code to launch in 3 weeks
Filyhost sends files to clients and gets files back: one private link out, one inbox link back, and no account for the client. The bill grows with the files stored, not the visitors. What it proves for you: one person can run a client portal that takes payments and keeps its costs and abuse in check.
Live at filyhost.com · built 31 Aug–21 Sep 2026 · 173 commits · numbers observed 2026-10-05
Open the live product: filyhost.com01 · Before
Sending work is easy. Getting files back isn’t. The problem, as agencies live it.
Every agency knows the routine. You send work through three different tools, then chase the client for their logo, text and photos. The paid tools that would fix this make that client sign up first.
- 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: Monthly fees per user, for something you use a few times a month
- lifespan
- risk: Links that live forever unless someone remembers to delete them
02 · What I built
One link out, one link back Gold is a person acting. Teal is software at work.
The whole product is one lean program with little to keep updated. Your browser does the heavy work on uploads, and downloads stream straight from storage, so even a 50 GB download needs no big server.
- Step 1 (you): Drop a folder, your browser prepares it. Rejected here: Over budget (sign-ups pause first).
- Step 2 (automated): Upload in pieces, each piece checked.
- Step 3 (automated): Private link, expires on its own. Rejected here: Abuse report (taken down at once).
- Step 4 (client): Client opens, no account.
- Step 5 (client): Sends files back, inbox link.
- Step 6 (automated): Email on arrival, to you.
- Step 7 (live): Download that resumes, any size.
03 · Who did what
Who did what Agents propose. A human approves.
-
agent://researcher
Mapped how agencies hand work over today and where each tool forces an account or a subscription.
Never allowed to: decide how the product is pitched.
-
human://vegardHUMAN GATE
Chose the product: one link out, one link back, a one-time licence instead of a subscription.
-
agent://architect
Put uploads on a separate web address, so a harmful file can never reach the app’s login.
-
agent://builder
Built the app, the uploads, the streaming download and the rising licence price.
-
agent://tester
Tested upload, expiry and deletion end to end on a real server, and caught a scheduled-job bug on its first run.
-
human://vegardHUMAN GATE
Found that one sign-in add-on (passkeys) made up 48% of the app’s size, and cut it. Evidence over features.
-
agent://watcher
Watches spending, runs 8 limits against abuse and sends me a daily status email.
Never allowed to: let the bill run away: new sign-ups pause first, then new uploads.
-
human://vegardHUMAN GATE
Releases only from a saved, recorded version of the code. The release script refuses anything else.
04 · Results
Results so far Every number dated, with how it was measured.
| Number | What it measures | How it was measured | Observed |
|---|---|---|---|
| 3 weeks✓ verified | from first line of code to a live, paid service | git history 31 Aug–21 Sep 2026 | 2026-10-05 |
| 173✓ verified | commits | git history | 2026-10-05 |
| ~0.1 s✓ verified | of server time to stream a 50 GB download | edge benchmark | 2026-10-05 |
| 3 GB✓ verified | download that resumes after a break, tested live (built for 50 GB) | edge test | 2026-10-05 |
| 8✓ verified | limits against abuse, checked before any code runs | wrangler config | 2026-10-05 |
| 8,695✓ verified | disposable-email domains blocked, list refreshed weekly | blocklist size | 2026-10-05 |
| $29 → $119✓ verified | lifetime licence price ladder | pricing config | 2026-10-05 |
| Not published | Revenue and customer count | own product; revenue figures stay private | — |
05 · Running costs
What it costs to run You pay for storage, not visitors.
No server runs all day: files sit in storage and stream straight to whoever downloads them. A budget guard watches spending. At the limit it pauses new sign-ups; if spending keeps rising, it pauses new uploads. Every existing link keeps working.
- Server time for a 50 GB downloadsent as one stream instead of a ZIP file
- ~0.1 s
- Limits against abusethey stop floods and misuse before any code runs
- 8
- Throwaway email domains blockedrefreshed weekly, so free accounts stay real
- 8,695
06 · Ownership
What you would own If I built a portal like this for you.
- The codeEvery line, with the full history of each live version.
- Your Cloudflare accountHosting, storage, database, abuse limits and scheduled jobs, in your name.
- Your Stripe accountPrices, the rising-price rule and payouts, straight to you.
- A separate address for uploadsSo uploads can never reach your app’s login.
- Daily report and manualThe daily email, the budget guard settings and the abuse off-switch, written down.
- The testsUpload, expiry and deletion, tested end to end on a real server.
07 · What I’d build for you
A client portal or paid tool that runs itself, on your accounts
Client portals, document intake, quote tools, member areas: if your business sends things to clients or needs things back, I’ll build the portal the same way. Payments, abuse protection and spending caps come with the build, not in a second phase.
- A portal or tool on your own web address and your own accounts
- No client accounts unless you want them; one-time codes instead of passwords
- Optional: a way for your clients’ AI assistants to use it
Not for you if an off-the-shelf tool already does the job. I’ll tell you so on the first call.
08 · Under the hood For your web developer: the technical detail
- Runtime
- Cloudflare Workers in vanilla JavaScript, no framework, no build step: ~20,000 lines of source. R2 for files, D1 for accounts and links, the Cache API, three cron triggers.
- Uploads
- Zips are unpacked in the browser with
DecompressionStream, never held in memory whole. Files are sliced and uploaded as multipart parts, each validated on arrival, so a bad upload fails fast instead of at 100%. - Downloads
- A streaming USTAR archive instead of ZIP: a 50 GB inbox costs ~0.1 s of CPU to stream, where ZIP’s CRC-32 would burn about 91 s. Downloads resume at any byte offset with zero stored state (fixed-length stream plus ETag and If-Range). Verified at 3 GB on the edge.
- Isolation
- User content is served from a separate registrable domain, so uploaded HTML can never touch the app’s auth scope.
- Abuse and limits
- 8 edge rate limiters, Turnstile, a weekly-refreshed blocklist of 8,695 disposable-email domains, and a kill switch that takes a reported link down in place.
- Viral links
- A link that goes viral costs one database read per data centre per minute, memoised in the Cache API, not one per request.
- Payments
- Stripe, with a lifetime licence that climbs $29 → $119 as live sales accumulate. Ads in the sponsored slot are bot-filtered and rotated by weight, rendered server-side with no layout shift.
- Trade-offs
- Passkeys removed after measuring: one library was 48% of the Worker bundle (773 KiB).
- Launch film
- Rendered frame by frame from HTML, in 16:9 and 9:16, with a timed voiceover script.


