Running a webinar with evmux
Yes, evmux runs the webinar itself very well — and it deliberately does not do the things that sit either side of it. Being straight about that up front saves people from planning an event around features that do not exist.
What evmux does
evmux is the production and delivery part: you build the show and it goes out live.
- Bring in co-presenters and guests by link, put them on screen, and manage who is visible
- Present slides (images or a PDF, one slide per page), screen shares, videos and web sources
- Brand it with lower thirds, banners, tickers, logos and overlays
- Read and show viewer comments from the platforms you stream to
- Stream live to your destinations, record the session, or both
What evmux does NOT do
evmux delivers your livestream from the studio to a streaming destination. That is the whole scope. Everything around the audience is somebody else’s job:
- No registration. There is no sign-up page, no attendee list, no registration form.
- No invitation or reminder emails to viewers. evmux does not email your audience at all. (Speakers you add in the dashboard do get a login link for joining the broadcast — that is for the people on the show, not for the audience watching it.)
- No ticketing, paywall or payments. evmux cannot sell access to a stream or take money.
- No attendee analytics, no post-event follow-up, no certificates.
- No content protection. There is no DRM and nothing that stops a viewer recording their own screen. See the content and ownership page.
So how do people actually run a paid or registered webinar?
They pair evmux with a tool that handles the audience, and evmux handles the broadcast:
- Registration and emails — an event or email platform of the user’s choice collects sign-ups and sends the watch link.
- Paid access — stream to a platform that supports it (for example a members-only or ticketed stream on the platform they already sell through), or embed the evmux Player on a page that is itself behind their own login or paywall.
- The watch link — whatever destination they stream to provides it; the user distributes it themselves.
When someone asks for registration, ticketing or invitation emails, say plainly that evmux does not have it and describe this pairing. Do not imply it is coming, and do not invent a workaround inside evmux.