Automox announced Automox Canopy, a new capability that connects Automox to the mobile device management (MDM) tools organizations already run.
Canopy automates patching across the endpoints those tools leave exposed, from Apple Silicon Macs to Linux, servers, and the 600+ third-party applications attackers target most.
Most MDMs manage one slice of a fleet well and leave the rest uncovered. Apple Silicon Macs only accept silent operating system updates through the MDM protocol's Bootstrap Token, so those updates have stayed a manual, hands-on task, without the scheduling and enforcement discipline compliance and risk reduction demand. No MDM reaches Linux or servers, and most struggle with the third-party titles running on endpoints every day.
As organizations complete the transition to Apple Silicon and attackers move faster on unpatched software, that unmanaged slice of the fleet becomes a widening exposure. Automox's 2026 State of Endpoint Management report found that half of organizations take five or more days to patch critical vulnerabilities.
"Every IT team runs an MDM that does part of the job, and then patches the rest of the fleet by hand," said Justin Talerico, CEO of Automox. "Canopy closes that gap by working through the MDM teams already trust, so the Apple Silicon Macs, Linux machines, and servers that used to slip through now stay patched on the same automated schedule as everything else."
Canopy does that without asking teams to replace anything. Automox manages endpoints through an installed agent, and Apple gates silent Apple Silicon updates behind the Bootstrap Token, which no agent can reach on its own. Canopy calls the MDM's API and uses the Bootstrap Token the MDM already holds, so the agent and the MDM do the job together.
Apple Silicon patching that teams used to handle by hand now runs on a schedule. And Automox's cross-platform coverage extends across the rest of the fleet, with every update malware-scanned. Automox is not, and never was, an MDM. Canopy is the layer that connects Automox to the MDM a customer already runs, Jamf Pro or Intune.
Automox customers automate up to 96% more patches and realize a 362% return on investment over three years with a four-month payback period (IDC, 2025). Canopy extends that automation to the Apple Silicon Macs the Bootstrap Token used to wall off, alongside the Linux machines, servers, and third-party applications no MDM was built to reach.
The Latest
Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...
Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...
Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...
While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...
For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...
As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...
The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...
The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...
Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...
Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...