Active Alpha Production surfaces are at different implementation stages. Review current boundaries
StreamSuites™
Public dashboard Open Studio

A connected livestream production suite

Build the show.
Run it your way.

StreamSuites connects a private browser Studio, a native Windows production workspace, an OBS integration path, and the audience tools around every live show.

Open Browser Studio Explore StudioApp
Runtime/Auth authority Separate media paths Honest Alpha states
STREAMSUITES STUDIO
LIVE NOW
Closed access Browser Studio

Private rooms, guests, layouts, branding, and direct browser media. Broadcast output remains unimplemented.

Explore the suite

The production core

Four connected surfaces. One StreamSuites system.

Choose the production surface that fits the room. Identity, permissions, rooms, destinations, and shared state remain coordinated underneath.

01
Closed access

StreamSuites Studio

Browser production workspace

Private Runtime-backed rooms with guests, layouts, branding, browser sources, and direct Cloudflare RealtimeKit media.

  • OFF AIR; recording and broadcast output are not shipped
  • Runtime-owned rooms, invitations, and permissions
  • Direct browser media—not a Python media path
Open Studio ↗
02
Windows Alpha

StreamSuites StudioApp

Native Windows production workspace

A native C#/.NET/WPF shell supervising a C++20 engine for local capture, preview, audio, recording, replay, and output foundations.

  • Native Windows app—not a WebView or wrapped site
  • Engine-owned local media and bounded IPC
  • Approved-tester download remains access-gated
View StudioApp ↗
03
In development

StreamSuites Studio for OBS

OBS plugin and integration

Bring StreamSuites pairing, rooms, guest receiver foundations, and supported control surfaces into an existing OBS workflow.

  • OBS remains the media owner
  • Not an OBS fork or a Studio replacement
  • No StudioApp engine duplication
View integration ↗
04
Public surfaces

StreamSuites Public

Audience-facing artifacts

Runtime/Auth-backed surfaces for the clips, interactions, profiles, and progression that live around a show.

  • Clips, polls, wheels, tallies, and scoreboards
  • Profiles, leaderboards, economy, and progression
  • Downstream presentation—not a production media engine
Explore Public ↗

One authority. Separate media paths.

Connected where it matters. Independent where it must be.

Runtime/Auth coordinates canonical identity, permissions, rooms, invitations, destinations, credentials, automation, alerts, shared state, exports, and versioning. It is not the media engine.

01

Shared control planeOne authoritative source for identity and shared state.

02

Product-owned mediaBrowser, native, and OBS media never pass through Python.

03

Explicit maturityAvailable, partial, and planned states stay visibly distinct.

01 / BROWSERMEDIA OWNER
BROWSER MEDIABrowser Studio

Cloudflare RealtimeKit

Identity + state from Runtime/Auth
02 / PUBLICDOWNSTREAM
AUTHORITY-BACKEDPublic Surfaces

Clips · polls · profiles · artifacts

Not a production media engine
SHARED AUTHORITYRuntime / Auth
AUTHORITATIVE

Canonical identity, permissions, rooms, destinations, credentials, automation, alerts, shared state, exports, and versioning.

IdentityRoomsPermissionsDestinationsAutomationVersioning
03 / WINDOWSMEDIA OWNER
NATIVE MEDIAStudioApp

Supervised C++ engine

Identity + state from Runtime/Auth
04 / OBSMEDIA OWNER
OBS MEDIAStudio for OBS

OBS-owned pipeline

Identity + state from Runtime/Auth

Connected creator tools

The production is the center. Everything else connects around it.

Automation and engagement remain first-class StreamSuites capabilities, now presented as modules supporting the production family.

01 / ROOMS

Guests, rooms, and invitations

Coordinate directors, cohosts, backstage guests, approvals, and room identity from Runtime/Auth-backed workflows.

02 / OUTPUT

Destinations

Keep authorization and destination intent under one shared authority.

03 / CHAT

Live chat and automation

Normalize audience events, run triggers, and surface relevant interactions to operators.

04 / ALERTS

Alerts and operator surfaces

Backend-authored rules, notifications, delivery history, and native operator clients.

06 / MEDIA

Clips and public experiences

Publish clips, public profiles, leaderboards, and community experiences from authoritative data and media artifacts.

creator.streamsuites.app
StreamSuites Creator dashboard interface

Beyond the control room

One product family, purpose-built surfaces.

Creator, Public, Admin, Developer, Docs, and FindMeHere remain focused clients of the same Runtime/Auth authority.

CreatorConfiguration and integrations↗ PublicProfiles and public artifacts↗ AdminPrivileged operations through Runtime/Auth↗ DeveloperDeveloper console and feedback↗ DocsShipped reality and operator guidance↗ FindMeHereEligible creator discovery↗

What StreamSuites is becoming

A complete production system—not a collection of disconnected utilities.

StreamSuites began with livestream automation and engagement foundations. Studio and StudioApp now sit at the center, with those systems becoming connected capabilities around the production workflow.

The result is one shared authority, multiple purpose-built production surfaces, and audience tools that remain interoperable without collapsing into one monolithic application.

Read the full product story ↗
01

Truthful state

No surface claims to be live, connected, or ready until the underlying contract confirms it.

02

Clear ownership

Runtime/Auth owns canonical state; each production product owns its media execution.

03

Incremental capability

Alpha features remain labelled as available, partial, in development, or planned.

Active Alpha development

Preview the direction. Keep the claims precise.

Browser Studio, StudioApp, and Studio for OBS are at different implementation stages. Product pages and Runtime/Auth remain authoritative for current access, capability, download, and release state.

Open Browser Studio View StudioApp