Local stays real
Printing, native profiles, and the local queue do not become artificial Cloud-only features.
Apache-2.0
Open at the edge. Portable at the core.
The node, control plane, SDK, dashboard, and deployment definitions are open source. Run the complete platform yourself, or keep an auditable, customisable edge while Piqae Cloud operates the durable queue.
The edge is yours
Audit or adapt the code that stores jobs, reconnects, and calls native print APIs.
Drivers keep authority
Vendor options come from the operating system, including specialist label and PostScript drivers.
Repository architecture
One shared Rust core. Thin native shells.
The durable agent owns identity, queueing, recovery, and cloud synchronisation. Native menu and tray applications remain disposable interfaces over a narrow local contract.
piqae/
├── control-plane
├── agent-core
├── piqae-agent
├── protocol
├── storage-postgres
├── web
├── sdk
└── native shellsChoose who operates it
Open source without giving up a managed path.
Both routes use the same product model. The difference is who owns the stateful infrastructure and the work required to keep it available.
Keep the open edge. Hand us the queue.
Piqae operates the control plane, object storage, backups, monitoring, upgrades, and recovery path. This is the simplest route when print jobs must wait safely for offline nodes without your team running printing infrastructure.
Run the complete platform yourself.
Compose and Kubernetes deployments keep core printing features available, but your team owns database durability, storage, scaling, monitoring, backups, and high availability.
Apache License 2.0
Built to be used, changed, and redistributed.
Use Piqae commercially, inspect every handoff, maintain a compatible fork, or operate it in your own environment.
- UsePersonal or commercial
- ModifyAdapt the node or platform
- DistributeSubject to licence notices
- Self-hostNo licence server or phone-home