Specifications.

99.99% a month, published on a public status page.

Every module reads and writes the same records. Nothing is copied between modules, so nothing needs syncing.

Two bookings on one table at once, two prices for the same time and a status going backwards are all refused by the database itself, not just by the screens.

Add fields to any record without a developer. They work in filters, reports, exports, imports and the API like the built-in ones.

Rename, add to, reorder or switch off the lists of statuses, categories and reasons.

Prices, products, policies, layouts and branding keep every version. Schedule a change ahead, such as a new price list from 1 January.

Takings after midnight count to the day you opened, and the night the clocks change is handled properly.

Switch a module on and it's ready straight away, with all your existing records already in it.

Hosted in the UK across two locations. Backups are test-restored on a schedule, and there's a public status page.

Load-tested before big on-sales. If demand goes past that, guests wait in a short online queue and the site stays up.

An assistant on every screen, built on the same MCP server. It answers and acts with your own permissions, and every action is logged.

Every screen in Hangar runs on the same public API you get. Nothing is screen-only.

Documented in OpenAPI. An old version keeps working for at least 12 months after a new one ships, and you're told by email.

Anything that creates a record or moves money can be retried without making a duplicate or charging twice.

Issue your own keys, read-only or read-write, limited to the venues and modules you choose. Each one shows when it was last used.

Connect an app or assistant as a named person, with exactly that person's permissions. Revoke it whenever you like.

MCP server included. Every action is logged against the person ("Refund £24.00, by Jo Smith, through an AI assistant"). Bulk messages and money actions show a preview and ask before they run.

Every change is published as an event in the same step it's saved, so no event is ever lost and none is sent for a change that didn't happen. Events are kept for 90 days to replay.

Subscribe by event type, venue and module. Every delivery is signed and timestamped, failed ones retry for 3 days, and the delivery log has one-tap resend.

A public availability feed built to be read by Google, AI assistants and listing sites.

The booking widgets, code libraries, MCP server and connectors are open source.

Every import runs as a dry run first and lists every problem. It can be undone in one go, and running it again never brings anything in twice.

Each staff device keeps today and the next 14 days: bookings, floor plans, prices, guests with their allergies and notes, and who's on shift.

When the internet drops, the devices in a venue keep each other up to date over your own wifi.

Runs in the cloud, so guests can still book when your venue's line is down.

Signed QR codes are checked without internet. Anything used twice on two devices is flagged when they reconnect.

Changes made offline are all kept. Anything that oversells a space or spends a balance twice goes to a manager.

Options from a 4G or 5G back-up router to satellite and battery back-up, with head office told when a line drops.

Booking runs on your own domain as part of your page, not a box in a frame. Your analytics and ad pixel see every step.

Every step loads in under a second on a phone.

Guests book without making an account, and Apple Pay or Google Pay fills in their details.

Every option shows the price per head from the first screen, with any service charge already in it.

Age limits, times and minimums are explained on screen. Nothing is greyed out without a reason.

Several activities in one booking, with back-to-back times suggested.

A chosen slot is held for 10 minutes, and the last places can never be sold twice.

Guests can ask to hear when a slot frees up, and they're shown the nearest open times and the same slot at your nearest other venue.

Every activity and package has its own link, so each ad opens straight on its offer.

An Apple or Google Wallet pass and a calendar entry, both updated if the booking changes. Guests change, add to, pass on or cancel their booking from a link, with no login.

Every step is tracked. Test two versions of the booking flow against each other and see where people drop out.

The guest booking flow meets WCAG 2.2 AA.

Bookable straight from Google search and Maps.

Draw each area yourself, join tables for big groups, and keep different layouts for different nights.

List, floor plan and timeline views with drag to move, and partial check-in ("6 of 8 here"). Warnings for allergies, VIPs, under-18s and birthdays come from the booking, so nobody types them in on the night.

A waitlist guests join by QR code or from Google with no app. The wait time is worked out from when tables will actually free up.

Automatic table assignment for the fewest empty seats, kitchen pacing every 15 minutes, sittings and turn times, and table status straight from the till.

Each guest orders through the group link. Allergies print on the kitchen ticket against each guest, and a recipe change re-checks every future pre-order.

Full payment, a deposit per person, a card hold or every guest paying their own share, set per product.

The full amount is held on the organiser's card. Friends pay their share from one link in the group chat, and the organiser's card covers whatever's left when the window closes. You're never left with an unpaid booking.

Per person, in equal shares, by seats or by amount.

The organiser sees who's paid and who hasn't, with a remind button and automatic reminders.

Every friend who pays gets their own guest record.

