One bridge. Every device on the floor.
Cloud Server is the routing layer between Odoo and the physical hardware in your customer's facility — printers, payment terminals, weight scales, barcode scanners. End-to-end encrypted, runs locally, no traffic ever leaves their network.
Watch the walkthrough — then we'll ship you a device.
Buy the module, sign the contract, and Bista will mail you the bridge device — free of charge. The walkthrough video covers pairing, device registration, and your first print job.
Four steps from Odoo click to printer ink.
No external cloud round-trips. Once paired, every job stays inside the customer's local network.
Job created in Odoo
Print a label, receipt, or invoice — Odoo creates a cloud.server.job record bound to a device.
Encrypted with Fernet
Payload is encrypted with the server's pairing code before it leaves Odoo. Authenticated, tamper-proof.
Routed by the bridge
Bridge device receives the job, decrypts it, and forwards it to the right device — by IP or via CUPS.
Device prints, status returns
Status flows back to Odoo: connected, queued, printed, errored. Visible in the Jobs view in real time.
If it has an IP or a CUPS queue, we route to it.
Three device categories, multiple printer dialects, two communication modes. Most factory floors are covered out of the box.
Label & receipt printers
Zebra, Honeywell, Star, EPSON, generic PCL, dot matrix. Any printer that takes raw bytes or PCL.
Payment terminals
Bridge POS payment to network-attached terminals. Order, sale, and refund flows from Odoo to the device.
Weight scales
Read live weight values from network-connected scales into Odoo at quote, pick, or ship time.
RFID readers
Impinj Speedway Revolution and compatible RAIN RFID readers. Tag reads stream directly into Odoo inventory and WMS workflows.
CUPS-based devices
If your customer's IT is on CUPS, we discover queues by name. No IP scanning, no firewall holes.
Custom & future devices
Bring your own device protocol. The bridge ships with hooks for adding new device types.
Works wherever your Odoo lives.
No public IP, no port forwarding, no inbound firewall changes. The bridge initiates an outbound connection — every Odoo hosting model is supported.
AWS
EC2, ECS, or any AWS-hosted Odoo. VPC private subnet is fine.
GCP
Compute Engine, GKE, Cloud Run — same setup, no extra config.
Odoo.sh
Production, staging, and dev branches all supported.
On-premises
Local servers, private data centers, factory networks.
No public IP required
The bridge calls out to Odoo, not the other way around. No inbound firewall rules, no port forwarding, no exposed services.
Encrypted end-to-end. Stays on the local network.
Cloud Server runs inside the customer's perimeter. Bista does not host their data, see their traffic, or hold a backdoor key.
- We don't route through any external server. Jobs stay on the customer's LAN.
- We don't store payloads. Jobs are forwarded and discarded.
- We don't hold pairing keys. Each customer generates their own; we never see them.
- We don't require outbound internet for standard print jobs — they stay on the LAN. Payment terminals need connectivity to return responses to Odoo.
- Symmetric encryption on every job — Fernet (AES-128-CBC + HMAC-SHA256).
- Pairing-code authentication — bridge rejects any payload that wasn't signed by the matching key.
- Role-based device access — bind devices to Odoo groups; only authorized users can submit jobs.
- Auditable — every job is recorded as an Odoo record with status, timing, and operator.
What other platforms make hard, we make a checkbox.
Most printing middleware was built for a specific device, a specific OS, or a specific cloud. Cloud Server was built for Odoo partners — first and foremost.
Everything partners ask before they install.
License the module. We'll mail the device. You're live.
Drop us a note — real humans answer, usually within hours. Or email [email protected] directly.