Connect one API
Send PDF or RAW jobs from the product and workflow your team already owns.
Printing infrastructure, ready for your product.
Add network printing without building the network. Piqae gives your application one straightforward API, a managed cloud, and a lightweight agent beside every printer.
One API · Managed cloud · Full native-driver capability
One place to run every print workflow
See printers, nodes, queues, and jobs across every customer and location. Piqae keeps each handoff clear, including the boundary between operating-system acceptance and the physical result.
How it works 01 02 03
Build once. Print wherever the work happens.
Open the quickstart →Add each print location
A small native agent securely connects the printers at every site to Piqae Cloud.
Use the full printer
Local operating-system drivers preserve media, tray, finishing, and vendor options.
Network preview Drag to explore
Durable by design Work waits safely. Cloud and local queues recover through interruptions.
Full print capability Your drivers stay in control. Paper, trays, finishing, and vendor settings stay local.
Piqae Cloud Hosted to scale.
Hosted to scale.
Local where it counts.
Run printing across customers and locations without operating the control plane yourself. Piqae keeps work durable from the cloud to the agent, then hands it to the real driver beside the printer.
Managed cloud control plane Durable cloud and local queues Native capability at every site
Read the job lifecycle guide →Built for developers
Add full-service printing. Keep building your product.
Piqae is the headless print layer behind your own experience. Keep your interface, customer relationships, and product logic while we handle the path to every printer.
- A straightforward API for jobs, printers, status, and customer workspaces
- PDF and RAW printing without sending credentials into the browser
- Idempotency, queueing, retries, and agent connectivity already handled
- Your brand and workflow stay in front; Piqae stays behind the scenes
orders.ts 200 OK
// Printing stays inside your workflow
const job = await piqae.printJobs.create({
printer: customer.defaultPrinter,
content: {
type: 'pdf',
url: order.packingSlip
},
idempotencyKey: order.id
}); Job accepted Customer workspace · Printer 04
Put printing inside the account your users already have.
Create an isolated Piqae customer account for each organisation from your backend, connect their printers, and keep the whole print experience inside your product.
- One server-side platform credential manages your customer accounts
- Each customer gets separate workspaces, environments, printers, jobs, and usage
- Your users connect a local agent without needing a separate Piqae login
Clear encryption boundaries, from cloud to printer.
TLS in transit
Remote API, upload, and agent traffic travels over authenticated TLS.
Encrypted at rest
Hosted document content uses object-level encryption and short retention controls.
AES-256-GCM payload encryption
Preview confidential printing encrypts each job for its permitted nodes before upload.
Confidential printing is a Preview feature, not yet an independently audited end-to-end encryption claim. The destination operating system and printer must receive plaintext to print.
See the security model →Less infrastructure to operate
Run the workflow, not the printing plumbing.
Piqae Cloud handles accounts, queues, agent connectivity, and status in one service. Your team gets the visibility to resolve problems without owning another distributed system.
See Piqae Cloud pricingPrint jobjob_01J9…K4P
OS acceptedPDF
Packing slip1 page · Printer 04
···- ✓Job receivedYour application · 09:41:03
- ✓Agent acceptedLocal print station · 09:41:04
- ✓Driver settings appliedA6 label · Tray 2 · 09:41:05
- OS spooler acceptedLocal handoff complete · 09:41:06
What this means: the operating system accepted the job. Physical output is not independently confirmed.
Why Piqae
A shorter path from an idea to printed output.
Developer-forward from day one
Clear resources, useful SDK patterns, webhooks, and a dashboard that speaks the same language as the API.
Dependable from cloud to edge
Durable queues and explicit recovery keep work moving through brief network and site interruptions.
Real drivers. Real print capability.
Use the installed operating-system driver for specialist media, trays, finishing, and production hardware.
Cloud economics that stay clear
Start free, move to straightforward usage allowances, and compare the cost against your current print volume.
Switch with confidence
A developer-first alternative to PrintNode.
Compare the API model, printer capability, and documented pricing against the way you print today. Then move one customer or location at a time with a clear rollback path.
Migration runCanary workspace
- 1 Inventory current endpoints
- 2 Map printers and credentials
- 3 Route a controlled job set
- 4 Observe status differences
- 5 Expand or roll back
Piqae Cloud pricing
Start small. Pay only for jobs reported complete.
Failed, blocked, cancelled, expired, and delivery-uncertain jobs do not count. Start free, grow with Pro, or tailor an Enterprise rollout.
Piqae Free
Start with the complete print path, no card required.
$0/mo.
100 reported-complete jobs per month · 1 node
Piqae Pro
ProductionPay only for jobs your printer path reports complete.
$9/mo.
25,000 reported-complete jobs per month · 25 nodes
Piqae Enterprise
TailoredScale fleets, customer deployments, and support around your product.
Custom
Volume and deployment pricing Higher fleet limits and rollout support · SSO · custom node and update policies
Displayed prices are USD excluding tax. Stripe confirms the final charge at checkout. Public sale remains gated by cost and release readiness.
Open source when you need it Explore open source →
Piqae Cloud is the easy path. The platform is still yours to inspect and run.
The complete printing stack is available under Apache-2.0 for teams with specific infrastructure, residency, or local-only requirements.