How it works
TavernSync is three pieces: a control hub on site, a cloud service that authors configuration and relays remote commands, and the screens your staff actually touch. The important part is which of them your Saturday night depends on.
A small computer in your rack, connected to your network. It holds the configuration for your venue, speaks each piece of equipment’s own protocol, serves the wall tablets, and runs your schedule on its own clock. It is the only device that needs a path to the outside world, and it is the thing that keeps working when that path goes away.
Mounted where the work happens: behind the bar, by the patio door, in the manager’s office. They talk to the hub over your own network and never need the internet at all. Large targets, few of them, named after your rooms rather than after your equipment.
Where a venue’s setup is authored and versioned, and where your manager’s phone connects when they are not on site. It is how you reach the venue from outside. It is not what the venue depends on to run.
The decisions behind it
When the hub starts, it loads its cached configuration, brings up the drivers, opens the local network server for the tablets and starts the schedule engine. Only then does it try to reach the cloud. A venue with a dead uplink is fully operational before the internet is ever consulted.
A dead uplink costs you remote control and reporting. It costs you nothing in the room.
Your open, your happy hour, your Sunday layout — all of it runs from the building, not from a server somewhere. This is why an outage at four in the afternoon does not become a dark room at seven in the evening.
One button expands into many commands, executed in a deliberate order — set the input, then unmute, because the other way round is a room that blasts the previous source at everyone.
Each command reports its own result. If one receiver is dead, the audio zones still get set. A partial result is something your staff can see and finish by hand; rolling the whole thing back because of one failure would just hand you a dark room instead.
The hub opens a connection to us and holds it open. Your inbound firewall stays shut — there is no port to forward, and no service of ours listening inside your building. When your manager sends a command from their phone, it travels down the connection the hub already opened.
The honest consequence, and we would rather you hear it here: if the hub is offline, it is unreachable from outside by any means, and commands are not queued up to fire later. You are told the venue is offline. Telling a manager their command will land at some unknown hour — possibly in the middle of a service — would be a lie they would go on to act on.
Getting started
Make and model of every receiver, audio processor, switcher and screen, and which rooms they serve. Most venues have more capability in the rack than anyone is currently using.
Your zones get named the way your staff name them — patio, dining, main bar — not the way the equipment numbers them. Volume is nought to a hundred everywhere, whatever scale the underlying processor happens to use.
Open, game day, private hire, close. The buttons your staff press are the situations you actually have, not a menu of every device in the building.
Tell us what is in it and what your week looks like. We will tell you what TavernSync would do with it.