Choose non-refundable, free date change, refundable or credit, with a cut-off. The wording writes itself into the booking, the confirmation and the terms.

Everyone is refunded in full and told automatically. Move an event to a new date and every booking moves with it.

The evidence is put together for you: the booking, the terms accepted and when, the messages sent and the check-in.

None, paid by the guest or absorbed by you. Fixed or a percentage, and reported separately.

Day and time, dates and seasons, demand with your own floor and ceiling, early bird and last minute, group size, codes, member rates and channel.

Each rule reads as a sentence before you save it ("Groups of 8 or more: take £2.00 off").

Pick a date, time and group size to see the price and which rules made it.

Test any price rule on a share of guests before it goes to everyone.

Batches of unique codes, with limits on total uses and uses per guest.

Ticket types, release waves, allocations for partners and promoters, bench seating that keeps each party together, and seat maps if you want them.

Ticket money goes straight to your own account, not held until after the event.

A waiting room gives everyone a random place in the queue at on-sale, with presales, limits per person and bot checks. Wallet QR codes change every few seconds, so a screenshot won't scan.

Only through Hangar, at face value or a price you cap.

Scan on any staff phone, offline included, with ID prompts, live counts per area against capacity and a guest list for each promoter.

Each one has their own link and code, with commission tracked. Promoters never see guests' contact details.

A pipeline with your own stages and proposals built from your products. Clients sign online and pay the deposit, and instalments are chased when they're due.

Pencilled dates take the space off sale and expire on their own.

The booking sits beside the bill, so deposits and pre-orders are already on it.

Scan a guest's pass to serve their included drinks. Nothing can be served twice, even offline ("Already served at 21:14 by Jo").

Bar and table service, order and pay at the table, kiosks and kitchen screens.

"Eat in or take away?" is only asked when the VAT is different.

The card total is checked against the provider's figures, and a cash-up is locked once a manager approves it.

One per terminal and per venue, numbered in order and kept permanently.

Labels with full ingredients for food made on site print from the till, for Natasha's Law.

A log of refusals and age checks, ready for a licensing officer.

Till signing for the countries that require it, such as Germany, Austria, France and Italy, set by country.

Card details never enter Hangar. Payments go through your provider's secure fields and terminals.

Choose your card provider, and change it later with both running side by side during the switch.

Card online, Apple Pay, Google Pay, card holds, a card on file as a guarantee, pay links, gift card balances, terminals, cash and accounts.

Every amount is in whole pence and rounded once. VAT is worked out once per line.

Payments, refunds and balances are never edited. Every correction is a new entry showing who, when and why.

A refund can't be more than was taken and a balance can't go below zero, even with two tills working at once.

Refunds over a role's limit need a manager PIN. Nobody can refund or void their own sale.

One ledger for gift cards, vouchers, booking credit, accounts and wristbands, spendable offline up to a limit you set.

Each voucher's VAT treatment is set by its type, so staff never have to choose.

Your provider's payouts are matched daily by venue and terminal, and card fees go to the P&L.

Once a period is closed, nothing can be dated into it. Reopening needs two people.

Every amount is stored inc VAT, as VAT and ex VAT. One switch flips every figure on screen.

A rate change at midnight applies from midnight, even in the middle of a shift.

One profile per guest across every venue and brand, with every visit, spend and message on one timeline.

Email and mobile are unique to one guest, and a merge can be undone.

The first and latest source on every guest and booking: channel, campaign, ad, click IDs, UTMs and promoter code.

Each consent keeps the exact wording the guest saw, where and when.

Someone who gives you one detail is kept as a lead and becomes a guest on the same record when they book.

Kept on the guest's record only when they ask you to remember them.

Bans by venue with an end date, flagged to staff. The reason is never shown on a screen the guest can see.

Bar staff see a name, tags and allergies but not a phone number. Bulk export needs a senior role and is logged.

Results from the second letter typed, names in either order, or the last four digits of a mobile.

Set by your own rules, such as "spent over £500 this year".

Every email has its own reply address, so replies land on the right guest and booking.

One thread per guest per venue across every channel, with the booking at the top.

Opens on "Needs reply", with handover, notes, mentions and reply-time targets that alert the duty manager.

Saved replies fill in from the booking, and any gap shows red before a message is sent.

Every message from every module goes through the same consent check.

Quiet hours by default and one reminder for several bookings on one night. Unsubscribing from marketing never stops booking messages.

Your own sending domain, with guest email kept in the UK and kept apart from every other operator's.

Email, then WhatsApp, text, Instagram, Messenger and website chat, all in the same inbox.

Segments, journeys, A/B tests with hold-out groups, ad audiences and conversions sent back to the ad platforms.

