LIVE DEMO · NO SIGNUP
Print a receipt. Right now.
Compose a receipt below and hit print. It goes through the real PrintForge pipeline — one POST /v1/jobs-style call, the same queue, the same state machine — and lands on a virtual printer instead of paper.
1 · Compose your receipt
2 · Watch it print
QUEUED
DISPATCHED
PRINTED
The printer is idle. Hit Print this receipt and the paper feeds out here.
THAT WAS THE REAL PIPELINE
One API call, a queue, a bridge ack.
Your receipt went through the real PrintForge queue — the API created a job, the dispatcher claimed it, and an acknowledgement flipped it to printed. In production the only difference is a $0 bridge agent next to your printer, and paper.
THE SAME PRINT, FROM YOUR CODE
- This was not a mock. The job you just watched lived in the production state machine:
queued → dispatched → printed. - Your printer, anywhere. A tiny agent long-polls outward over HTTPS — no inbound ports, works behind any firewall.
- Idempotent & retried.
dedupeKeystops double prints; failures auto-retry up to 3 times.