Your guest opens the link and they’re already on the show.
No accounts. No downloads. No "give me 10 minutes, I just need to install OBS" email six minutes before air. Send a URL, the guest joins in Chrome or Safari in about 30 seconds, you mix camera angles + screen-shares + a real scene canvas, then push the show to YouTube, Twitch, Facebook, LinkedIn, and Kick simultaneously.
Built for the podcasts workflow
Guest links that just work
Send a URL. Your guest opens it in Chrome or Safari and they’re in inside 30 seconds. No accounts, no downloads, no "what’s a stream key" calls 10 minutes before air.
Real scene canvas, not a grid
Compose shots the way a control room would: picture-in-picture, screen-share underneath, branded lower thirds. Switch live with one click.
Multi-platform out of one studio
Push the same show to YouTube, Twitch, Facebook, LinkedIn, and Kick simultaneously. One canvas, every audience, one encode.
Cloud or browser encoding
Heavy show? Route the encode through our GPU fleet so your laptop stays cool. Solo show? Browser encoding is fine. Same studio either way.
Why podcast teams pick TRaX
Most browser studios force you into a fixed grid of guest tiles. Podcasts that have ever cared about visual polish (a brand background, a screen share for chapters, a guest highlight) outgrow that fast. TRaX gives you the canvas without leaving the browser.
- Shared inputs across hosts: co-producers operate the same source library
- Modular pricing that bills the inputs and outputs you actually use
- A US edge network we run ourselves, so delivery behaviour is ours to tune
What a two-host, one-guest episode runs at
A talking-head show is the least demanding thing you can put through an encoder, and that is worth exploiting: spend the bitrate on clean faces and legible screen-shares rather than on frames nobody perceives.
- Program canvas
- 1080p30
- Two people sitting still is low-motion video. The 30-class rung costs 6 Mbps where 60 costs 9, and on a locked-off head-and-shoulders shot the difference is invisible to an audience that is mostly listening.
- Guest arrival
- A link, opened in Chrome or Safari
- The invite is an opaque token you can cap by number of uses and expire on a date, which is what stops episode 40’s link being a standing door into episode 41.
- Screen-share
- A canvas source, not a full-frame takeover
- A shared screen is placed on the scene like any other input, so the host stays on camera beside the slide instead of disappearing behind it for eleven minutes.
- Destinations
- YouTube, Twitch, Facebook, LinkedIn, Kick
- Those five are all 1080p-class ingests, so the whole set takes the same program and nothing gets re-encoded downward for the benefit of one platform.
- Archive
- Per-GB storage, billed by what you keep
- An hour of 1080p30 at 6 Mbps is roughly 2.7 GB, so a weekly show retained for a year is arithmetic you can do before you commit to it.
Programs run at 1080p as standard, and up to 1440p when every destination you have enabled can accept it — the canvas is clamped to the least capable one in the set.
Already comparing the alternatives?
A typical podcast show on TRaX
- 1
Spin up a studio
Sign in, name the show, pick a layout.
- 2
Invite the guest
Send the join link. They open it in their browser.
- 3
Build the scene
Drag cameras, screen, and branding onto the canvas. Live-switch between scenes.
- 4
Go live everywhere
Link Twitch/YouTube/Facebook/Kick once. Hit Go Live. Every destination starts at once.
What to know before you book the guest
None of this is a dealbreaker for a podcast. All of it is easier to design around than to discover twenty minutes before you record.
Browser encoding is free; the GPU encoder is metered
Encoding in the browser costs nothing on any plan. The cloud encoder draws from a monthly hour allowance and bills by the hour past it, so a show that records four hours a week should check that against the allowance rather than against a typical episode length.
An invite you never expire is an invite that still works
Tokens support a use limit and an expiry date, and both are optional. A guest link mailed out with neither set remains valid indefinitely, which is fine for a co-host and wrong for a one-off guest. Set an expiry when you mint it; revoking later means remembering to.
Your back catalogue is a recurring cost, not a sunk one
Storage bills monthly per gigabyte for as long as you keep the file. Two hundred archived episodes is a line item that grows every week, so decide early whether the master lives here or gets pulled down to cold storage once it is published.