Lakuyo is local-first by default, cloud-enhanced when you need it.
- Free tier: single-device operation, SQLite only for operational data — no Lakuyo backend.
- Core POS + Inventory must remain usable without Lakuyo backend connectivity.
- Free manual local backup / restore remains available.
- Personal Cloud Backup (POS-008) is optional user-owned Google Drive storage on Android and iOS (merchant’s Google account; not iCloud; not Lakuyo-hosted).
- Personal Cloud Backup is unlocked by a one-time purchase (indicative ≈ Rp100.000) or included while Pro is active; it still does not require the Lakuyo backend.
- Automatic Personal Cloud Backup is ON by default after Google Drive authorization for entitled users, but the merchant can turn it off and can always use Back Up Now.
- Google Drive availability is never required to open the app, manage inventory, or complete a Sale; provider availability affects backup operations only.
- Personal Cloud Backup is disaster recovery/device replacement, not live synchronization between active devices.
- Pro tier adds Lakuyo-operated sync / multi-device / cloud backup via Play / App Store subscription; Pro also includes Personal Cloud Backup while active.
- Kasir Sale completion (cash / EDC / static QRIS confirm) must succeed offline.
- Local product and stock operations must not require cloud connectivity.
This means cloud enhancement has two different boundaries:
- User-owned cloud storage — POS-008 Personal Cloud Backup; no Lakuyo data hosting.
- Lakuyo-operated cloud services — Pro subscription; sync, multi-device, Lakuyo cloud backup, and related services.
Backup integrity without backend DRM
Free and Personal Cloud Backup support one active operational device. Lakuyo does not require backend DRM solely to police manual copying. Instead, POS-008 protects the user’s backup lineage:
- each installation has a stable installation identifier;
- backup/manifest metadata carries source installation, revision, timestamp, and schema/format version;
- provider-side Google Drive metadata identifies one active Personal Cloud Backup writer per backup lineage;
- restoring onto another installation explicitly transfers writer ownership;
- the old installation can still work locally, but its Personal Cloud Backup writes stop until writer ownership is explicitly reclaimed;
- divergent local databases are never presented as safely mergeable through backup/restore.
If Pro expires, existing merchant-owned Google Drive backup data is not deleted. A prior one-time purchase remains restorable through the platform store; without that prior purchase, new Personal Cloud Backup writes stop until the merchant buys once or renews Pro, while recovery of an existing backup remains available.
Canonical domain vocabulary: Product/Domain Terminology.
Authoritative engineering rule: ADR-001 · Product/Business Model · Product/Plans and Entitlements.