A venue operating system, live tonight.

Fennec is an operating system, not a feature. It runs the floor, the door, the bar, the bottles, the coat check, the guest record, the campaigns and the count in the stock room, off one set of records that every surface reads at the same time.

A venue running separate tools is running separate versions of the same night. Each one is right about its own slice and wrong about everything else, and the reconciliation happens in a group chat at 11pm.

The floor plan is a drawing that cannot tell anyone which table is still free. Tickets sell on a third-party page that knows the guest bought and nothing about where they will sit. The guestlist is a spreadsheet or a text thread, stale by midnight. The bar runs on a POS that has never heard of the table. Marketing is a separate address book.

Every one of them held a slightly different version of it. The same table could be sold twice. Somebody had to phone the office to ask whether T3 was gone.

Each tool was right about its own slice. None of them could be the record of the night, because none of them knew about the others. An agent cannot tell you what is leaking if the numbers are sitting in five accounts that never speak.

The guest picks the table over a photograph of the real room. Seat counts sit on each table, the bar and the backstage table are marked, and a legend says what is available, requested, booked, unavailable and selected.

The operator half is the floor plan editor. Every table carries a label, a section, a capacity, a table fee, a shape, a VIP flag and its own generated QR code. Layouts are versioned, so a Friday room and a Saturday room are two saved states. Activating a layout is what publishes the map the guest picks from, which is why the two screens can never disagree.

The public event page is generated from the event the operator built. The discover feed puts it in front of guests who came for a different room.

A coordinated agent network across operations, guests, campaigns, inventory and service, plus a Revenue Copilot that reads voids, pricing, promoters and inventory. Each agent owns one part of the operation and reads the same record as every other surface.

The host works the same map and confirms where the party actually lands, which is how a venue keeps control of its best tables without making a guest guess at a seating chart.

Every venue on the network runs its own nights, its own promoters and its own bar. They share one system, which is why an event published in one room shows up in a feed that guests of the others already use. No hours-saved or revenue figure is claimed for Fennec on this site.

Fennec is where our own architecture came from. Vishal built the core of it and the Ferry agent network, and that is the same pair of hands on the Uniserve engagement.