Tenant isolation
Workspace and environment identifiers scope every control-plane operation and storage query.
Security and trust
Built for the documents your business depends on.
Piqae protects credentials, gives every enrolled agent its own identity, separates customer workspaces, and keeps sensitive print data out of marketing analytics.
Device identity
Enrolled agents authenticate requests with signed, replay-resistant device credentials.
Bounded content
Downloads, URIs, files, render work, and waits are constrained rather than trusted indefinitely.
Secret hygiene
API keys, enrollment tokens, device keys, lease capabilities, and documents are excluded from client telemetry.
Auditable events
State changes are append-oriented and the reported-complete usage event is idempotent.
Honest status
Native spooler acceptance and reported completion are not presented as verified physical delivery.
Encryption boundaries
Protection matched to each part of the print path.
Piqae layers transport, storage, and optional payload encryption without hiding where plaintext must exist for the operating system, driver, and printer to do their work.
Authenticated TLS
Remote API, upload, and agent connections use TLS with hostname and trust-root validation.
Object-level encryption
Hosted document content uses a random data-encryption key, with short retention and deletion controls.
AES-256-GCM per job
The SDK can encrypt PDF or RAW content before upload and wrap its one-time key separately for each permitted node.
Precisely scoped: confidential printing is a Preview path and is not yet an independently audited zero-knowledge or end-to-end encrypted service. Routing metadata remains visible, and the destination system must decrypt content to print it.
Data path
| Data | Where it belongs | Control |
|---|---|---|
| Print content | Bounded object storage and the enrolled agent | Retention and deletion policy |
| Device credentials | Protected local secret storage | Revocable enrolment identity |
| Job metadata | Workspace-scoped database rows | Role and environment boundaries |
| Marketing analytics | Consent-gated PostHog events | No document, printer, key, or address fields |
Deployment responsibility
Piqae Cloud operates the managed control plane. Self-hosted operators are responsible for their database, object storage, network, identity configuration, retention, upgrades, and backups. The native agent remains inside the printer network in either model.
Current release envelope
Source-complete does not mean every platform is generally available. The checked-in support matrix and release gates are authoritative; the downloads page renders those limits instead of making broader claims.