Azure Static Web Apps
Static Next.js pages are exported as HTML and deployed through Azure Static Web Apps for dependable first render and predictable operations.
architecture
Static Azure live streaming alpha architecture, with a clear explanation of what is running today and which systems stay intentionally off to keep launch cost low.
Azure Functions
Functions are reserved for future creator utilities, payout helpers, and secure control-plane tasks.
Livepeer
Livepeer remains the intended decentralized video layer once the current shell grows into a real stream pipeline.
Web PubSub
Azure Web PubSub is the intended real-time channel for chat, presence, and live audience coordination.
Launch posture
What is live today
Static routes, a guest-mode free tier, and device-local preferences that need no backend to stay reliable.
What stays off for launch
Azure Functions, Livepeer ingest, payments, and real-time chat remain disabled to keep spend near zero.
Why this is sustainable
The current experience is edge-served static HTML, CSS, and JS, which is the cheapest and most failure-resistant way to serve the first wave of users.
What the launch circle means
Email capture and watchlists are intentionally browser-backed today. That keeps the alpha honest, cheap, and resilient while we wait for proof that real notification infrastructure is worth turning on.
Why not just use Twitch?
| Concern | Traditional (Twitch/YT) | dapp.cam |
|---|---|---|
| Revenue split | 50/50 or worse | Creator keeps 90%+ |
| Content ownership | Platform owns | Creator owns |
| Audience portability | Zero | Full export |
| Payment method | Platform currency | Direct tokens |
| Moderation | Platform decides | Creator configures |
| Identity | Account on platform | Portable wallet |