Skip to main content
Status: Live — 555stream is operational at stream.rndrntwrk.com.

​
555stream

555stream is how RNDRNTWRK keeps creator and agent media live across the open internet. It gives creators and operators one browser-native surface for output, layout, overlays, guesting, and continuity, while cloud encoding handles the heavy lifting. 555stream sends output to any RTMP-compatible destination. Current first-party destinations include Twitch, YouTube, Kick, X, TikTok, Zora, and pump.fun, but the system is built for any RTMP-compatible destination.

​
Key Capabilities

Everywhere All at Once

Custom RTMP output to any destination. First-party support for major platforms with no architectural limit on where the stream goes.

Cloud Encoding

Video encoding offloaded to edge network. No GPU load, consistent quality regardless of local hardware.

Wallet and Permission Controls

Configure stream ownership and controller permissions from your wallet. Wire in on-chain triggers and gated actions where supported.

Always-On Programming

Keep the creator environment active between live segments with scheduled clips, games, quests, lottery windows, and recurring participation loops.

Alice (AI Operator)

Alice extends the operating window of 555stream. She can keep the system live, scheduled, and monetized even when the creator is not manually driving every moment.

Recovery and Failover

Automatic reconnection and state recovery for transient network events. Region selection with hot fallback. Published bitrate and resolution limits per region.

​
Setup: Browser Studio

Use the browser-based studio at stream.rndrntwrk.com with wallet auth. No desktop encoder needed.
1

Open Browser Studio

Go to stream.rndrntwrk.com in your browser. No OBS, no desktop app, no download.
2

Connect Wallet and Set Permissions

Connect your Solana wallet to set stream ownership and define controller permissions. If integrating pump.fun, ensure the project wallet has the required scopes.
3

Add Destinations

Add RTMP keys for the destinations you care about: Twitch, YouTube, Kick, X, TikTok, Zora, pump.fun, and any other RTMP-compatible destination.
4

Build Scenes and Overlays

Select a layout template: Solo, 2-grid, 4-grid, PIP (Picture-in-Picture). Configure overlays: lower thirds, tickers, alerts, branding, and sponsor assets.
5

Add Guests

Invite guests to join your stream live via WebRTC. Control guest audio and video independently. Grid layouts adjust automatically.
6

Go Live and Monitor Health

Start the session from the control surface. Monitor ingest health, bitrate, dropped frames, and auto-recovery status. The system automatically routes your stream to the best region based on audience distribution and live health metrics.
7

Schedule Always-On (Optional)

Add an offline schedule: clips from past streams and social channels, games, quests, lottery windows, and recurring participation loops. You can also hand this off to Auto Pilot.

​
OBS Browser Source (Fallback)

If you are transitioning from OBS or need a hybrid setup, add the Render overlay as a browser source while you migrate scenes. 
# OBS Browser Source (example)
# 1) Sources → Add → Browser Source
# 2) Name: "Render Overlay"
# 3) URL: https://555.rndrntwrk.com/overlay
# 4) Width: 1920, Height: 1080
# 5) Enable "Shutdown source when not visible"
Prefer the native 555stream path for lowest latency and simpler operations. Use the OBS Browser Source during migration only. See OBS Migration Guide.

​
L-Bar Ads

L-Bar keeps the creator visible while the ad is on screen. Instead of cutting away into a standard ad break, the stream stays live and the ad unit occupies the remaining screen space. The viewer never loses the stream. This matters because:
  • The audience keeps the live context
  • The creator does not disappear
  • The ad shows up inside the moment instead of replacing it

​
Placement Logic

Alice monitors engagement signals and triggers placements when those signals cross the required threshold. Current placement uses four live metrics: watch time, active plays, engagement score, and staking TVL, polled every 5 seconds. See Monetization Module for the detailed trigger and threshold logic.

​
Ad Revenue Flow

Ad revenue follows the standard economic cascade:
  • 10% ARP to audience
  • 50% of post-ARP to creator
  • 50% of post-ARP to platform allocation
See Fee Distribution for the full breakdown.

​
Alice as Operator

Alice extends the operating window of 555stream. She can help keep the system live, scheduled, and monetized even when the creator is not manually driving every moment. Alice can:
  • Start and stop broadcasts on schedule
  • Trigger L-Bar ads at signal-driven moments
  • Manage guest appearances
  • Control overlays, scenes, tickers, and alerts
  • Run Always-On programming through Auto Pilot
Alice is not required. She exists as an additional operating layer when creators want more leverage or more continuity.

​
Operations and Reliability

If 555stream is the distribution layer, reliability is part of the product thesis.
  • Session Recovery: Automatic reconnection and state recovery for transient network events.
  • Health Metrics: Ingest health, frame drops, CPU/network load recommendations, bitrate guidance.
  • Failover and Regions: Region selection with hot fallback. Published bitrate and resolution limits per region.

​
Creator Token Integration (Optional)

Status: Partially Implemented — Creator Token infrastructure is being rolled out via Render Expand.
Where enabled, creators can connect a Creator Token to add token-side economics into their stream:
  • Staker eligibility: All stakers are eligible for revenue sharing based on their staked amount
  • Staking choice: Creators may configure staking to their own token or to $555
  • Buybacks: A minimum of 20% of all creator revenue is used to buy back the staked token
  • Gated actions: Gate chat modes, overlay triggers, and experiences behind token thresholds
This extends the creator surface. It is not required to use the core broadcast, participation, and monetization flow.

​
Architecture

555stream runs on a multi-layer stack:
LayerWhat It Does
Browser ClientReal-time video capture and WebRTC communication
Edge EncodingCloud-based video encoding and media storage
Control PlaneScene management, source routing, and configuration
SFU ServiceSelective Forwarding Unit for multi-party WebRTC
Media EngineVideo composition and transcoding pipeline
Capture ServiceBrowser-based capture for recording and clips

​
Roadmap: Decentralized Stream

Note: Decentralized streaming is a long-term vision item. The current architecture is centralized cloud infrastructure. These roadmap items have no active implementation path yet.
  • Peer-assisted distribution and resilient ingest
  • Community-operated nodes with performance and reputation metrics
  • Censorship-resistant architecture governed by a future DAO

​
Integrating 555stream

If you are integrating 555stream into an agent or operator workflow:
  1. This page for product context and operator framing
  2. Developer Resources for ecosystem-level integration context
  3. Plugin README for package-level setup
  4. Plugin Repo for source, issues, and action-by-action reference docs

​
Repo reference docs

CTRL Panel

Configure overlays, modules, schedules, and operator settings.

Monetization Module

See how revenue enters the system and how campaigns are managed.

Alice

See how the AI operator layer works.

555 Arcade

See how the participation layer integrates with the stream.

OBS Migration

Transition from legacy desktop workflows.

API Usage

Integration and proxying best practices.
See also: Creator Tokens · Fee Distribution