Registration
Public page with questions, capacity, a join link per registrant, a calendar file and reminders 24 hours, 1 hour and 10 minutes before; a repeat option for series.
A live room, a replay and a follow-up
Host live webinars with registration, Q&A, polls and chat, and send the replay and follow-ups afterwards.
A webinar has hosts who are team members, panelists who are team members or outside guests with their own join link, a series option (daily, weekly, biweekly or monthly, up to 26 sessions) and moves through draft, scheduled, live, ended and cancelled. Registration has questions, capacity, honeypot and rate limits, a personal join link per registrant, a calendar file and reminders 24 hours, 1 hour and 10 minutes before. The live room is one Durable Object per webinar with WebSocket hibernation and a polling fallback, and shows each role only what it may see: presence, raised hands, invite to speak, a stage of up to 8, Q&A with votes and answers, single and multiple choice polls with shared results, and chat with moderation. Stage video uses Cloudflare Realtime and needs the Realtime secret; without it the room says so and the rest works, and the video path has not been run in a real browser. Recording is made in the host's Chrome or Edge and stored in R2 for replay on a registrant, public or emailed-code link, or a Videos embed address can be framed. Afterwards the app keeps attendance and minutes watched, Q&A and poll results, a registrant CSV, follow-up emails to attended and missed, leads to Enquiries or Contacts, and a Claude summary. Not built: breakout rooms, live captions, a waiting room, paid webinars and load testing. API /api/v1/webinars, /api/v1/registrants and a workspace feed; webhooks webinar.scheduled, webinar.started, webinar.ended, registrant.created and registrant.attended.
What Webinars does for you.
Public page with questions, capacity, a join link per registrant, a calendar file and reminders 24 hours, 1 hour and 10 minutes before; a repeat option for series.
Hosts and panelists on stage, hands, invite to speak, voted Q&A, single and multiple choice polls, chat with moderation; stage video needs the Cloudflare Realtime secret.
Attendance and minutes watched, recording and replay, Q&A and poll results, follow-ups to attended and missed, and leads to Enquiries or Contacts.
A suggested path for Webinars. What you can do depends on your access in the app.
Set the time, hosts and registration questions.
Open the room and run the session.
Send the replay and export registrants and questions.
Live host, inventory, governance, health checks, verification, dependencies and history.
A webinar has hosts who are team members, panelists who are team members or outside guests with their own join link, a series option (daily, weekly, biweekly or monthly, up to 26 sessions) and moves through draft, scheduled, live, ended and cancelled. Registration has questions, capacity, honeypot and rate limits, a personal join link per registrant, a calendar file and reminders 24 hours, 1 hour and 10 minutes before. The live room is one Durable Object per webinar with WebSocket hibernation and a polling fallback, and shows each role only what it may see: presence, raised hands, invite to speak, a stage of up to 8, Q&A with votes and answers, single and multiple choice polls with shared results, and chat with moderation. Stage video uses Cloudflare Realtime and needs the Realtime secret; without it the room says so and the rest works, and the video path has not been run in a real browser. Recording is made in the host's Chrome or Edge and stored in R2 for replay on a registrant, public or emailed-code link, or a Videos embed address can be framed. Afterwards the app keeps attendance and minutes watched, Q&A and poll results, a registrant CSV, follow-up emails to attended and missed, leads to Enquiries or Contacts, and a Claude summary. Not built: breakout rooms, live captions, a waiting room, paid webinars and load testing. API /api/v1/webinars, /api/v1/registrants and a workspace feed; webhooks webinar.scheduled, webinar.started, webinar.ended, registrant.created and registrant.attended.
Ticketed in-person events belong to Events; two-way team meetings belong to Meetings; stored videos belong to Videos.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
webinars.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.