Luck product ecosystem

Beyond the browser web app and LuckDesign online design (text, graphics, barcodes, QR codes on labels), projects can combine cloud services, intranet offline design, LuckNext, LuckData, and tooling.

Components are purchased and deployed separately – not everything ships in one installer.

Four license tiers (Standard / Professional / Enterprise / LuckNext) have dedicated pages; boundaries: Versions & permissions.

Why multiple components?

You can compose what you need without assuming one package does it all. Fits retail, manufacturing, logistics, healthcare, FMCG: start with the designer, add cloud and audit later; deploy LuckNext at plants or branches as a unified print output (intranet, cloud, etc. – per contract), coordinated with HQ or business systems.

  • Accounts and collaboration via cloud or intranet activation
  • Unified print gateway and HTTP API via LuckNext
  • Enterprise data connectivity via LuckData
  • Integration: Luck SDK demos and /sdk/ scripts; LuckCert for local or intranet HTTPS dev – not a public CA substitute

Luck cloud (online)

Sign-up, trial, subscription, sub-accounts and devices, profile and security; cloud designer entry; Excel smart template print, scan print, list print, print history (primarily Enterprise and LuckNext; sub-accounts need template-print and related rights). Links browser / LuckDesign via accounts, templates, and quotas.

Scan deduplication blocks duplicate business requests at scan or pick time; print history traces who printed what and when – different jobs, enable and configure separately for process and compliance.

Intranet offline design

For closed networks: intranet activation unlocks designer entry, serial counters, etc. “Offline” here means vs. public cloud deployment – not that every device must be air-gapped. Does not include the full public-cloud PostgreSQL/Redis/SSO stack; scope follows delivery and is not feature-parity with SaaS.

LuckNext local service

Same name as the LuckNext product line (next-generation print partner worldwide) but refers here to server-side print services on Windows, Linux, etc. – Kestrel, bind address, HTTPS, template dirs, printers, HTTP API (jobs, preview, templates, printers, health) – a unified print output for systems or linking mobile browser design to print (deployment: on-prem, branch, cloud – per delivery; LuckDesign clients on Windows, macOS, Linux, Android match the browser web experience). Separate install and license; combine with tiers and cloud per contract.

ERP/MES/WMS/OMS upstream brands often include SAP, Oracle, Microsoft Dynamics 365, Infor, Yonyou, Kingdee, Chanjet, Inspur, Digiwin, etc. – API is vendor-agnostic; fields and auth per project.

LuckData (on-prem data service)

LuckData runs inside your network: connects to databases and business data with controlled query/write, JWT APIs, print history, enterprise table permissions; data stays internal. In cloud, users save connection settings that talk to this service – multiple configs, defaults, enable flags. Cloud-stored connection metadata is not the same deliverable as the on-prem service process – keep docs and ops clear.

Entry deduplication (e.g. at scan) vs. print and data trace (history, audit) are different layers – evaluate separately in selection and rollout.

LuckCert

Helper for dev HTTPS (e.g. mkcert, OpenSSL) on workstation or intranet – not a substitute for public commercial CA policy.

Developer demos and public SDK (Luck SDK / dev.lucknext.com)

Built-in or delivered demos for joint testing; public tech hub: dev.lucknext.comLuckDesign SDK embeds designer, templates, variables; LuckNext SDK handles jobs, printer lists, dialog print. Licensing: Enterprise usually design SDK only; LuckNext line can use both – see Versions & permissions.

Live demos: LuckDesignSDK_Demo1, LuckNextSDK_Demo1; production: use minified scripts from /sdk/ (versions online) – never paste secrets in public docs or repos.

Relationship to product overview

Product overview has a quick “ecosystem components” table; this page expands responsibilities and edges. Selection still starts from that list.