LuckDesign’s three editions cover design and local print; LuckNext covers unified print, HTTP API, and multi-node. Choose the edition by headcount and process—do not treat the free starter as a full plant stack. Headcount below reflects typical team size from past projects; prep days follow delivery timelines from past implementations.
| Edition | Fits whom | What you can do first | Typical next step |
|---|---|---|---|
| LuckDesign Standard | 1–5 people; about 1–3 days to prove local print | Everyday text, graphics, barcodes, and print | Upgrade when you need Excel merge, forms, or permissions |
| Professional | One department’s daily merge; about 3–7 days | Data and collaboration on top of Standard, opened by edition | Enterprise when you need the LuckDesign SDK and finer permissions |
| Enterprise | Multi-role sign-off; governance go-live about 10 days | Label managers / operators, template approval, LuckDesign SDK, opened by edition | Add LuckNext for HTTP API and submitting print jobs |
| LuckNext | Multi-station or multi-site; integration about 14–30 days | Unified print, API, multi-node policy | Local PCs still need LuckDesign; data can also come from LuckData / Excel / a staging table |
After governance is running, prints can use approved templates only. See versions and permissions and Standard.