@broadpaper/server

The BroadPaper render service: either PDF backend behind HTTP, with a queue, a bearer token and a Dockerfile.

Part of BroadPaper — an embeddable visual report designer and PDF renderer. Your users design the report in your application; BroadPaper owns the layout, the branding, the pagination and the output.

Install

npm install @broadpaper/server

POST /render, POST /render/batch and GET /health, so an application in any language can produce a PDF without hosting a JavaScript runtime itself. There is a .NET client on NuGet (BroadPaper.Client); everything else can speak the HTTP directly.

The queue is bounded, and the service refuses work rather than accepting more than it can finish — a render that is going to fail should fail at the door, not after thirty seconds of somebody's month-end.

It listens with plain HTTP and authenticates with a shared bearer token. Terminating TLS is your ingress's job. In clear text that token is the credential, so put TLS in front of it wherever a request crosses a network you do not control.

Licensing

BroadPaper is free to evaluate, with no trial clock and nothing behind a feature gate. Install it, use every feature and evaluate it against your real data for as long as you like. Production use needs a licence.

In the software, the only difference without a licence is that generated PDFs carry an evaluation mark, and a licence removes it. Contractually, the licence is also what permits production use. No seats, no activation, no machine binding, no telemetry, and no call home at any point.

• How licensing works
• Pricing
• Licence agreement

Documentation

• The render service
• Security
• Full documentation

Support

Paid licences include email support at [email protected].

Copyright © 2026 Codingbadger Creative Limited. See LICENSE in this package, and THIRD-PARTY-NOTICES.md for the components it ships with.