Auth inside a headless browser
The OBS Browser source cannot show a login. Each creator gets a signed, scoped, revocable token embedded in the URL — enough to render their own stream surface and nothing else.
All work
Go live from OBS — no desktop app, no plugin
Streamerdap
- Role
- Backend lead
- Year
- 2025
- Impact
- 500+ concurrent streamers · 5,000+ weekly payouts
Overview
Streamerdap turns a browser URL into a streaming surface. Creators drop it into an OBS Browser source and their stream runs straight from the web app — nothing to install, nothing to update.
Around that sits the business: PayPal subscriptions, renewal handling and plan-based feature gating, so what a creator can do on air follows the plan they are actually paying for.
What I built
- Led the backend — MySQL schema via Sequelize, REST API and the PayPal integration.
- Built the OBS-facing token flow so a browser source authenticates without a login screen inside OBS.
- Implemented subscription lifecycle handling: checkout, renewal, cancellation and plan-based feature gating.
- Built the PayPal payout system, processing 5,000+ weekly payouts to creators at 99.5% accuracy.
- Modelled creators, channels, plans and entitlements so a feature check is one query, not a chain of them.
The hard parts
Webhooks you can trust
PayPal webhooks arrive out of order and sometimes twice. Every event is signature-verified and applied idempotently against a stored subscription state machine, so a replayed renewal never grants a second month.
Entitlements that hold mid-stream
A plan can lapse while a creator is live. Entitlements are resolved server-side per request against the subscription state rather than trusted from the session, so a downgrade takes effect without needing the creator to reconnect.
Outcomes
- Install for creators
- Zero
- Recurring billing
- PayPal
- Gated features
- Plan
Stack
- Node.js
- MySQL
- Sequelize
- PayPal API
- OBS