Stagemere is webinar and live class software you host yourself, built by DEV3 Technologies on Laravel 12 and Filament 4. Each customer of yours is an organisation: a coach, a school, a training company or a marketing team that runs one-off webinars, multi-session cohorts and recurring office hours. Attendees register, get a personal join link, enter a live room and later watch the replay. You run it as the operator: plans, ticket sales, weekly payouts and abuse reports live in a separate panel.
What it does
- Registration that fills rooms. Branded event pages, your own registration questions, approval by hand when you want it, a waitlist that holds a freed seat for the first person in line, and a personal join link by email with a calendar file in the visitor's time zone. Reminders go out a day and an hour before and at the start; every email can be reworded and retimed.
- Paid tickets and coupons. Free or paid tickets per event, quantity limits, sales windows, percentage or fixed coupons and a price preview before checkout. Seats and tickets are held under a lock, so a full event never oversells; a payment that arrives after its hold expired is refunded automatically, and so is a duplicate. Refunds follow your policy, partial refunds are supported, and a cancelled session refunds its tickets (series tickets in proportion).
- A live room that survives a bad day. A green room for hosts 15 minutes early, a lobby countdown for attendees, then the room: the stage, chat with slow mode, hide, pin and timeouts, a question queue sorted by votes with a spotlight, live polls, hand raises and resources pushed into the room. The host runs it from a control room with Go live and End confirmations. If the video server is down the room keeps working and the host sees a retry banner.
- Series, office hours and certificates. A twelve-session cohort on one ticket, recurring weekly drop-ins, attendance across sessions and a certificate of attendance (PDF) at 75% that anyone can verify by link.
- Replays. Upload a file or paste a link. Files are private and streamed through signed ten-minute links with range support; who may watch follows the event's policy and expiry. Questions answered live become chapters.
- Reports. Registrations by source, show-up rate, average watch time, an attendance curve per minute, chat, question and poll engagement, revenue and replay views, with a CSV of every registration and segments you can export.
- Studio and operator panels. The studio has a dashboard with a Seat Map, events, sessions, tickets, registrations, waitlist, orders, coupons, refunds, takings, payout statements, certificates, branding, custom domain, API keys, webhooks and roles (owner, producer, host, moderator, analyst). Operators get organisations with plan meters, subscriptions, ticket sales, payouts, refunds, a video driver page, abuse reports with takedowns, an outbox, an audit log and audited, view-only support sessions.
- API and webhooks. Scoped keys, an OpenAPI description and signed webhooks for registrations, orders, session state, replays and attendance.
Video, in plain words
Stagemere hosts no video. Rooms run on Jitsi Meet through its embed API: use your own Jitsi server for production (signed JWT sign-in is supported, so only registered people get in) or a public instance for testing under its own terms. Recording needs Jibri on your server; replays are files or links. Attendance counts time on the Stagemere room page (a heartbeat every 30 seconds), not anything inside Jitsi. Public pages send a strict content security policy, and room pages allow exactly your Jitsi origin.
Quality
The release passed seven gates: Pint and Larastan level 6 with no baseline, 335 Pest tests (2747 assertions) on SQLite, a production build with a script budget, demo and empty seeders on MySQL 8 and SQLite, a headless browser smoke test with happy paths in the live room, the hero check at six widths and in Arabic and a no-3D check, MySQL race checks (twenty parallel registrations for the last five seats, parallel payments of one hold, two devices joining at once, parallel votes, go-live against cancel, parallel attendance finalisers), the web installer driven from the zip, and a secret scan. A model-assisted review of the money, room-access and attendance code found bugs that were fixed with regression tests before release. The home page scores performance 90 and accessibility 95 on mobile.
What you should know before buying
- No video hosting, no recording. You need a Jitsi Meet server for real rooms; room capacity is whatever it handles. Jibri records; Stagemere takes the file.
- You are the merchant of record. Tickets are paid on your gateway (simulated by default) and you pay each organisation out weekly from its takings. Organisations cannot connect their own payment account in this version.
- Email needs your provider. Confirmations and reminders go to a log until you configure a mailer.
- Live updates use Reverb when you run it and fall back to polling every three seconds otherwise.
- Custom domains need DNS and TLS at your web server or proxy (a Caddy example is in the guide). Verification is simulated in the demo.
- Web only. There are no mobile apps. Node.js is not needed to run it, since assets are prebuilt. MySQL 8 or MariaDB 10.6 or newer is recommended; SQLite works for trials.
Included
Source code, the web installer, a buyer guide, demo data with fictional organisations and people (10 organisations, about 26,000 attendees and a year of events, orders, attendance and replays, seeded in about 15 seconds), a live demo session that stays live, a cron entry for the scheduler, and six months of support.
Hero in the light theme — The marketing site follows the visitor colour scheme and keeps gold for every action.
