Frequently asked Questions

Can Qbee be deployed on our own server?

Yes, Qbee is available as a self-hosted/on-premise installation under our enterprice subscription.

What hardware does Qbee support?

Qbee runs on virtually any Linux-based device.This includes industrial gateways, embedded systems, SBCs like Raspberry Pi, x86 servers, ARM devices, and most custom hardware. As long as the device runs a supported Linux distribution and has network access, qbee works out of the box.

Does Qbee support A/B updates or rollback?

Qbee can deploy A/B image updates on systems that support dual-partition setups. Rollback is automatic if the device fails to boot correctly after an update. For systems without A/B, qbee offers package-level updates, container rollbacks, and script-based rollback logic.

How well does qbee scale with tens of thousands of devices?

Qbee is designed for large-scale fleets. The platform uses efficient delta communication, lightweight agents, and a distributed backend architecture. Customers operate deployments ranging from a few hundred to many tens of thousands of devices with high reliability and low overhead.

What types of artifacts can I update?

You can update Full firmware images, A/B system partitions, Debian or RPM packages, Files and configuration templates, Docker containers, Custom scripts or binaries.
‍
Qbee supports multiple update strategies, from full OS images to small incremental changes.

Can qbee integrate with CI/CD pipelines?

Yes, Qbee provides a REST API and supports automated artifact uploads and deployments. You can integrate with GitHub Actions, GitLab CI, Jenkins, Azure DevOps, or any system that can call an API.

Contact Qbee

Contact

Frequently asked Questions