One suite · purpose-built production surfaces
StreamSuites is a connected livestream-production suite built around Browser Studio, native StudioApp, and an OBS integration—with automation, engagement, alerts, and public experiences supporting the show.
Identity · permissions · rooms · destinations · shared state
The production family
Each product has a distinct media architecture. They share authoritative identity and state without forcing media through the Python runtime.
Private Runtime-backed rooms, guests, layouts, branding, and direct browser media through Cloudflare RealtimeKit.
A native C#/.NET/WPF production shell supervising a C++20 engine for local capture, composition, audio, recording, replay, and output foundations.
A supported plugin and integration path for StreamSuites rooms, guest receiver foundations, and control surfaces inside existing OBS workflows.
Architecture with boundaries
Runtime/Auth is the canonical source for accounts, sessions, roles, permissions, rooms, invitations, credentials, destinations, alerts, automation, shared state, exports, and versioning.
It coordinates the suite, but it does not carry Browser Studio, StudioApp, or OBS media. Each production surface keeps its own appropriate media architecture and lifecycle.
Connected around the show
StreamSuites began with automation and audience tools. Those capabilities remain first-class modules, now connected around the production workflow instead of defining the product alone.
A wider product system
Public, Creator, Admin, Developer, Docs, and FindMeHere each serve a specific audience while Runtime/Auth remains authoritative underneath.
Living product record
The structured About sources keep general explanations and expandable implementation constraints together in manifest-defined order.
Current development posture
Products are at different implementation stages. Current product pages, access gates, and Runtime/Auth metadata remain authoritative for capability and availability.
