Set up local printing first
1. Download only a verified installer from the official Downloads page. Check its exact version and release notes. This pilot documentation covers 0.6.4-beta.3; this does not mean a validated installer for that version is already published.
2. Install on the Windows computer connected to your printer. Follow the installer instructions. Developer SDK requirements are not automatically requirements for an end-user installer.
3. Start FourPrint in local printing mode. Configure a station, select a connected printer, and set paper options and prices. Keep the station computer available on the local network.
4. Display the station QR, issue a one-time customer code, and have a phone on the same network open the printing page. Upload a document, review the allowed options, and approve the job through the staff workflow.
5. Verify an actual physical print before serving customers. A successful upload, simulated job or dry-run status is not proof that paper was printed. Keep customer access closed when the station is unattended.
Customer and staff workflow
- Staff configure the station, printer, allowed options and prices.
- The customer opens the station QR page, redeems the issued one-time code and submits a document.
- Staff review the job, control submission and handle payment/closure through the station workflow.
- Verify the physical output and document cleanup before closing the session.
The desktop, local services, customer website and printer worker must be available for their parts of the workflow. Customers need network access to the shop in local mode.
Internet printing through the beta.3 relay
After the shop is linked and its hostname is provisioned, customer HTTPS requests travel through the Render relay to an authenticated outbound connection from the shop computer. The gateway stages the document locally for staff approval and printing.
- The operator configures the approved shop hostname, DNS and trusted HTTPS for the relay pilot. Confirm the deployed service is ready before accepting customer uploads.
- Link the desktop using the supported account workflow. Keep FourPrint, its gateway and the printing services running.
- Select Open printing and choose a customer access window from 1 to 60 minutes.
- Use the existing Issue one-time code button. Linked desktops use the protected gateway while preserving the local session identity. Unlinked local printing retains its local workflow.
- Ask the customer to open the station QR page, redeem the code promptly and submit a document. Staff review and approve the job, then verify the physical print.
- Close customer printing when finished. A process restart begins with access closed; a connection interruption requires the desktop to reconnect while the access window remains open.
The shop gateway uses an outbound connection and keeps its private listeners on loopback. Follow the beta.3 deployment configuration rather than exposing private shop API ports.
Privacy and document handling
Render terminates HTTPS and relays encrypted upload envelopes in memory. The design does not persist PDF payloads in the central database or relay filesystem. The shop uses encrypted local staging and staff-controlled approval.
The browser assets and key delivery remain trusted to the central/gateway delivery path. This is not a claim of independently authenticated end-to-end web delivery. Shop operators must verify cleanup, access controls and the actual installed release before handling customer documents.
Pilot verification and limitations
A phone upload and physical print were confirmed for the beta.3 outbound-relay pilot. That result covers the tested setup; it does not certify every printer, shop or installation.
Check DNS/HTTPS availability, desktop linking, reconnection, closed-window access and document cleanup in your own deployment. Relay state and in-memory counters reset on restart; pilot limits are not a durable provider spending cap. Review capacity before expanding beyond the pilot.
Developer builds default to dry-run processing unless physical printing is configured. Simulated success does not confirm paper output. Signing, installer acceptance and printer compatibility still require release checks. Online payment processing is not enabled by this pilot.