Why I built FireballKaraoke

Every karaoke host has had this night, or is going to.

The laptop dies at 10:40 on a Saturday. The room is full, the rotation is twenty deep, and the machine that was running the whole thing is a brick. You have a backup of the music, because everybody has a backup of the music. What you do not have is a backup of the night: who has sung, who is up next, whose turn got skipped when they stepped outside, and the key that one regular needs on every Journey song.

All of that lived in the software, and the software lived on the machine that just stopped being a machine.

You get through it. Paper, apologies, a bar that mostly does not notice. And somewhere on the drive home it lands that what you lost was not data. It was years of knowing your room, and the tools treated it as disposable.

The hard parts were never technical

Ask a working host what makes a night difficult and nobody says audio routing.

Somebody hands you a slip while you are cueing the next track. A regular walks in and you want to greet them by name and already know their song. A group of six turns up at nine and has to be fitted in without gutting the rotation for the people who came at seven. A singer takes the mic in a key you set for them three weeks ago and neither of you can remember what it was.

None of that is exotic. It is the job. And the software available for it treated all of it as an afterthought, because it was built as a playlist manager with a karaoke mode bolted on the side. The DJ tools were fine. The karaoke layer on top of them was missing.

Built the other way round

FireballKaraoke started as a plugin for VirtualDJ, which is what a lot of us already run, because asking hosts to replace their whole rig is the wrong ask. The decks work. The library works. What was missing was the layer that remembers the room.

So the plugin does the karaoke part and nothing else. Rotation with fair insertion, so a late group cannot steal the night from the early crowd. A profile for every singer, with their history and their keys. An audience screen that carries your branding rather than ours. A sound board for the stings and the drops. Recordings, if you want them.

And it runs on the machine in front of you, with no account and no connection. That last part is not a limitation waiting to be fixed. It is the whole point, and it is worth its own post: a karaoke night should never be something that somebody else's servers can take down, ours included.

The cloud half, added second and on purpose

Some things genuinely cannot work without a network.

Phone requests beat paper slips, and hosts who switch tend to say the same thing about how much quieter the booth gets. Approving a song from the far end of the room beats walking back to the laptop. Singers who move between venues want their history and their keys to come with them.

All of that needs a connection, so it lives on FireballKaraoke.com, and it is optional. The plugin does not phone home, does not check a licence, and does not care whether you have ever heard of the website. Never subscribe and nothing you already had stops working. Subscribe, then watch the venue Wi-Fi fall over mid show, and the night carries on while the requests catch up on their own.

Where it is now

The plugin is free and out. The cloud service runs the request page, the host remote, singer accounts, and encrypted backups of exactly the thing that goes missing when a laptop dies at 10:40 on a Saturday.

If you host karaoke, take the plugin. It costs nothing and it will not ask you for anything. If it makes your nights easier and you want the phone half too, the first month is free.

And if it does not do something your room needs, say so. What gets built next comes almost entirely from hosts who did.