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
Performance bottlenecks aren't uncommon when it comes to rolling out new technology, regardless of how capable or game-changing that technology might be. Every generation of new tech has encountered roadblocks that had to be overcome before it was truly able to shine. Virtualization forced organizations to rethink resource allocation, cloud transformation had us shift our focus toward scalability and elasticity, and microservices introduced entirely new challenges around observability and distributed systems. There's something different about AI, however ...
Consider a single order represented across order-management, execution, and settlement systems. Each database, message broker, and application may be online and processing its own records correctly. Yet the workflow has failed if related events arrive on different clocks, rely on inconsistent state, or cannot be reconciled before an operational decision must be made ...
AI now exists in almost every IT workflow. In a recent survey of more than 800 IT service professionals, all respondents indicated the use of AI in some form within their organization. But there's a growing paradox: if dashboards are clearing faster and alerts are resolved at unprecedented speed, why aren't IT service desks reporting lighter workloads? The research found that 71% of IT teams said their actual workload has remained flat or increased since adopting AI. This reality appears to contradict what we’ve been told about AI ...
Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...
Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...
When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...
If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...
Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...
AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...
Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...