Why write this
Every product page describes an ideal user. Very few describe who should look elsewhere, which means the reader has to work it out by inference, and inference is slow and often wrong.
I would rather tell you. If you are in one of these situations, something else will serve you better, and finding that out now costs you five minutes instead of a weekend.
You are not on Windows
The studio application runs on Windows. Not Mac, not Linux.
Cameras and viewer screens work from any modern browser on any device... phones, tablets, smart TVs, whatever. But the machine doing the production has to be a Windows PC, and no amount of enthusiasm changes that.
If your team runs on Macs, this is the end of the conversation, and I would rather you know at the top of the article than at the end of an installation attempt.
You need several people producing at once
On most plans, one account is active on one studio machine at a time.
If your organisation needs two independent productions running simultaneously (two sites each producing their own service, two teams working in parallel) the licensing does not fit that shape without multiple accounts.
This is a genuine constraint and one of the more common reasons a larger organisation will find this awkward. Sending one production to several places works well. Several places each producing independently is a different requirement.
You have a crew and a rack
If you already have a dedicated AV team, a hardware switcher, a proper audio desk, and people whose job this is, you are not who I built this for.
Not because it would not work, but because you have already solved the problem it solves. The entire design premise is that the operator is a volunteer with limited time and the equipment is what you already own. If that premise is false for you, the design decisions that follow from it are working against you rather than for you.
Purpose-built professional tools will serve you better, and you have the crew to run them.
Your event is genuinely mission-critical commercially
If the stream failing means refunds, contractual penalties, or a client relationship ending, buy insurance in the form of professionals and redundant equipment.
I build carefully and I field-test, and no software running on one laptop in a venue is the right answer for an event where failure has that kind of consequence. That situation calls for redundancy, two of everything and people whose job is to handle the failure, and that is a different kind of purchase.
You want it to run unattended forever
Some venues want a permanently installed system: switch on, run, no operator, never touched.
This is built around someone operating a live day... choosing shots, advancing the plan, making decisions. There is automation for pieces of it, and the shape of the product assumes a person is present.
If you want a fully automatic installation, a fixed-function appliance suits that better than production software with the operator removed.
You are streaming one static camera and nothing else
If your entire requirement is one fixed camera streaming to one platform, with no lyrics, no slides, no switching, no recording, no second screen... you do not need this.
A simple encoder, or the platform's own tools, will do that with less setup. This would be additional complexity in exchange for capabilities you have said you do not want.
Come back if you later want lyrics, a second angle, or a recording. Until then, simpler is correct.
You are past the ceiling
Some numbers are honest limits rather than things I am about to change. The highest tier supports five cameras. Output goes to up to eight displays. If you need twelve cameras, this is the wrong shape and no configuration will fix that.
Who it is actually for
Having said all that, the positive case is narrow and specific:
A small team, often one person, running a live day on hardware they already own. A church with volunteers. A school hall. A community venue. A conference organiser without a crew. Someone who needs several things at once (cameras, lyrics, a stream, a recording, a screen in another room) and has neither the budget nor the staff to assemble that from separate tools.
The design decisions all follow from that. Phones as cameras because they are already in the room. One application because a volunteer cannot learn four. Recording on every tier because losing a service that happened once is unacceptable regardless of what someone pays. Operable by one person because one person is who shows up on a bad week.
If that describes you, the trade-offs will feel like relief. If it does not, they will feel like limitations... because for you, that is exactly what they are.
Why I would rather you know
A user in the wrong situation is not a win. They struggle, conclude the software is poor, and are right... for them.
I would rather have a smaller number of people for whom this fits properly. So if you recognised yourself in the first half of this article, I genuinely think you should look elsewhere, and I would rather say so plainly than let you find out slowly.