We’ve released several new capabilities over the past few months, making it easier to automate fleet operations, manage infrastructure as code, streamline device onboarding, control software updates, and integrate Qbee into existing systems.

Integrations (Preview): Connect Qbee Events to Your Existing Systems

Fleet management rarely happens in isolation. With the new Integrations feature, currently available in preview, you can subscribe to device and account events in Qbee and send them to external systems through outbound webhooks.

The new Integrations page allows you to create, edit, test, enable, and delete subscriptions, as well as inspect previously delivered events and re-trigger events from the past six hours.

Supported events include:

• Devices being added or deleted
• Devices moving between groups
• Changes to device tags
• Updates to device attributes
• Devices going online or offline, including heartbeat monitoring
• Device log entries, filterable by severity and label

Webhook deliveries can also be secured using a signing secret, allowing receiving systems to verify that events originate from Qbee.

This opens up a wide range of automation possibilities, from triggering internal workflows and alerting systems to synchronizing Qbee with asset management, monitoring, support, and operational platforms.

Integrations is currently available in preview. If you're interested in participating, please contact support@qbee.io to enable the feature.

‍

‍

Infrastructure as Code for IoT with the New Terraform Provider

Modern cloud infrastructure is built and managed through code. Now your IoT fleet can be too.

We’re excited to introduce the Qbee Terraform Provider, allowing infrastructure and platform teams to provision and manage Qbee resources using Terraform alongside the rest of their cloud infrastructure.

Whether you're deploying new customer environments, managing staging and production fleets, or automating onboarding workflows, Terraform enables repeatable, version-controlled infrastructure that integrates into existing DevOps practices.

With the Qbee Terraform Provider, you can:

• Provision Qbee resources using declarative configuration
• Store infrastructure definitions in Git
• Review changes through pull requests
• Automate deployments through CI/CD pipelines
• Standardize fleet configuration across environments

This release is another important milestone toward our IoT as Code vision: treating fleet management with the same automation, repeatability, and governance used for modern cloud infrastructure.

Get started with the provider on the Terraform Registry.

‍

Automate Device Organization with Bootstrap Auto-Tagging

As fleets grow, organizing devices from the moment they come online becomes increasingly important.

Bootstrap keys now support automatic device tagging. When creating a bootstrap key, you can define one or more tags that are automatically applied whenever a device joins the fleet using that key.

This makes it easy to:

• Automatically organize devices by customer, site, region, hardware model, or deployment
• Simplify device searches and filtering
• Apply group-based automation immediately after onboarding
• Reduce manual post-provisioning tasks

Instead of manually tagging hundreds or thousands of devices after deployment, devices can be correctly classified from their very first connection.

Add Business Context with Custom Device Attributes

Every deployment contains information specific to the business behind it. With Custom Device Attributes, you can now store up to 10 custom key/value pairs directly on each device.

Attributes can be managed through:

• The Qbee API
• The qbee-agent

Examples include:

• Customer ID
• Asset ID
• Production line
• Installation date
• Internal inventory identifiers

Devices can also be searched through the API using attribute keys or key/value combinations.

This provides richer inventory management and makes it easier to connect Qbee with existing operational, asset management, and business systems.

More Flexible RAUC Update Reboot Control

We’ve added configurable reboot conditions for RAUC updates, giving administrators greater control over when devices restart after a bundle installation.

Previously, devices rebooted automatically after installation. Now you can optionally define a shell expression that determines whether a reboot should occur.

If the expression exits successfully with exit code 0, the device reboots. If no expression is configured, Qbee retains the previous automatic reboot behavior, ensuring full backward compatibility.

This additional flexibility is especially useful for:

• Production environments
• Scheduled maintenance windows
• Operational safety requirements
• Devices running critical workloads

Enterprise Security with Bring Your Own Certificate Authority

Enterprise organizations often require devices to authenticate using their existing internal Public Key Infrastructure (PKI).

Our new Bring Your Own Certificate Authority (BYOCA) capability allows enterprise customers to authenticate devices using their own Certificate Authority rather than relying solely on the default trust model.

Benefits include:

• Alignment with existing enterprise PKI policies
• Greater control over certificate lifecycle management
• Simplified compliance with internal security requirements
• Stronger integration with enterprise security infrastructure

Building Toward More Automated Linux Fleet Operations

Taken together, these releases continue to move Qbee toward a more automated and composable approach to Linux device management.

Terraform makes fleet configuration part of your infrastructure workflow. Bootstrap tagging and custom attributes make device onboarding and organization easier to automate. Integrations allow Qbee events to trigger workflows in external systems. RAUC controls provide more flexibility for production deployments, while BYOCA strengthens integration with enterprise security infrastructure.

The goal is simple. Make managing large Linux fleets feel less like maintaining a collection of individual devices and more like operating modern cloud infrastructure.

‍