XiotBox Documentation
Odoo 19.0 & 18.0 supported
Capability matrix: two delivery plans
Compare the official-client plan with the XiotBox-client plan so you can pick the deployment that matches your security and roadmap needs.
Short version: both plans let you keep Odoo Direct Print PRO and choose between the official PrintNode API and the self-hosted XiotBox API. The XiotBox client plan adds end-to-end transport encryption on both APIs, per-user printer visibility and the AI extension roadmap.
Terminology
| Official API | The PrintNode cloud API (api.printnode.com / client.printnode.com). |
|---|---|
| Self-hosted private API | The xiotbox_lite + Runtime service you operate yourself (client server_mode="odoo"). |
| printnode_base | The third-party Odoo Direct Print PRO module by VentorTech, licensed separately. It is never included with XiotBox. |
| og_printnode_me | The first-party extension module that adds per-user account ownership, safe printer visibility and editable account endpoints. |
| XiotBox client | The first-party desktop client (xiotbox_flutter) with odoo and xiotbox server modes. |
| Official client + patch | The official PrintNode client pointed at your Runtime through a reversible XiotBox patch (API base override only). |
| E2E transport encryption | End-to-end encryption between the client and the delivery layer: X25519 ECDH, AES-256-GCM content encryption and Ed25519 identity signatures with per-device key bundles. |
Plan A · Official PrintNode client + XiotBox patch
- Components:
printnode_base+xiotbox_lite+ Runtime + the official PrintNode client (patched). - Value-add: the official client can select the self-hosted private API and switch back to the official API at any time.
- Boundary: the patch only redirects endpoints. The official client does not implement the XiotBox E2E key model, so E2E transport encryption is not available in this plan.
Plan B · XiotBox client + og_printnode_me
- Components:
printnode_base+og_printnode_me+xiotbox_lite+ Runtime + the XiotBox client. - Value-add: E2E transport encryption on the official API and on the self-hosted API, per-user printer visibility, and the AI extension roadmap (OpenClaw channel).
- Note: in official-API mode the client registers its E2E public key with your business Odoo server; print content is carried to PrintNode as an opaque payload.
Capability matrix
| Capability | Plan A · official client + patch | Plan B · XiotBox client + extension |
|---|---|---|
| Official PrintNode API | Yes | Yes |
| Self-hosted private API | Yes (selectable) | Yes (selectable) |
| E2E encryption on official API | No | Yes |
| E2E encryption on self-hosted API | No | Yes |
| Transport security baseline | TLS / HTTPS / WSS | TLS / HTTPS / WSS + optional E2E |
| Per-user account and printer visibility | Base (printnode_base) | Enhanced (og_printnode_me) |
| Editable account endpoint | Via patch manager | On the account record |
| AI extension (roadmap) | No | OpenClaw channel |
| Client release control | Vendor client updates can reset the endpoint | First-party client, own release cadence |
| Module price | EUR 0 | EUR 0 |
| Runtime subscription | Separate paid subscription (price agreed per deployment) | |
Pricing
xiotbox_lite,og_printnode_meandxiotbox_runtime_manager: free (EUR 0), with phased small price increases planned over time.- XiotBox client and desktop patches: free.
- Runtime production subscription: separate, per claimed Runtime installation; price agreed in the commercial discussion.
printnode_base: third-party VentorTech module, licensed separately at your own cost.
Pick by need: choose Plan A for the smallest change when you already run the official client and only want the self-hosted API option. Choose Plan B when you need end-to-end transport encryption, per-user printer control, or the AI roadmap.