
A little over a month into the NetBox Copilot public preview, adoption of Copilot by the NetBox community has accelerated fast. Copilot is now being used across 150+ organizations worldwide – from universities and MSPs to global enterprises and telecom operators – showing that conversational infrastructure management is quickly becoming the new normal.
The new Copilot “preference” introduced in NetBox 4.4.5+ has made it push-button easy to enable Copilot in any environment, and we’ve been shipping improvements every week as we learn from how teams are using it in the real world.
Here’s a look at what we’re learning about how teams are using Copilot in its first few weeks.
From November through early December, Copilot usage spanned:
We’re thrilled to see the multilingual engagement with NetBox Copilot, which is a nice surprise we weren’t expecting but demonstrates the power and flexibility of natural language agents like Copilot for working with infrastructure data. And we’re equally excited to see NetBox Copilot being used across all shapes and sizes of infrastructure and teams.
Across all organizations, a number of common use cases have emerged, and teams are finding operational value quickly. Here are a few of the most widely observed use cases from teams using Copilot today:
The most common workflow: “What do I have, and where is it?” Teams ask Copilot to count devices, audit statuses, analyze roles, identify missing serials, and distribute assets across sites or regions.
Users rely on Copilot to validate completeness and ensure data accuracy – surfacing missing contacts, incomplete rack documentation, unassigned VLANs, or outdated lifecycle data. We talked with one organization that used Copilot to audit thousands of devices to help find and fix duplicate device metadata and improve documentation accuracy.
IPAM is a standout pattern, with users:
Teams use Copilot to trace physical connections – mapping fiber routes, validating patching, and exploring end-to-end paths between devices.
Power users are using Copilot to help them build with Ansible, NetBox custom scripts, and automated discovery solutions. Many are using Copilot to validate filters, debug API calls, or build workflows. Copilot’s knowledge of NetBox’s ecosystem and its ability to combine knowledge and docs with direct access to your data helps streamline NetBox development.
There are many other use cases we’ve heard about, including virtual infrastructure (VM/cluster analysis), topology planning, power tracking, and data quality analysis. These patterns reflect how Copilot lowers the barrier to interacting with NetBox’s deep data model – especially for less-frequent users.
With NetBox 4.4.5 and later, enabling Copilot is as simple as turning on a built-in preference in NetBox – no plugin installation needed. If you’re on an older version, it’s a simple embed – almost as easy.
See our Quickstart Guide.
As Copilot heads toward general availability in the coming weeks, we’re expanding its capabilities with a number of features for NetBox Cloud and NetBox Enterprise customers:
Based on the usage patterns we’ve seen and talked with users about across hundreds organizations using NetBox Copilot so far, it’s clear Copilot is evolving into the primary interface many teams use to interact with NetBox data and we’re going to continue improving Copilot rapidly to meet this demand.
Looking to accelerate past clickops to automate analysis of your infrastructure and quickly answer key questions, or get NetBox guidance from Copilot’s built-in expertise? NetBox Copilot is available to everyone in the NetBox community for free, with generous free usage included.
Want a walkthrough or deeper dive? https://netboxlabs.com/contact-us/