Your restaurant, on your own machine.

Offline first

The till keeps working

The server runs in the restaurant, not in a data centre. Adding to a bill works with the network unplugged and drains to the server when it comes back. Firing to the kitchen and settling a bill deliberately do not work offline, because a total only the server computes cannot honestly be guessed at on a tablet.

No account

Nothing to sign up for

No licence key, no subscription, no telemetry, no paid tier. One installer gives a restaurant a working system on its own hardware. The data stays where the restaurant can see it.

One binary

Three shells, one download

Not three applications. The signed-in staff member's role decides whether they get the till, the kitchen screen, or the manager shell. One codebase, one thing to explain.

Point of sale

Till

Floor plan with live bill totals per table. Modifiers, kitchen notes, and quantities. Send to kitchen in one action. Partial payments that accumulate until a bill covers itself, cash with tendered and change, discounts by percentage or amount, each with a reason and each written to the audit log.

Voids are recorded rather than silently deleted.

Kitchen display

Pass

Tickets appear the moment the till fires them, sized to read from across a kitchen. Tapping an item walks it queued, cooking, ready. Timers count from when the ticket was fired and the card ages against a ten-minute target.

A ticket's border and timer carry how long it has waited; its dots and chips carry what state each item is in. Because ageing never touches the status colours, a late ticket full of cooking items still reads correctly at a glance.

Back office

Manager

Menu with categories, photographs, tags, preparation times, modifier groups, and a sold-out toggle. Tables grouped into zones. Staff accounts with five roles, each described in plain language rather than by permission flags.

A manager can reset a forgotten PIN without anyone opening the admin dashboard.

Reporting

Takings

Sales broken down by item, by who served it, and by hour, with CSV export for the bookkeeper. Shifts with an opening float, a counted close, and the variance called out.

Takings are counted by when a bill closed, not when it was opened. A table seated before a shift began and settled during it belongs to that shift.

Table-side ordering

Guest ordering

A guest scans the QR code on their table and orders from their own phone. It is a web page, not an application to install, and it runs on the same server and port, so nothing is exposed to the internet.

Guests reach exactly three public routes; every collection stays staff-only. No price is ever taken from the request.

Hardware

Printing

Network thermal printers over TCP 9100 using ESC/POS, which is what virtually every restaurant printer already speaks. No driver to install: a printer is an address and a paper width.

Thermal printers speak code pages, not Unicode, so any non-ASCII currency symbol falls back to its three-letter code. Every printable byte the builder emits is plain ASCII, and a test holds it to that.