10 Years of Addigy in MacAdmins art

Ten Years of the Addigy Community: From Solo Admins to a Global Braintrust

Table of Contents:

  • Introduction
  • The Early Days of Addigy
  • Growth Through Collaboration
  • Highlights from the Addigy Journey
  • Looking Ahead

Managing Apple devices was once a solitary pursuit. A decade ago, being a Mac Admin often meant working in isolation—you were likely the only person in the organization trying to decipher why an update bricked several executive laptops at once. There was no established playbook for MDM challenges, only scattered forums and trial-and-error.

Jason Dettbarn, Addigy’s Founder and CTO, recognized this gap early on. His philosophy was simple: Mac admins shouldn’t have to manage alone.

This belief sparked the Addigy community. It wasn’t designed as a marketing channel, but as a lifeline. Over the last decade, it has evolved from a small group of early adopters into a global braintrust where technical expertise meets genuine camaraderie.

A Decade by the Numbers

Today, the Addigy community boasts 2,505 members worldwide. But the impact goes beyond headcount. Tens of thousands of messages represent real questions answered and crises averted. Every statistic reflects a fire extinguished faster or a deployment that succeeded because an admin wasn’t alone. This collective intelligence turns daily IT struggles into shared solutions.

What We’re Proud Of

Beyond the troubleshooting, we are proud of the tangible value this ecosystem provides:

  • Expertise Without Gatekeeping: Senior admins freely share production-grade details on complex topics like MDM, RMM, PPPC, DEP, and TCC.
  • A 24/7 Safety Net: For solo admins, this channel is a force multiplier. Members often find solutions here faster than through formal support channels.
  • Community-Driven Product: User ideas discussed in the community often become real Addigy features. Our product roadmap is directly influenced by the people using it every day.
  • Shared Automation: By sharing scripts and custom facts, members save thousands of hours and allow smaller organizations to implement complex automation easily.

Honoring Our Apple MDM Community

To celebrate 10 years of innovation and collaboration, we are proud to introduce special awards recognizing the contributions that make this community exceptional:

  • Community Champion: Awarded to those who show up daily with answers, patience, and working code. 
  • Most Helpful Contributor: For embodying generosity, patience, and transparency.
  • Best Humor Under Pressure: For maintaining perspective with perfectly timed wit during technical crises.

These individuals exemplify the heart of our community, ensuring it remains a premier source of inspiration and support.

Join us for a live announcement of the winners on Feb 11, 2026 – 12:00pm ET. Register to attend

Addigy 2036: What’s next in Apple MDM

Tools and macOS versions will evolve, but the value of a dedicated, intelligent community is timeless. As we look ahead, the invitation remains open: if you haven’t joined us yet, there’s a seat at the table. If you’re already here, we encourage you to share your scripts, answer a newcomer’s question, or celebrate a win.

Ten years strong, we remain a community that truly cares.

Ready to stop managing alone?

Join a network of peers who understand exactly what you do. 

To join the channel, follow these steps:

Addigy Community FAQ

What is the Addigy Community?

The Addigy Community is a place where Mac admins and IT teams share troubleshooting tips, scripts, and best practices for managing Apple devices with Addigy.

It’s designed for peer-to-peer collaboration and practical “how do I…?” questions.

​Is the Addigy Community official support?

The community is primarily for community support and discussion, not guaranteed real-time IT support.

For official support, use Addigy Technical Support and the Help Center resources.

Where can I get official Addigy help?

Use these official Addigy resources:

​What topics are best for community questions?

The community is best for:

  • “Is anyone else seeing this?” sanity checks.
  • Workflow advice (policies, profiles, app deployment strategy).
  • Scripting ideas (custom facts, remediation approaches).

These are common patterns in community support channels.

What topics should go to Addigy Support instead?

Send a support ticket when:

  • You suspect a service incident (also check status first).
  • The issue involves account access, billing, or tenant-level problems.
  • You need an official answer tied to SLAs or an internal investigation.
Can I request features or report bugs?

Yes—feature requests and bug reports are typically handled through Addigy’s support channels and product feedback processes (often linked through the platform).

If it impacts many people, post in the community too so others can confirm impact and workarounds.

 

Similar Posts