Who we are

Operators, first.
Software, second.

Vespar was built by people who have worked a Saturday night, not by a product team imagining one.

Every venue leaks private-event revenue in the same two places: nobody is marketing the rooms, and the enquiries that do arrive land at nine on a Saturday and wait. We built the host we wanted when we were the ones behind the pass, and we run it in partner venues, on their guests, before it reaches anyone else.

Get Started

A kitchen pass at the end of service, brass lamps still lit over the counter, two cooks out of focus beyond it

What we hold ourselves to.

Three commitments. They decide what gets built, what gets cut, and what the host is allowed to say to a guest.

Restaurant-operator founded
The people who built this have worked the floor. That is why the host asks what a maître d' would ask, and why it hands off the moment a night stops being routine. The failure modes were learned the expensive way, in service.
Service first, software second.
Built for the owner, tailored to the guest
Two customers, one system. The owner needs the economics to work and the data to stay theirs; the guest needs to feel hosted, not processed. Where those pull apart, the guest experience wins and we find another way to make the economics work.
Your Stripe. Your guests. Your call.
Nothing invented
The host quotes from your live catalog or it says it will check. It never estimates a price, never invents a capacity, and never claims a capability that has not shipped. Anything on the roadmap is labelled roadmap, here and everywhere else on this site.
If it isn't shipped, it says so.

The roadmap is set in dining rooms.

Vespar is advised by the people who have to live with it: operators running private events week in and week out, and the technologists who keep restaurant systems standing up on a Friday night.

They see what is coming before it ships and they are not shy about it. When a venue tells us a feature would not survive service, that is the end of the feature.

What advisers do here

Review before it ships
not after, when changing it is expensive
Set the order of work
the next thing built is the thing venues keep asking for
Kill things
the most valuable feedback we get is a flat no

We build it in someone's dining room first.

Nothing reaches the platform until it has run in a partner venue, on that venue's guests. Partner venues get the host early, and in exchange they shape what it becomes: which room types matter, which questions guests actually ask, and exactly where a human has to take over.

A partner venue gets the host before general availability, hands-on bring-up with the menu, spaces and policies loaded together, a direct line rather than a ticket queue, and a say in what gets built next.

It is a slower way to build software and a much faster way to build software that survives a Saturday.

A private dining room set for thirty-five and waiting for them, long tables in pale oak with linen runners

Tell us about your rooms.

A few questions about your venue and the events you host, and we'll show you exactly what Vespar would take off your plate.