Point of sale + control plane
The till thatkeeps trading.
RidgePoS runs a restaurant’s counter — billing, kitchen screens, receipts, online orders — and keeps running when the internet doesn’t. This console is where the whole fleet is licensed, watched and helped, from one place.
Not a screenshot — the register, ringing an order up right now.
Alive, end to end
An order’s whole life, on one loop
Rung up at the counter, cooked on the kitchen screen, printed at the pass. These three run the same choreography the real product runs, thousands of times a day.
Billing that never waits
Exact-cent math, split payments, UPI and cards — and the drawer still opens with the network down.
- 2× Smash Burger
- 1× Fries — no salt
- 1× Paneer Wrap
- 1× Cold Brew
- 3× Tacos
- 1× Salad
Kitchen screens on any tablet
The till serves them over the shop's own LAN. Tickets arrive the second they're sent, and bump when the food is up.
RIDGE DINER
Receipts, tickets, Z-reports
Thermal printers on plain TCP — receipts at the front, prep tickets in the kitchen, the day's Z-report at close.
Why it was built
Real counters break software built in quiet offices
Shop internet dies at 7pm
The till is offline-first: it bills, prints and closes the business day with no connection at all. Online orders queue safely at the gateway and land the moment the link returns — nothing is lost, nobody stops selling.
One counter becomes four
A hub till serves the whole shop: extra counters join over the LAN, and any tablet with a browser becomes a kitchen screen. How many of each a shop may run is set in this console — and the licence itself enforces it.
Orders come from everywhere
The shop's own website, DoorDash Drive couriers, aggregators, UPI payments — one gateway carries them all, and an order is acknowledged only after it is safely on the till's own database.
A licence must never brick a shop
Tills run on signed 30-day leases. If a subscription lapses, only new sales pause — reports, refunds, exports and day close keep working, and every enforcement step is written into the shop's own audit log with a reason.
Support that asks first
From this console, support can see and operate a till live — but only after the shop taps Accept, with an unmissable banner the whole time, a hard 15-minute cap, and an audit entry under the supporter's own name.
One console runs the fleet
Licences, plans and prices, capacity caps, integration keys, remote support — everything is watched and decided in one place, and the services keep serving even if the console itself goes down.
The console behind it
One screen, every shop
Licences are minted here, plans and prices decided here, capacity caps set here, integration keys stored here — and a struggling shop can be helped here, live, with their consent. Every action lands in that shop’s audit log under a real person’s name.
Sign in to Control0
days
a signed lease keeps a till trading offline
0
min
hard cap on any remote-support session
0
markets
US and India — tax, currency and payments native to each