Boundaries
What Stream does not do, and which product to read about instead.
Stream owns going live, the on-air scene, and merged chat across streaming platforms. It deliberately does not own the fan-facing business around that stream, or the shared account/identity layer underneath it. This page is the map of what's next door.
| Not Stream | Lives in | Why it's not here |
|---|---|---|
| Fan messaging, PPV, broadcasts, the vault | Club | No inbox, PPV, or vault code exists anywhere in Stream's product tree. |
| Domains, smart links, click-tracking, landing pages | Link | Stream displays landing-page objects on air (see Connections), but doesn't own the domain, the link, or the click. |
| Login, sessions, team-access grants, platform-account connection, billing, support | Account Platform | Auth, team access, and OnlyFans/Fansly account connection all live in the shared layer, not inside Stream. |
| The media a scene shows on air | Link | Images and video for scene layers come from the shared Media Gallery — Stream reads it, doesn't own it. |
| Traffic/ad attribution | Link / Club | Stream has no concept of a traffic source, campaign, or attribution window. |
Fan messaging and the vault
Stream has no inbox, no PPV composer, no broadcast system, and no content vault anywhere in its own tree. A creator's paid-fan conversations and content library are entirely Club's.
Domains, smart links, and landing pages — with one real exception
Stream doesn't register domains, build smart links, or track clicks — that's Link's
Domain/Click model and its public redirect. The one place the two products actually
touch is on-air: a scene layer can show a landing-page teaser, content deck, or
notification banner pulled from Link's funnel constructor, through a single adapter
file that names exactly what it's allowed to borrow (see
Connections). That adapter is the only door —
nothing else in Stream's core is allowed to import Link's landing code directly, and an
import-linter contract enforces it.
Login, team access, and platform-account connection
Whether someone can log in at all, what a team-access grant lets them reach, and how an OnlyFans/Fansly account gets connected in the first place are Account Platform's:
- Auth and sessions — the shared cookie/session mechanism every product's admin API relies on to know who's asking.
- Team-access grants — which tabs and functions a team member can reach; Stream's own endpoints trust this rather than re-implementing it (see Who needs it).
- Account connection — logging an OnlyFans/Fansly account into the platform is separate from Stream's own "connect a webcam platform" flow, which logs a streaming site (Chaturbate, Stripchat, CAM4, BongaCams) into the motor, not an OnlyFans account into anything.
'Platform' means three different things in this codebase
A streaming platform (Chaturbate, Twitch, Kick — Stream's own vocabulary), a fan's platform (OnlyFans or Fansly — Club's), and Account Platform the product are three separate meanings of the same word. This page uses "platform" only in Stream's sense; see the glossary for the other two.
The media a scene shows
An image or video layer in a scene, and a landing-page object's teaser art, are picked from a shared Media Gallery — a single upload used across products ("upload once, use everywhere"). Stream reads it by ID; it doesn't run its own media library, its own upload endpoint, or its own storage for these files.
What's next
Connections — the specific places Stream's code actually reaches across these boundaries today, cited to the file.