You cannot find out whether List & Label works in your Linux container without buying the top tier first. Everything that makes it deployable off Windows, meaning the Cross Platform engine, container hosting, the Web Report Designer, and the combit Report Server, sits behind Enterprise at €1,990 per developer in year one. On Standard or Professional, asking whether this runs in Docker is a purchase order rather than a feature flag, and the answer arrives after the money does. IronPDF answers the same question on its only tier, before any purchase order, in an afternoon of turning markup into a PDF.
IronPDF is ours. We build it at Iron Software, and what follows explores the Enterprise-only tier that gates List & Label on Linux, next to IronPDF running the same render call from its only tier.
What Does the Tier Ladder Gate?
The vendor has shipped this component inside .NET applications since 1992, and version 31 reached general availability on 16 October 2025. The tier ladder is where a deployment question turns into a purchasing one.
| Capability (document output only) | List & Label 31 | IronPDF |
|---|---|---|
| PDF export of a designed report | Native, from a .lst or .lbl definition |
Renders markup, a file, or a URL through ChromePdfRenderer
|
| HTML and CSS in the document body | Custom component, restricted CSS subset, no browser engine | Chromium rendering of HTML, CSS, and JavaScript |
| Direct rendering of a URL or Razor view | Bound into a report definition first | Direct, via RenderUrlAsPdf or a .cshtml view |
| Manipulating an existing PDF | Outside the export pipeline |
PdfDocument.Merge, split, stamp, encrypt |
| Tier required for Linux and container hosting | 3rd tier, Enterprise | 1st tier, and the only tier |
| Entry price per developer, first year | €740 Standard, €1,390 Professional, €1,990 Enterprise | 1 licence, 1 tier |
Table 1. Document output only, List & Label 31 against IronPDF, with tier gating shown where combit applies it.
The last two rows keep this comparison honest. Everything above them is a document-output question, while those two are what the tier ladder costs to answer.
€1,990 Buys the Answer to a Linux Question
That ladder is not arbitrary, and the vendor is transparent about what sits where. Standard and Professional are Windows desktop reporting. Enterprise adds List & Label Cross Platform for Windows, Linux, and macOS, unlimited use in web and server applications, the Web Report Designer and Web Report Viewer, the browser-based Report Server, premium support with a 14-day bug-fix commitment on even-numbered versions, and additional designer languages. Priced as a package, that is defensible. Priced as the cost of finding out whether a container deployment is viable, it front-loads the commitment before the evidence exists.
A second constraint inside the cross-platform story survives the tier upgrade. The migration documentation states plainly that the designer is not yet available for List & Label Cross Platform, and that templates must therefore still be created using the classic version on Windows and then converted to the new JSON format. A Linux-hosted deployment on the Enterprise tier therefore keeps a Windows machine in the authoring pipeline. The runtime went cross-platform ahead of the tool that feeds it, which is a reasonable order to build things in, and it means a team with developers on macOS is planning around a Windows box for report editing regardless of what the runtime supports.
The HTML path carries its own boundary. The documentation states that List & Label uses a custom component for HTML rendering supporting a restricted CSS subset, and that correct rendering of entire web pages is not that component's main intent, while the designer docs warn against complex scripts, redirects, and unusual CSS. That is an accurate self-description rather than a hidden limitation, and it means a layout built for a browser reaches PDF through IronPDF without a rebuild and through combit's component only with one.
On security, a search of NVD, the GitHub Advisory Database, and Snyk turns up no advisory naming combit or List & Label as the affected vendor or product. Two things follow from that. It is not the same as an absence of vulnerabilities, because the vendor is not a CVE Numbering Authority, so a missing public record carries less evidential weight than it would for a company filing its own advisories, and a plain keyword search on the product name is a poor filter since the phrase is ordinary English, so a real check confirms the CPE vendor string reads combit. Having granted that, the risk that actually decides this product is elsewhere, because the deployment surface, the Windows authoring dependency, and the tier gate are all fixed at purchase time.
Where Does That Breadth Stop Short?
The surface area is wide. The product pages list roughly 30 export formats, over 250 formula functions, more than 40 built-in .NET data providers, and chart, map, crosstab, barcode, and gauge objects. Version 31 added something concrete on top of that, namely out-of-the-box ZUGFeRD and Factur-X 2.3 e-invoicing in the PDF export path, covering the BASIC, EN 16931, EXTENDED, and XRECHNUNG profiles. That produces a conformant PDF/A-3 invoice with the structured XML embedded as an attachment straight from a report definition, with no separate compliance library in the build. For anyone shipping into European markets where e-invoicing is becoming mandatory, that covers an integration the build would otherwise carry on its own. That matrix is Enterprise-tier work, and the Linux question it leaves open is the one IronPDF answers on its first tier.
Licensing is per developer, not per deployment. End users and projects are unlimited under every tier, and the report designer is redistributable with no royalty, so handing report authoring to your own customers adds no per-deployment line item. That is a materially different commercial shape from tools metering by server, end user, or deployment target, and it is the ceiling of what the licence covers, because IronPDF licenses per developer on the same basis with no tier ladder to climb for a container.
Which Tier Does IronPDF Ask You to Reach?
The narrower job is a fixed layout or an HTML template that has to become a PDF, with no report project or bound data source in the path.
using IronPdf;
var statementRenderer = new ChromePdfRenderer();
statementRenderer.RenderingOptions.MarginTop = 20;
statementRenderer.RenderingOptions.MarginBottom = 20;
using PdfDocument statement = statementRenderer.RenderHtmlAsPdf(statementHtml);
// The assembly step a report definition would need a subreport for
using PdfDocument packet = PdfDocument.Merge(statement, appendix);
packet.SaveAs("statement-package.pdf");
IronPDF writes a single searchable PDF from two sources, and the same call runs on Windows, on Linux, and in a container from one package with no cross-platform tier to reach first. IronPDF hands the stylesheet to a full browser engine, so the responsive CSS a design team already wrote survives the trip, and where the markup starts life as an MVC template it takes the Razor view directly.
Upstream of that call belongs to List & Label and should stay there. A rendering library has none of it, not a business analyst designing their own layout, not a parameter-driven query against a live data source, not a crosstab or a subreport, and not scheduled distribution through a report server. The ceiling on this particular path is that the tier unlocking Linux also prices in a designer the workload may never open, and that the authoring half of cross-platform has not shipped yet. Coexistence is the usual outcome for teams with real use for both, and the renderer-side pattern is written up in full if that split is on the table. IronPDF has a free trial if you want to answer the container question against your own template before signing anything.
Has anyone here run List & Label Cross Platform in production yet, or is report authoring still routed through a Windows machine because the designer has not caught up? Let us know in the comments, because the gap between runtime support and tooling support is the part that decides how this feels day to day.
List & Label is a trademark of its owner and this piece is not affiliated with the company. The pricing, tier gating, cross-platform, and HTML rendering details above are drawn from combit's own pricing pages and documentation, and from NVD, the GitHub Advisory Database, and Snyk, as they stood at the time of writing. If a detail has changed since, correct us in the comments.
Top comments (0)