Analytics
Menu engineering, staff scoring, retention curves
One platform for the floor, the pass, the bar, the shisha lounge, the till and the ledger. Built for rooms where a clumsy interface would be noticed — and remembered.
No card. No install. Menu live in about forty minutes.
A table cannot be released on an open balance.
Closing unpaid takes a role, a reason and your own PIN.
Every change is hash-chained, and the chain is recomputed.
12 surfaces, one spine
Not renders. Each card opens the real interface with live data — the offline queue, the role guard, the settlement rules and all.
Revenue, covers, kitchen load, settlement risk and counsel from your own numbers, on one pane.
Open itDrag-and-drop rooms, zone rules, merge and split, permanent table QR codes.
Open itA surface that reads like a brand site, not a PDF.
Open itWalk-in, takeaway, delivery, room service. Works with the line down.
Open itTickets the kitchen has marked ready, and who runs them out.
Open itSplit, partial, multi-tender, GST invoicing, dine-and-dash defence.
Open itCourse-aware tickets, timers, chef assignment, delay escalation.
Open itIncoming, building, past target, on the pass. A lane of its own.
Open itFlavour, base, head, coal cycles, refills, cleaning discipline.
Open itRooms, stays, a guest folio. A dinner charged to 214 and settled at checkout.
Open itPlans that derive from each other, seasons, close-outs, allotments.
Open itMenu engineering, staff scoring, retention curves.
Open itAnd the 15 screens that do the rest
The reason this exists
Releasing a table has exactly two callers in the codebase: a completed settlement, or a manager-authorised exception that writes its own audit row first. There is no third path — no admin panel, no support tool.
Staff flag a party as May leave without paying, which starts a countdown you configure per venue. Breach it and the manager console escalates in real time.
The system watches bills, tables, staff actions and money — never people. No biometrics, no facial recognition, no covert tracking.
Table cannot be released with ₹52,300 outstanding.
What the API returns when the guarantee is tested.
Your own PIN is required — not a manager's.
Closing unpaid needs a role, a reason code, a written note and the acting person's own PIN.
Settled. Table released.
The only unguarded path that frees a table.
Offline-first
Terminals hold a full local ledger. Every mutation carries a client-generated ULID, so an order has a permanent identity before the server has ever seen it.
Every mutation lands on the terminal with a device-scoped ULID and a Lamport counter before the UI acknowledges it.
A durable outbox replays in causal order with idempotency keys. Duplicates are impossible; partial batches resume.
Money never merges — it appends. Two terminals paying one bill is not a conflict, it is two payments.
What still works: taking orders, printing KOTs on the venue LAN, creating bills, cash and card-machine payments, opening and closing tables, stock, walk-ins, shisha.
Try the terminalRooms
A property running a till from one vendor and a front desk from another spends its life reconciling the two. Here there is nothing to reconcile. A guest eats downstairs, charges it to 214, and it is on their folio before they have left the table — same ledger, same audit trail, same login.
Book, check in, move rooms, extend, cancel, mark a no-show. Availability is counted from the rooms — close a day out, hold an allotment back for an operator, or oversell one deliberately.
Charges from the restaurant, the bar, room service and the minibar land on one signed ledger. The balance is the sum of it, so nothing can disagree with it. A mistake is reversed, never edited.
A plan carries its own price or derives from another — non-refundable is best-available minus twelve per cent, in one row. Seasons move the number and only the highest-priority one applies.
Checkout is the last moment anybody can ask, and after it the guest is in a taxi. A manager may let them go with a PIN and a reason, and a month of those is a number an owner can look at rather than a surprise in the accounts.
See the deskThe night audit
A restaurant closes its till and the day is over. A hotel has guests asleep in it, so the day is declared — one folio line per guest per night, at the price that night was sold at. It will be pressed twice at three in the morning, and it is safe to.
Channels, on your terms
Which channels, whose contract, and who owns the inventory when two systems disagree are yours to set — not assumptions in our code. Own it and an oversell is refused with a reason they can show; let them own it and the oversell is taken and shown in red on your calendar.
Plugin architecture
Every capability is a plugin with its own price and permissions. A disabled module is unreachable, not merely hidden — its routes 403, its jobs never enqueue, its tables are never queried.
Menu engineering, staff scoring, retention curves
Separate beverage queue and pass
Aggregator sync, dispatch, virtual brands
Profiles, preferences, spend, segmentation
Flavours, coals, refills, service timers
Stock, suppliers, recipe costing, waste
Live tickets, timers, chef assignment
Points, tiers, redemption at the till
Online + offline terminal, KOT, GST invoicing
Contactless menu, cart, live order tracking
Bookings, table assignment, waitlist, no-show priors
Staff records, clock-in, timesheets with overtime
Subscription
No add-on ladder, no per-cover cut, no quote to request. Card payments run on your own gateway account at your own rate — we take no share of them. These are the prices, and they are the same ones your neighbour pays.
Every module, for three weeks
₹0 for 21 days
Then pick a plan
No card, cancel by doing nothing
One restaurant, lounge or café. The whole floor, no rooms.
₹5,000 / year
2 months free — pay for 10, use it for 12
Save ₹1,000 · works out to ₹417/month
Hotels, resorts and small groups running rooms and F&B together.
₹19,999 / year
2 months free — pay for 10, use it for 12
Save ₹3,989 · works out to ₹1,667/month
Multi-property groups and brands. Group console, white label, priority support.
₹49,999 / year
2 months free — pay for 10, use it for 12
Save ₹9,989 · works out to ₹4,167/month
21 days of Signature on any plan. No card. Cancel by doing nothing. Changing tier afterwards is a conversation rather than a switch — we size it with you and adjust the invoice by hand.
Prices exclude GST. There is no permanent free plan: the twenty-one days are the free way in, and they run on a full Signature venue with a real database behind it rather than a sandbox.
Open an account
A trial is a full Signature venue with a real database behind it. Run a real service on it — a restaurant cannot evaluate a POS any other way.