Separate failure domains
Frontend maintenance should not consume resources on a running class server. Isolation limits resource competition and lets each layer follow its own backup and change schedule.
Right-sized instead of oversized
Greenlight does not need a media-node hardware profile. The isolated tier uses a smaller dedicated-compute VPS while keeping NVMe storage, public addressing and optional daily snapshots.
Ready for a load-balanced backend
Point Greenlight at one BigBlueButton API endpoint today, then introduce Scalelite as the backend pool grows. Keeping the frontend separate means that transition needs fewer moving pieces.
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.