FAQ

We earn from cloud subscriptions and commercial licensing, not from locking local features. Open source buys installs and trust — an asset worth more than the code itself.

It promises that every local feature in today’s open-source edition stays free and never requires online activation. Two things make that binding: Apache-2.0 grants you the right to use, modify and redistribute the code, so nobody can take those features back; and a separate trademark policy keeps the project name apart from the code licence.

In a local database file in the app data directory — not on our servers. To move, copy the data file and config to the new machine; the app reads them on start. Back the data directory up to an external drive weekly.

Cloud POS charges yearly and keeps the core logic on the vendor’s servers, so offline usually means read-only. Data sits with the vendor and export means asking. This project inverts that: offline-first, data local, nothing locked, no cut of your turnover. The trade-off is that out-of-the-box multi-store and remote reporting belong to the paid editions.

Yes. Register, order hold, refunds, tables, membership, shifts, reports and printing all run locally. Only cloud modules — remote reports, cloud printing, the owner app — need a network.

Commercial use is fine. Apache-2.0 lets you modify, distribute and even sell a derived build without open-sourcing your changes. The only limit is trademark: don’t market your fork under the project name or logo — rename it and you are clear.

ESC/POS 58 mm and 80 mm thermal receipt printers over USB, serial or LAN, with automatic port detection and per-station routing for kitchens. Label printers and cross-network cloud printing are out of scope for the open-source build.

Search existing issues first, then open one with version, OS, reproduction steps and logs. Feature ideas go to Discussions; the most-upvoted ones get scheduled into the roadmap.

No. You can run a single shop completely without a subscription. Cloud and commercial editions solve what the open-source build cannot: multi-store, central kitchen, remote reports, QR ordering, cloud printing.

Schema migrations run automatically on start and the current data file is backed up first. For major-version jumps, try it on a spare machine before rolling out.