Orca Devs logo Orca Devssoftware studio · new delhi
Get a quote
Home Work GOD POS
runs inside the shop · not on the internet, on purpose

Billing that never stops working.

GOD POS runs a whole restaurant from one computer at the counter: billing, the kitchen screen, bill printing, stock, GST and the daily reports. None of it waits for the internet, so nothing slows down when the connection does.

node.jshono better-sqlite3websockets electronesc/pos cloudflare d1
local network only · not published
GOD POS table view
Screenshot pending Send a screen capture of the table view:
assets/screens/god-pos-tables.png
main parts
11
screens, one computer
4
commits
79
other companies in your data
0
status
Installed & running
why build another billing system

Because the rented ones stop when the wifi does

Most software sold to small restaurants is rented, not owned, and slowly gets expensive. You pay every month for a billing system that becomes a useless box the moment the connection drops, and you never really own your own sales data.

GOD POS does the opposite. Everything is saved on the computer at your own counter first. That computer updates every other screen in the building instantly over your shop wifi, and bills print straight to the printer. Taking an order and printing a bill never touches the internet at all.

A backup copy is sent off-site for safety, and each restaurant gets its own separate copy, never mixed with anyone else. If that backup fails, service carries on as normal and nobody notices.

Nothing between taking an order and printing the bill touches the internet.

try it

Unplug the internet and see what still works.

This is the honest version. Switch the connection off and watch which parts of a normal evening keep working, and which two really do need the internet back.

Friday, 8:42 PM · sixteen tables running internet up
Take an order at the tillSaved on the computer at your counter working
Send it to the kitchen screenSent over your own shop wifi, never the internet working
Print the GST billGoes straight to the bill printer working
Split settlement, held orders, day-end reportAll local reads and writes working
Take an online card paymentRazorpay genuinely needs the line — cash and card machine still work working
Sync the off-site backupQueues locally and drains automatically when the line returns working

Everything is green because the connection is up. Turn it off.

the screens

What the staff actually look at.

Captures from an install, not reconstructions. Anything not here yet is marked as pending rather than filled in with a drawing of what it might look like.

architecture

One computer. Four screens. No internet in the middle.

One program on the counter computer holds all the data. Every other screen in the building talks to it over your own shop wifi: the billing screen, the kitchen screen, a manager's tablet and the reports view.

The terminal ships as an Electron application so it installs like a normal Windows program, launches on boot and recovers after a power cut. Receipts print straight to the bill printer rather than going through a driver that may or may not exist on the machine.

Off-site, a Cloudflare Worker writes to a D1 database that is isolated per restaurant. That is a deliberate cost: pooling would be cheaper and we do not do it.

server
node.jshonowebsockets
local storage
better-sqlite3wal mode
clients
electroncapacitorreact
hardware
esc/pos thermalcash drawerwindows install
off-site
cloudflare workerd1, isolated per venue
Why there is nothing to click. The point of sale has no public address. It runs on a machine inside the restaurant and is deliberately never exposed to the internet — that is the entire feature. We are happy to walk through the real thing on a call.
want to see it

A walkthrough beats a screenshot.

We will screen-share the real install, on a real evening's data, and you can ask it awkward questions.