About kasir.mu
Most point-of-sale software treats a working internet connection as a given. We built kasir.mu the other way round: the sale happens on the register, the cloud is the backup, and the hardware you already own is fast enough.
kasir.mu started in 2025 with a single requirement: a sale has to be finished before the network is involved — written down, printed, and counted on the machine in front of the cashier, not queued for a server that may not answer.
Everything else follows from that. The sync engine exists so registers and branches agree afterwards. The hardware layer exists so the printer and the scanner answer immediately. The price exists because software that needs less infrastructure costs less to run. We are not trying to win a feature-list comparison — we are trying to make the register the most reliable thing in the shop.
Cloud-first registers look identical on a product page. The differences show up in the middle of a lunch rush, on a shop floor with one weak router, in the hardware budget, and in what the monthly bill actually pays for.
Offline mode is a browser workaround. A web client that keeps selling from localStorage and replays the queue later drops sales, duplicates receipts, or applies them out of order when the connection returns.
Peripherals need a background translator. Printing a receipt, opening the cash drawer, or reading a barcode scanner from a web client means running a second local service on every register — one more thing that can die mid-service.
The client is heavier than the job. A bundled browser window needs a modern tablet or an i5 mini PC to feel responsive, so adopting the software means replacing registers that were working fine.
Peak-hour stock becomes a database lock. When two lanes sell the same last unit in the same instant, a cloud backend fights over row locks and the store can oversell while a request times out.
Infrastructure cost is priced into the subscription. Servers sized for the busiest day of the year are paid for all year, and that margin comes out of what a merchant is quoted.
kasir.mu is a native application: the same systems language on the register and on the server, a database embedded in the register itself, and direct access to the hardware.
The register runs its own embedded database. A sale is written locally the moment the cashier takes it, so it is complete before the network is ever involved.
The store keeps selling all day with the internet down — no lost sales, and no duplicates when the connection returns.
Registers queue their changes and reconcile with each other and with the cloud through one ordered protocol, so applying the same events twice still produces the same result.
Several registers in one store agree on the numbers, even after a day spent off-grid.
Receipt printers, cash drawers, barcode scanners, and card terminals are addressed directly by the application — no localhost bridge, no browser sandbox in between.
Receipts fire instantly and barcode lookups return immediately, with no background service to babysit.
The client is a small native application rather than a bundled browser, and memory use is measured in tens of megabytes instead of hundreds.
Keep the register hardware you already own — a low-spec PC, a cheap tablet, a fanless mini PC.
The server has no garbage collector and no runtime warm-up, so latency stays flat when every register checks out at once.
The lunch rush and the end-of-day close behave like a quiet Tuesday, with live stock shared across branches.
The engineering is ours to worry about. This is what it means on the shop floor.
| Built with | What you get |
|---|---|
| Local storage engine, no runtime pauses | No frozen screens or lag during the peak lunch rush. |
| Embedded database with peer-to-peer sync | The store never stops selling, even if the internet is down all day. |
| Direct printer, scanner, and drawer control | Instant receipts and barcode scans, with no bridge service to crash. |
| Small native client | Runs on the cheap or existing POS hardware you already have. |
| Efficient server, no container sprawl | Stable multi-branch stock accuracy at a price that stays low. |
Every merchant in Indonesia should be able to run a register they can trust on the hardware they already own — with no monthly bill deciding how much of the product they are allowed to use.
We measure that three ways: a sale never fails because of the network, the stock numbers agree across every register and every branch, and the software stays affordable enough that a warung and a ten-branch chain can both run it.
Concrete commitments, each one something you can check on your own machine.
Sales, receipts, shifts, stock, and reports all work without a connection. Cloud sync is an addition, never a prerequisite.
Records live on your own machine first, and you can export or back them up whenever you want. No feature is held hostage to keep you from leaving.
A low-spec PC, a tablet you already own, or a fanless mini PC is enough. A working register will never be made obsolete by us.
The free plan is a product of its own, not a trial, and the paid plans do not meter individual features.
Support in Indonesian and English, usually within one business day, from the people who build the software.
Download kasir.mu, ring up a sale, unplug the network cable, and keep going. That is the whole point.