AmazeLPD is the drop-in Windows service that keeps LPD/LPR and IPP printing alive — receiving jobs from AS400, Linux, Unix, SAP, mainframe and CUPS, and forwarding them to any document platform.
No credit card. Full functionality · installs in minutes · nothing changes on the sending side.
Thousands of enterprises still route print jobs from AS400 output queues, Linux, Unix, SAP and mainframe systems to Windows over LPD/LPR. These pipelines are invisible until they fail — and the day Microsoft pulls LPD, invoices, statements and batch documents simply stop coming out the other end.
AmazeLPD replaces the Microsoft LPD service transparently. It listens on the same port 515, speaks RFC 1179 independently, and forwards every job onward — so the sending side never knows anything changed.
“Our business is high volume, and the built-in Windows LPD service just wasn't coping. Under load, jobs would go missing — no error, no log, no indication. We'd only find out when a customer rang asking where their statement was. You can't run a billing operation on a print path you can't see.”
With AmazeLPD, every job is written to a durable spool the instant it lands and recorded in an auditable ledger — received, processed, delivered — so nothing disappears silently. One worker per queue keeps dozens of queues running at full speed at once, and if a destination is down the job holds as Pending instead of vanishing. Same LPR and IPP endpoints; nothing changed on the sending side.
— Systems administrator, high-volume print operations (composite scenario)
No SQL Server, no additional runtime, no configuration beyond installation. Just a Windows service that does one job exceptionally well.
Installs and starts automatically, survives reboots, and resumes pending jobs after a restart.
Works with any LPR client — AS400, Linux, AIX, CUPS, SAP, mainframe and Windows lpr.exe.
Every queue is also a CUPS-compatible IPP printer at ipp://server:631/printers/<Queue>.
One worker per queue — 100 queues process simultaneously and no queue ever blocks another.
Each queue has its own destination, package/branch and parameters. Fan out to many targets at once.
A full, searchable trail of every job received, processed and delivered — with status and logs.
Pause a queue for maintenance without losing jobs; they hold as Pending and flush on resume.
Stand up hundreds of queues at once from a spreadsheet instead of clicking through a UI.
Embedded SQLite, ~50 MB on disk, no external database. The hot path never touches the DB.
Run the installer. The AmazeLPD service registers and starts automatically, listening on ports 515 and 631.
In AmazeLPD Manager, add a queue whose name matches your LPR -P target, and set its destination.
Point your AS400, Linux or CUPS client at the server. Jobs spool, forward, and appear as Completed.
If it can send LPR or IPP, AmazeLPD can receive it — with no changes on the sending side.
| Sending platform | Method | Notes |
|---|---|---|
| IBM i / AS400 | OS/400 Output Queue (OUTQ) via LPR | Configure remote system + remote printer queue |
| Linux / Unix | lpr / CUPS (LPR or IPP) | Standard LPR output, or add as an IPP printer |
| AIX | lpr / lpd | Native support |
| SAP | Spool output via LPR | Configure SAP output device |
| Oracle EBS | Concurrent Manager print | LPR output method |
| Mainframe z/OS | JES spool LPR output | Standard configuration |
| Windows | lpr.exe or LPR port | Built-in Windows lpr.exe |
| HP-UX / Solaris | lpr | Native support |
| macOS / modern Linux / CUPS | IPP ipp://server:631/printers/<Queue> | Add as a remote IPP printer — no LPR setup |
Not a heavyweight print-management suite, not a device-tiered LPD tool, not a retiring OS component — a focused, per-server gateway with unlimited queues.
| AmazeLPD | Competitor 1 | Competitor 2 | Competitor 3 | |
|---|---|---|---|---|
| Purpose-built LPD/LPR + IPP gateway | ✔ | ✔ | ✗ | ✗ |
| Per-queue destination routing | ✔ | ✔ | ✗ | ✗ |
| IPP for CUPS / macOS / Linux | ✔ | ✗ | ✔ | ✗ |
| XML / JSON envelope with custom parameters | ✔ | ✗ | ✗ | ✗ |
| Job history & audit log | ✔ | ✔ | ✔ | ✗ |
| Unlimited queues per server (not device-tiered) | ✔ | ✗ | — | ✔ |
| No SQL Server / heavyweight platform | ✔ | ✔ | ✗ | ✔ |
| Perpetual licence option | ✔ | ✔ | ✗ | — |
| Actively developed & supported | ✔ | ✔ | ✔ | ✗ |
| Comparison reflects common products in each category; capabilities vary by product and version. | ||||
The 7-day trial is the full product, no restrictions. Own AmazeLPD outright with a perpetual per-server licence — unlimited queues — add maintenance for updates & support, or pick a lower-upfront annual subscription.
System requirements: Windows Server 2016/2019/2022/2025 or Windows 10/11 · .NET Framework 4.8 · 50 MB disk · ports 515 & 631 (both configurable).
lpr command, or any other LPR client keeps working exactly as before — just point it at the AmazeLPD server IP.ipp://<server>:631/printers/<QueueName>. Add it with lpadmin or macOS System Settings and print normally — it lands in the same spool and queue as LPR jobs.Install AmazeLPD, recreate your queues, and let every LPR and IPP job keep flowing — auditable, concurrent, and independent of Microsoft's LPD.