Independent, self-managed infrastructure Read the production requirements

Separate capacity from retention

Recording storage sized around hours, not guesswork

Recordings can turn disk into the long-term constraint even when compute capacity is healthy. Estimate growth, define retention and keep backups distinct from live storage.

01

Local NVMe for processing

Fast local disks support capture and post-processing. Retaining every published recording forever on the same filesystem eventually couples server replacement to a large data migration.

02

Retention changes the calculation

Monthly recorded hours, the media profile and the number of months retained matter more than registered users. Use the recording calculator to create a planning estimate, then measure real output from your deployment.

03

Storage is not a backup

Mirroring and external capacity improve resilience but do not replace an independent, tested backup. Decide separately how published recordings, raw archives and application metadata are protected.

The operational reality

BigBlueButton capacity depends on how people use media. Hardware specifications help narrow the choice, but your own load test, monitoring and failure plan turn that choice into a production design.

Questions answered

What teams ask before ordering

How much storage does one recording use?+

It varies with webcams, screen sharing, audio and processing formats. The calculator provides a planning range, not a guarantee. Measure real meetings before setting long retention periods.

Can I add storage later?+

Yes, subject to availability and architecture. Planning an external tier early reduces migration work when local NVMe fills.