A review request goes to every guest, unfiltered.

A wifi sign-in in your brand, loyalty you set up yourself and an app in your brand.

Everyone on one record, with or without a login, including people with several jobs across different companies.

12 roles to start, all editable and given per venue, with refund, discount and approval limits you set.

Tap your name and enter a PIN. A leaver is marked in two taps and signed out of every device at once.

Two-step sign-in or a passkey for anyone who can reach guest data, payments or settings. Google and Microsoft single sign-on.

Sign a lost device out remotely and wipe its data.

One app for every module, showing only the modules you've switched on.

Rota, clock-in, holidays, tips and tronc, checks, licences, repairs and a staff wiki.

Staff needed per hour, role and area, updated the moment a big booking lands on a day that's already on the rota.

One list of everything you sell or stock, used by every module. A walk-in game of pool and a booked one are the same product.

Built from your real products, with takings split by each part's price and VAT following each part.

Worked out from the recipe and impossible to type over, using the 14 UK allergens.

Kegs are counted in ml, so a pint and a half come off the same keg. GP % shows beside every price as you type it.

Upload a price list and see the GP change before you accept it ("Pint GP: 71% to 69%. 14 products affected.").

Mark it sold out once and it's gone everywhere at that venue straight away.

Change a price and see every package it's in before you save.

Bring your products in from your old till by upload, checked first and undoable in one go.

A report of what was paid for but not served.

One screen per date with what's on, the target, the forecast, bookings, staff needed, live campaigns and notes.

Your monthly budget is spread into daily targets using each venue's own weekday pattern, with event days weighted up.

Covers forecast from booking pace plus walk-ins, tracked against last year and target, with a 13-week view across the group.

You hear when a day or event is falling behind, a site is short-staffed or labour is over budget, with an 8am digest and a Monday summary.

By venue and during the shift: sales, GP and labour against the day's target. Click any figure to see the transactions behind it.

Targets use each venue's real VAT mix, never a flat 20%.

Budgets lock at the start of the month, and reforecasts sit beside the original.

A daily summary journal per venue, anything that fails waits in a queue with a retry button, and a daily check against your ledger. Your ledger always wins.

Bills are read and coded automatically, duplicates are caught (even ones already in Xero), and price rises are flagged.

A supplier's new bank details are never accepted from a bill or an email.

The person who builds a payment run can't approve it.

Custom reports, scheduled emails, exports and a data feed to your own warehouse. Ask an AI assistant "How is Saturday filling?" and get the answer through MCP.

Companies, brands, venues, areas and spaces, including separate trading, employing and payroll companies.

Copy a whole venue, from layouts and products to prices and settings, to open the next one.

Set a closing date and Hangar lists every future booking to move or refund.

Move a venue to a new company from a date, and past takings stay with the old one.

Several brands on one account. Guests never see the name Hangar.

Premises licence, DPS and capacity limits stored on each venue, with changes saved ahead of their date.

Currency, language, time zone, tax and privacy rules are settings per operator and per venue.

Tax is stored in parts, ready for countries that charge more than one.

Hangar isn't tied to any hardware. It runs on iPads and Android tablets, iPhones and Android phones, and any computer with a web browser.

One app for iPhone and Android. Staff can use their own phones with a PIN login.

Any iPad or Android tablet. Staff tap their name and enter a PIN, so one device serves the whole team.

The same screens in any web browser.

Card machines from the provider you choose, and Tap to Pay on staff phones.

The phone's camera scans tickets, passes and vouchers, so there's no separate scanner to buy.

Orders go to kitchen screens or printers.

A tablet by the door or the bar where walk-ins book and pay.

The host stand's tablet keeps the venue's devices in step when the internet drops, so no extra box is needed.

The database itself refuses to show one operator's data to another. Every release is tested against every route and stopped if one gets through.

One log across every module that nobody can change or delete, the owner included.

Our support team only sees inside your account with your approval, for up to 7 days, and every action is logged.

Encrypted in transit and at rest. No key ever returns passwords, PINs or card details.

Independently tested before launch.

You're the controller and we're the processor, under a data processing agreement. Privacy rules are presets for each country.

Access and erasure requests are one action each, with deadlines tracked. Erasures are applied again after any backup restore.

Non-essential tracking only fires after consent.

We tell you straight away, so you can meet the ICO's 72 hours.

Export everything in standard formats and have your data deleted.

Bookings from another system can come in by connector or upload.

Staffing needs export to the rota tool you already use.

Enquiries from venue-hire marketplaces go into your pipeline, and your events go out to ticket sites and Google.