Case study · 2026
Zivon
Nine services, three servers, one operator
A white-label streaming software platform for resellers: an Android player, a full distributor panel, a branded-APK build pipeline, a Stripe pay-server and two Cloudflare Workers — designed, built, deployed and kept running end to end.
9
Sites & services
3
Production servers
2
Cloudflare Workers
1
Signed Android pipeline
Challenge
Resellers want to sell a streaming product under their own brand, but building one means an app, a payment system, a customer panel, a way to generate branded builds, and somewhere to host all of it. Any single piece is a project; together they are a platform. Zivon had to deliver that as software a non-technical reseller can operate — while staying strictly software-only, with no content provided — and it had to keep running once real customers depended on it.
Approach
- 01Built the Android player first and put it behind a reproducible, signed release pipeline so every shipped build is traceable to a commit.
- 02Designed one panel process to serve both the distributor workspace and the end-user companion site, gated by host, so there is a single deploy rather than two drifting codebases.
- 03Separated concerns across servers by blast radius: panel, payments and public APK hosting each run isolated, so a failure in one cannot take down the others.
- 04Pushed the lightweight, latency-sensitive pieces — sign-in relay and metadata proxy — to Cloudflare Workers instead of paying for more origin servers.
- 05Wrote a written operations model — canonical checkouts, per-release source snapshots and nightly off-site backups — after a duplicate checkout once caused builds to ship mid-development code.
The reseller panel
A React SPA on a Node API where distributors manage their customers, branding and credits, with a gated admin host for superadmin access on the same process.
- Multi-tier access: distributor, reseller and superadmin
- Per-brand configuration consumed directly by the Android app
- Admin surface isolated to its own hostname, same deploy
- Runs under systemd behind nginx and Cloudflare, TLS full-strict
Payments and the marketing site
A separate pay-server handling Stripe checkout for the premium tier, sitting alongside the public marketing site and blog on its own isolated server.
- Stripe checkout and webhook handling for subscriptions
- Premium tier resellers earn margin on, not just a flat licence
- Marketing site, blog and pricing on the same box
- Isolated from the panel so a payment outage can't take down customer accounts
Branded build pipeline and edge services
A build tool that produces per-reseller branded APKs, a hardened public download host, and two Cloudflare Workers carrying the auth and metadata load.
- Automated branded-APK generation per reseller
- Hardened, single-purpose public download host
- QR and phone sign-in relay as a Cloudflare Worker with KV
- Metadata proxy Worker keeping third-party API keys off the client
- Release signing key treated as irreplaceable, with documented backup
Outcome
- A complete white-label platform a reseller can run as their own business, software only.
- Nine sites and services across three servers plus the Cloudflare edge, all under one operator.
- A documented recovery model with three independent layers: git history, per-release source snapshots and nightly off-site backups.
- Proof that I can carry a product from Android source through to billing, hosting and the runbook that keeps it alive.
Services involved
Want something like this built — and kept running? oliver@omwc.co.uk