Much of what we build sits on open-source technology, not a closed stack only we control. Here's why, and what that means in practice.
The impact sector runs on tight budgets and long time horizons. Locking a nonprofit or a government programme into a closed, single-vendor stack makes both worse: harder to afford, harder to leave, harder to inspect.
Open, inspectable technology means our clients aren't betting their programme on one company staying in business, staying interested, or staying reasonably priced. It also means the code we write can outlive any single contract.
Much of what we build sits on Frappe, the open-source low-code framework behind ERPNext. It gives us a fast, well-tested foundation for the systems and workflows our clients need, instead of reinventing forms, permissions, and reporting from scratch on every project.
A meaningful part of our engineering team works in Frappe day to day, alongside PHP, full-stack JavaScript and mobile development, so it's a real, load-bearing part of how we build, not a marketing line.
We think the impact sector is better served by open, inspectable technology than by vendor lock-in. Where we can, we contribute back to the ecosystems we rely on.
That means code and fixes upstream where it makes sense, documentation for the tools we use, and mentoring the developers who extend them. It's an ongoing commitment, not a one-time claim, and we'll keep this page honest as it grows.
The clearest example: the Frappe Mobile Framework, now open source. It did not start as a framework. It started as us solving real, on-ground problems for the social sector: actual challenges, real users, and over time it became the thing we used to build Frappe-based mobile apps faster and more simply. It was launched into the open at Frappe Build 2026, and it is no longer limited to one team.
If you are building on Frappe, try it. If you can improve it, contribute. The best tools should not stay closed.