Companies that use Netbox

Source: Analysis of job postings that mention Netbox (using the Bloomberry Jobs API)

My analysis shows that Netbox purchasing decisions are primarily made by infrastructure and network leadership roles, with about 5% of postings representing director-level positions overseeing customer success, operations, and infrastructure tooling. The dominant hiring pattern focuses on network engineers (29%), system administrators (10%), and DevOps/SRE roles (7%), suggesting that Netbox is championed by technical teams who need to solve immediate operational challenges around network inventory, documentation, and automation. Strategic priorities center on modernization, scalability, and moving toward infrastructure-as-code practices.

Day-to-day users are hands-on network and infrastructure engineers who rely on Netbox as a source of truth for network inventory, IP address management (IPAM), and asset tracking. I noticed extensive references to maintaining documentation, integrating Netbox with automation frameworks like Ansible and Python, and using it alongside monitoring tools like Grafana, Zabbix, and Prometheus. These practitioners are building automation pipelines, managing device configurations, and coordinating network deployments across global data centers and multi-cloud environments.

The pain points reveal a clear shift from manual processes to automated, data-driven operations. Companies repeatedly mention goals like "replace manual repetitive tasks with efficient automation solutions," "establish a single source of truth," and "improve data quality and operational efficiency." One posting emphasized the need to "minimize manual labor and achieve Service Level Objectives," while another highlighted "maintaining competitive product standards" through better inventory management. These organizations are scaling rapidly and need Netbox to bring order, visibility, and automation to increasingly complex network infrastructures.

Source: Analysis of Linkedin bios of 953 companies that use Netbox

I noticed that Netbox users are predominantly infrastructure-focused companies that build, operate, or manage physical and digital networks. These are telecommunications providers, internet service providers, data center operators, and IT service companies. They're not selling consumer products or abstract services. They're managing cables, servers, fiber optic networks, and complex technical infrastructures that require meticulous documentation. Many operate their own physical network infrastructure, whether that's "high-speed broadband connectivity" or "optical transport networks" or managing "30GW of solar power plants."

These are established, operationally mature companies rather than early-stage startups. The employee counts cluster in the 11-50 and 51-200 ranges, with many operating for decades (DNS:NET since 1998, Nepal Telecom over years, WiscNet since its founding). They have physical infrastructure investments, multiple office locations, and stable business models. Very few show venture funding, and when they do, it's modest. This suggests organic growth funded by operations rather than venture capital.

Source: Analysis of tech stacks from 953 companies that use Netbox

I noticed that Netbox users are infrastructure-focused companies managing complex, self-hosted technical environments. The extremely high correlation with tools like Zabbix, Rancher, and Portainer tells me these are organizations running their own data centers or extensive on-premise infrastructure. They're not typical SaaS companies using cloud-native solutions. Instead, they need serious infrastructure management capabilities, which is exactly what Netbox provides as an IP address management and data center infrastructure tool.

The pairing with Zabbix makes perfect sense because companies tracking network infrastructure in Netbox need robust monitoring to keep those systems running. GitLab's presence suggests these teams are managing infrastructure as code, likely using version control for their network configurations and automation scripts. The Grafana correlation reinforces this picture of organizations that need deep visibility into their infrastructure performance. Meanwhile, Rancher and Portainer appearing together points to companies orchestrating containers across their own infrastructure rather than relying solely on managed Kubernetes services.

My analysis shows these are operationally mature, engineering-led organizations. They're definitely not product-led growth companies with simple cloud deployments. These companies have substantial technical teams that prefer building and controlling their own infrastructure stack rather than buying fully managed solutions. They're likely at growth or mature stages since they've invested in sophisticated monitoring and container orchestration. The presence of Bitwarden Enterprise suggests security-conscious organizations with compliance requirements that justify running their own password management.