Self-hosted webinars and large online events

The attendee record comes from the conferencing platform's own logs, so the platform and its reverse proxy must be configured to keep them. On BigBlueButton, the meeting events and participant join and leave records are written by the server and can be exported after each session. On Jitsi, the Prosody XMPP server, Jicofo and the Jitsi Videobridge produce join and conference events, and the web server records access. The useful evidence is a set of logs kept in one place, with timestamps synchronized across hosts, and a documented retention period. DeployOpen can configure log collection, retention and export for these components as part of an implementation, and can prepare the evidence procedure. Auditors decide whether that evidence is sufficient for your attendance requirements. Confirm with the vendor exactly which fields each log records in your version, because lists of attendee names, email addresses and join times vary by setup and by whether guests join anonymously.

Role assignment is recorded in two places: the authentication source and the platform's session state. When moderators are authenticated through JWT tokens, LDAP, or an identity provider, the token or directory group that granted the moderator role is the primary record, and it should be retained with the session. Jitsi's token authentication recommends JWT for moderator control and a separate anonymous domain for guests, which gives a clear split between identified hosts and anonymous attendees. On BigBlueButton, moderator status is set when the meeting is created through the API, and the request is authenticated with a checksum computed from a shared secret. Keep the API call logs and the identity provider logs together so that each presenter can be matched to a login event. DeployOpen can design that mapping and the log retention. Whether the mapping meets a particular policy is a question for your auditor.

Keep the login events from the identity source that authorized each host, plus the platform's record of which role each session received. The list usually includes successful and failed sign-ins, the time of each, the account or token identifier, and the directory group used to grant access. For Greenlight on BigBlueButton, external authentication through OpenID Connect means the identity provider holds the primary sign-in record. For Nextcloud Talk, LDAP and Active Directory logins and OpenID Connect or SAML backends produce their own events. Confirm which of these events your identity provider exports and for how long, since many default retention periods are shorter than a regulator expects. DeployOpen can connect these sources to a central log store and document the retention settings. The retention length itself is a policy decision you set with legal and records owners.

Recording evidence has three parts: the storage location, the access log, and the deletion record. BigBlueButton stores recordings on the server disk, and its install guidance recommends 500 GB of disk for recordings, which makes storage location and retention a deliberate design choice. Jibri in a Jitsi Docker deployment produces recordings and streams from its own container, so its output path and file handling must be defined and monitored. Access to recordings is controlled by the file system permissions, the web server's access logs, and any playback front end or file sharing layer you add, such as Nextcloud with its audit features. Deletion should be a logged, scheduled job rather than an manual cleanup. DeployOpen can implement storage paths, access logging and retention jobs, and prepare a deletion procedure. Your records retention schedule determines how long each recording must stay. Ask an auditor to confirm which records count as official.

Ask for a written load test report that states the test scenario, the number of active and passive participants, the media path used, the server sizes, and the measured results for CPU, memory, bandwidth and failures. Nextcloud Talk's High Performance Backend documentation describes support for roughly 30 to 50 or more active participants plus hundreds of passive ones, so a report should show your event's actual mix against those figures. For BigBlueButton, the report should compare the test against the 16 GB RAM, 8 CPU core and 250 Mbit/s symmetrical bandwidth minimums in the install documentation, and against the ports that must be reachable. For Jitsi, the report should show how many videobridges were used and whether load was spread across them. A rehearsal report is evidence of capacity planning, not a guarantee. DeployOpen can plan and run rehearsal load tests as part of a fixed scope and deliver a written report.

Change records are the tickets, configuration diffs and version notes that show what changed, when, who approved it and how it was tested. For a webinar stack, the record should name each component version, such as the Nextcloud major version, the BigBlueButton release, or the Jitsi Meet stable build, and the date of each upgrade. Nextcloud requires upgrading one major version at a time with a backup before each step, and BigBlueButton 4.0 does not support direct upgrades from 2.6, 2.7 or 3.0 and recommends a clean install. Keep the configuration files under version control and save a pre-change backup with each record. Note that the Nextcloud release schedule sets support windows for each major version, so an upgrade plan should match those dates. DeployOpen can run upgrades under a written change procedure and document each change. Your change advisory board decides what counts as an approved change.

The HIPAA Security Rule requires audit controls that record and examine activity in systems that contain electronic protected health information, under 45 CFR 164.312(b), and transmission security under 164.312(e)(1) that guards against unauthorized access to that information while it moves across a network. In plain terms, you must be able to see who did what on a platform that handles patient data, and you must protect the data while it travels. For a webinar platform, that means keeping session, authentication and recording access records, and using encrypted connections with valid certificates. Whether a self-hosted meeting platform is in scope depends on the content it carries and your risk analysis. DeployOpen prepares the logging, encryption configuration and evidence procedure, and does not issue a compliance determination. A qualified HIPAA advisor or auditor should confirm how these controls apply to your use.

