For over a decade, I've been on a mission to make Salesforce development more accessible, secure, and collaborative. From the early days of building CumulusCI and Cumulus Suite at Salesforce.org to founding Muselab, my journey has always been about leveraging GitHub to empower the Salesforce ecosystem.
Today, I'm excited to share a pivotal realization—one that brings us back to our open source roots and sets the stage for a transformative shift in how nonprofits and organizations approach Salesforce DevOps.
Back in 2013, when I started working on CumulusCI, the goal was simple yet ambitious: enable the Salesforce nonprofit ecosystem to collaborate effectively through GitHub. We believed in the power of open source to drive innovation and democratize access to tools and knowledge.
Fast forward to today, and GitHub has made significant strides in supporting nonprofits. With GitHub for Nonprofits, GitHub Teams is now free for qualifying organizations. This means that nonprofits running on Salesforce no longer have to bear additional costs to manage their DevOps processes effectively.
The realization that a thin layer of open source tooling could adapt GitHub to meet the unique needs of Salesforce development was groundbreaking. We don't need to build or invest in expensive, proprietary platforms when GitHub already offers robust features. By adding just a bit of open source magic, we can achieve more than what many costly DevOps apps offer—without the hefty price tag.
The Salesforce DevOps landscape is crowded with vendors offering proprietary solutions that often require additional licenses and expenses. Many of these tools not only necessitate purchasing their software but also require GitHub Enterprise licenses at $21 per user per month. On top of that, the services themselves can range from $30 to over $500 per user per month!
This model is unsustainable and places a significant financial burden on organizations, especially nonprofits.
What worse, most of what you're paying for is just reimplementing features GitHub already has, more secure, more scalable, more flexible, and already integrated with enterprise ITSM tooling out of the box. What are were paying so much for anyhow? At this point, the open source tooling in the ecosystem can do everything any devops vendor can.
What's missing is the infrastructure to run it securely and at scale and the user experiences to bring all stakeholders to the collaborate around a single source of truth, finally!
With D2X 2.0 and our renewed open source focus, we're offering an alternative:
With D2X 2.0, we're doubling down on our commitment to open source and the community. This isn't just a pivot; it's a return to the principles that sparked our journey over a decade ago.
Nonprofits have always been at the heart of what we do. By leveraging GitHub's free offerings for nonprofits and our open source tools, we're making it possible for these organizations to:
This approach levels the playing field, allowing nonprofits to access enterprise-grade DevOps practices without the associated costs.
It's incredible what a small layer of open source tooling can accomplish. By building on top of GitHub's existing platform, we can:
We're proving that you don't need a bulky platform outside of GitHub to achieve what many DevOps apps charge significantly more to do—and often deliver less.
Recognizing the potential of this approach, we're also redefining how Muselab engages with the community and our clients.
We're introducing a new matrix of services with various levels of engagement and timeframes. This structure makes our expertise in setting up D2X and optimizing GitHub for Salesforce DevOps more accessible to organizations of all sizes.
Whether you need a quick setup or ongoing support, our flexible engagement model ensures that you get the right level of assistance when you need it.
While we're moving away from building what GitHub already provides, we'll continue to develop platform tools that complement and enhance the GitHub experience. Our focus will always be on adding value without duplicating existing functionalities.
We're drawing a bright line: We won't build what GitHub already does. Instead, we're inspired to view GitHub as a comprehensive platform—not just a git host—and explore ways to extend its capabilities in meaningful ways.
This journey isn't just about technology; it's about community, collaboration, and returning to the ethos that sparked our initial efforts.
I recall the early days of CumulusCI, when the nonprofit community came together to solve common challenges. The energy was palpable, and the innovations were groundbreaking. By returning to these open source roots, we're reigniting that spirit of collective progress.
We're not just building tools; we're fostering a movement that empowers everyone to contribute, share, and grow together.
I invite you to be part of this exciting evolution.
Returning to our open source roots has been a deeply fulfilling realization. It's a reminder of why we started this journey—to democratize access, foster collaboration, and build a better ecosystem for everyone.
By leveraging GitHub's platform and adding a thin layer of open source tooling, we're making powerful DevOps capabilities accessible to all, especially the nonprofits that inspire us.
Thank you for being part of this story. Together, we're not just adapting to change; we're driving it.