Luck Next

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)

Public collaboration and accounts: after sign-in, manage trial and subscription, sub-accounts and devices, and use the cloud designer plus common web print flows. Browser / LuckDesign share templates and quotas through the account system.

  • Accounts and admin: trial and subscription, sub-accounts and devices, profile and security.
  • Design and web print: cloud designer entry; Excel smart template print, scan print, list print, and print history (primarily Enterprise and LuckNext; sub-accounts need template-print and related rights).
  • Scan dedup vs print history: the former blocks duplicate business requests at scan or pick time; the latter traces who printed what and when. Different jobs—enable and configure separately.

Intranet offline design

For closed networks (enterprise intranet): intranet activation unlocks designer entry, serial counters, and related features.

  • “Offline” means deployment style: versus public cloud—not that every device must be air-gapped.
  • Scope: does not include the full public-cloud PostgreSQL / Redis / SSO and quota stack; follows delivery docs and is not feature-parity with SaaS.

LuckNext local service

Same name as the LuckNext product line (next-generation print partner worldwide) but here means server-side print services—a unified print output gateway for business systems.

  • Runtime: Windows, Linux, and similar servers; embedded Kestrel with bind address, HTTPS, template directories, and printers.
  • HTTP API: jobs, preview, templates, printer list, health checks—fit for unified print output or linking mobile browser design to print (on-prem, branch, or cloud per delivery).
  • Clients: LuckDesign installs on Windows, macOS, Linux, and Android with the same design experience as the browser; install LuckDesign for local print. The local service needs its own install and license; combine with tiers and cloud per contract.
  • Upstream systems: often ERP / MES / WMS / OMS—SAP, Oracle, Microsoft Dynamics 365, Infor, Yonyou, Kingdee, Chanjet, Inspur, Digiwin, and others. The API is vendor-agnostic; fields and auth per project. See LuckNext and ERP & business systems.

LuckData (on-prem data service)

An on-prem data service inside your network: connects to databases and business sources with controlled query/write, JWT APIs, print history, and enterprise table permissions; business data stays internal by default.

  • Cloud settings ≠ on-prem process: in cloud, users save connection configs that talk to this service (multiple configs, defaults, enable flags)—not the same deliverable as the running on-prem process; keep docs and ops clear.
  • Entry dedup vs print trace: process checks at scan time versus history and audit trails—evaluate separately in selection and rollout.

LuckCert

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

Developer demos and public SDK

Public tech hub: dev.lucknext.com.

  • LuckDesign SDK: embed the designer, load templates and variables.
  • LuckNext SDK: print jobs, printer lists, dialog print, and related calls.
  • Licensing: Enterprise usually covers the design SDK only; the LuckNext line can use both—see Versions & permissions.
  • Demos: LuckDesignSDK_Demo1, LuckNextSDK_Demo1; for production, use minified scripts under /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.

Product overview Label printing software Solutions inquiry