wiqlo
Paid videos and a digital-goods marketplace for Bangladeshi creators
Watch
Phone channel
Phone join
Phone product
Phone upload
Shop
Channel
Studio
Members
Admin payments
FollowingHover to spread the screens, click one to look closer, orSwipe through the screens, tap one to look closer, or flip through all 11.
From a local run with the repository's seeded demo creators; the live site has only its first real shop so far.
Fans pay one creator in taka and see their videos up to a week before YouTube; creators also sell courses, presets and templates once. Built on Cloudflare Workers and Convex with bKash payments, and live at wiqlo.com.
- RoleTop committer on a three-person team
- Contribution248 of 487 commits, the most on the team
- StatusLive, bKash in sandbox wiqlo.com
- WhenSep – Nov 2026 · Arkieforge
In numbers
- watch page p95 at 200 viewers, after the load-test fixes
- 2.4 s → 9.5 ms
- server calls per viewer-hour once comments shared one head
- 998 → 118
- at 1,000 simultaneous viewers on the R2 delivery route
- 0 errors
- Playwright end-to-end specs, run against a production build
- 96
The problem
Bangladeshi YouTubers earn little from ads, and the global membership platforms don't take bKash, Nagad or Rocket. A fan who would happily pay a favourite creator has no simple way to do it in taka.
wiqlo gives each creator a paid home without changing how they publish: members see the next video up to a week before YouTube, exclusives never go public, and the same page doubles as a shop for one-time digital goods.
How it works
step through it · each step is a notePaid means bKash said so, to us
- 01The fan names what they want. The server prices it and writes a pending payment; the client never sends an amount.
- 02bKash takes the PIN and redirects the browser back. That redirect proves nothing on its own.
- 03Our server asks bKash itself: query the payment, and execute it only if it was approved.
- 04Amount in paisa, currency and invoice must match our row, and the capture needs a transaction id. Any mismatch fails it.
- 05A match settles exactly once: the membership is extended, the creator's ledger booked and the receipt queued.
- 06A fan who closes the tab mid-payment still gets what they paid for: a sweep finishes payments the browser never came back for.
My part
Built by a three-person team at Arkieforge.
- Built most of the watch experience: the watch page with chapters and up next, an autoplay queue, captions, Chromecast and AirPlay with signed playback renewal, offline downloads and a data-saver mode.
- Built Studio for creators: resumable uploads from a phone, release types and scheduled publishing, members with CSV export, retention and churn analytics, and comment moderation.
- Built the payment paths on bKash: memberships, tips, one-time purchases and tier upgrades, plus gifts, coupons and trials, saved wallets for PIN-only renewals, refunds and daily settlement reconciliation.
- Protected members-only video: a per-viewer watermark, a two-device cap, and an R2 delivery copy with plays, errors and cache-hit metrics that alert admins past 1% errors.
- Wrote the local load harness and fixed the four hot spots it found, including an SSR memory leak patched in the Clerk and TanStack Router packages.
- Built the admin side (approvals, payment lookup and refunds, payout batches, reports, suspensions with undo, an activity log) and moved production to wiqlo.com with existing accounts surviving the auth switch.
Decisions
A redirect is not a receipt
bKash sends the fan's browser back to a callback, and anyone can forge a query string. A payment is paid only when our own server asks bKash and the amount, currency, invoice and transaction id all match. Settlement runs exactly once, so a repeated callback can never extend a membership twice.
Money is integer paisa, priced on the server
Every amount is taka times 100 in a field ending in Paisa, and prices come from one server module. The client names a plan or an item, never an amount. A lint rule enforces it.
Measure before scaling
A load harness on one laptop found four hot spots before real traffic did: a view counter causing write conflicts, a watch query reading every membership, comment fan-out, and a server-render memory leak. All four were fixed and re-measured.
Delivery that can change vendors
Stream bills per minute watched, and a 10% platform fee stops covering that past a few hours a month. An R2 copy behind configuration flags costs about 1% as much to deliver, with the same signed token, so the switch happens on a threshold and not as a rewrite.
Upload once, watch with a signed token
- 01Video goes from the creator's phone straight to Stream over tus, so a dropped connection resumes and no bytes pass through our servers.
- 02When encoding finishes, the creator picks Early, Exclusive or Free and publishes.
- 03Every play asks one server-side check. A members-only video never ships a raw URL.
- 04Non-members get the free preview clip and the Join wall.
- 05Members get a short-lived token signed on our server, with no Stream API call per play, and a watermark that names the viewer.
- 06Behind a flag, the same token plays a copy from R2 through our Worker: 1,000 load-test viewers, 0 errors.
Stack
- AppTanStack Start, React 19, Tailwind 4, Cloudflare Workers, Alchemy
- BackendConvex, Clerk, Resend, React Email, Web Push
- Video and moneyCloudflare Stream, R2, tus uploads, bKash Tokenized Checkout
- QualityPlaywright, Vitest, convex-test, axe, Lighthouse CI, Biome, knip
