For software vendors
The parts of your product nobody wants to build twice
Document design, label rendering and on-site printing are hard to get right and never your differentiator. Embed them, and spend your roadmap on what makes your software yours.
Build or embed
What building it yourself really means
Build in-house
- Write a layout engine that paginates tables and repeats headers
- Reverse-engineer how printers interpret ZPL, barcode by barcode
- Ship and support an agent for every customer site and OS
- Maintain all of it, forever, next to your real product
Embed ours
- A designer and PDF engine with 20 warehouse templates to start from
- A label designer and renderer that follows Zebra's rules dot for dot, 16+ barcode families
- A print service with discovery, dedupe and dead-letter handling
- Evaluate free, and build the integration before you buy
Integration model
Components in your UI, services next to yours
Your UI, your data
The designers are web components inside your pages. Templates live in your database, with your tenants and versions; we store nothing.
Plain HTTP APIs
Render and merge endpoints with OpenAPI 3.1 specs and samples for Node, Python, Java and C#. Stateless, so they scale out.
Any front-end stack
Both designers have guides for plain HTML, Angular, React and Vue; Label Designer also for Next.js, Report Designer for Svelte.
Deployment
Runs wherever your product runs
Next to your services
Run the render services in your own cloud, inside your private network, one per region or tenant group.
At your customers' sites
Ship the Report Designer and Label Designer executables with your on-prem edition. No internet access needed: license keys are checked locally.
Cloud in, warehouse out
Your SaaS queues print jobs; Print Daemon prints them at the site over outbound connections only.
White label
It looks like your product, not ours
Styled with your design tokens
Every component takes CSS custom properties for accent, background, text, borders, radius and font, a light, dark
or automatic theme, and documented ::part() hooks. The token names are the same across products, with a per-product
prefix, so one palette themes them all.
Fits a strict security policy
The label components run without unsafe-inline or unsafe-eval. The report designer
runs without unsafe-eval and needs style-src 'unsafe-inline'.
Security
Built to run inside your customers' networks
Offline licenses
Signed keys checked locally. No license server, no telemetry, nothing phones home.
Untrusted input handled
Templates and ZPL are treated as untrusted: sizes clamped, expressions sandboxed, renders capped in memory and time.
Protected releases
Report Designer and Label Designer ship as compiled, obfuscated builds with SHA-256 checksums. The services have no authentication by design: keep them on your private network.
Start with an evaluation
Report Designer and Label Designer evaluation builds include a license, so your team can build the integration before you buy.