If you’ve used ERPNext in the past few years, chances are you’ve benefited from Resilient Tech’s work, even if you didn’t realise it. From tightening security and improving performance and making the system more stable, they have contributed deeply to the Frappe ecosystem. Many of these contributions were unpaid, driven purely by a commitment to the community. They also played a key role in bringing ERPNext closer to India’s compliance standards, helping businesses here stay aligned and confident.

Castlecraft has been the backbone for anyone running Frappe on their own servers. As the maintainer of frappe_docker, they made self-hosting possible and manageable for hundreds of users. From setting things up to solving tricky deployment issues, Castlecraft has been there with guidance, fixes, and support whenever the community needed it.

Alyf has been quietly making Frappe better for everyone, one fix at a time. From strengthening security to solving all sorts of unexpected issues across the system, their contributions have been steady and meaningful. They have also played a big role in moving localisation forward, especially for German users. Whether it is working on compliance or building the translation system we use today, Alyf has helped make Frappe more usable and accessible across regions.

Wahni has been contributing to the Frappe ecosystem and other open-source projects since its inception. They have been avid users and implementers of Frappe products for a long time, and that helps them gather a lot of insights from end users, which in turn has enabled them to improve the products with features and fixes. From accounting to stock to sales, they have left their fingerprint on almost all modules of ERPNext.