DeployOpen prepares the systems, controls and evidence that an assessment will review. In a webinar engagement, that typically means configured logging and retention, documented authentication and role mapping, recording storage and deletion procedures, rehearsal load test reports, and change records for each upgrade. The output is an evidence set your team and your auditor can inspect. DeployOpen does not issue audit reports, attestations or certifications. An independent auditor or certification body decides whether your controls meet a framework such as HIPAA, SEC recordkeeping or an internal policy, and issues any report. Before work starts, agree in writing which evidence artifacts are in scope, who owns each one after handover, and how often each must be refreshed. Ask your auditor to review the evidence list early so gaps are found before the event.

The cost has four parts: the servers and bandwidth that carry audio and video, the storage for recordings, the implementation work and the ongoing support. Servers and bandwidth are paid to your cloud provider or data center, and they recur every month. Implementation is a one-time project cost, usually agreed as a fixed scope with deliverables and timelines in writing before work starts. Support, upgrades and continuous testing are typically a recurring retainer. Ask each vendor and partner to show these four lines separately so you can see what is one-time and what recurs.

The main drivers are peak concurrent participants, how many people speak or share video, whether sessions are recorded or streamed, and how long recordings are kept. For BigBlueButton 4.0, the documented minimum for one server is 16 GB of RAM with swap, 8 CPU cores with high single-thread performance, 500 GB of disk for recordings (50 GB without recording) and 250 Mbit/s symmetrical bandwidth. Larger audiences usually mean more servers or more videobridges, so the bill grows in steps rather than smoothly. Reducing the number of active speakers, keeping most attendees in listen-only mode and setting a short recording retention period are the most direct levers.

Nextcloud Enterprise is a paid subscription sold in Standard, Premium and Ultimate tiers, with a 100-user minimum. According to Nextcloud's pricing page, list prices start at 71.29 euros, 104.99 euros and 204.75 euros per user per year respectively for 100 or more users, with lower rates from 200 users. Standard includes one year of maintenance, Premium adds a maintenance lifecycle of five or more years and clustered instance support, and Ultimate adds support up to 24/7 with response times down to one hour. Confirm current pricing with Nextcloud before budgeting, because the High Performance Backend that webinars need is obtained through Nextcloud sales and is priced separately.

A capable team can run a platform in-house, but large events add work that is easy to underestimate: capacity planning, rehearsal load tests, presenter and moderator training, lobby and access control, and monitoring during live sessions. Plan for on-call coverage around scheduled all-hands and public hearings, and confirm who owns upgrades, since BigBlueButton 4.0 does not support direct upgrades from 2.6, 2.7 or 3.0 and a clean installation is recommended. Many organizations split the work: internal staff own accounts, schedules and event coordination, while an implementation partner handles sizing, hardening, backups and load testing. Decide which of these tasks your team can staff before you choose a model.

Duration depends on the platform, the size of the audience you need to reach, the hosting environment and how many integrations are in scope, such as identity, a learning management system or a streaming destination. Infrastructure approvals, firewall changes, TLS certificates for a proper domain and the time needed for rehearsal load tests often take longer than the software installation itself. No fixed duration applies to every organization, so ask a partner to state the phases, dependencies and milestones in the written scope rather than relying on a general estimate. Plan a load test well before your first large public event.

You need to supply the hosting environment, a public or internal domain with a valid certificate, firewall rules for the required ports, and access to your identity provider or directory if users will sign in with corporate accounts. You also need named owners for event approval, recording consent and retention policy, and a set of representative test users for rehearsals. For BigBlueButton, the documented requirements include TCP ports 80 and 443, UDP ports 16384 to 32768, a valid hostname for SSL and Docker for document conversion, and a TURN server is recommended for users behind restrictive firewalls. Confirm these with your network and security teams early, because they often set the schedule.

Ask for the scope in writing, with a list of deliverables, the environments covered, the peak concurrency the design supports and the acceptance criteria for rehearsal load tests. The quote should separate one-time implementation fees from recurring hosting, support and retainer fees, and state what each covers and what it excludes. Ask which third-party licenses or subscriptions are required, what upgrade and backup responsibilities look like, and how change requests are priced. DeployOpen does not publish a price list, and a quote follows from the written scope, so provide your expected audience sizes, recording needs and integration list when you request one.

Yes, recording is often the largest variable item after compute. BigBlueButton 4.0 documents 500 GB of disk for recordings, compared with 50 GB without recording, so storage needs should be sized from your event calendar and retention policy. Storage is a recurring cost, and it also creates compliance work, since recordings may contain personal data and must be deleted on schedule. Ask the partner how recordings are stored, backed up, encrypted and removed, and whether that work is inside the fixed scope or part of a retainer.