Announcing our acquisition by Frappe

TL;DR: The Commit Company is being acquired by Frappe Technologies on 1st January 2026. Most of the team is joining Frappe, and all existing products and libraries will be moved to the Frappe GitHub repository.

A little over three years ago, I received an email from Rushabh asking me to build something for the Frappe ecosystem under the Frappe Incubator program. After sharing a few (overtly) simple project ideas, he liked the idea of building an open-source Slack alternative for the Frappe ecosystem. We flew to Bangalore for FOSSHack 3.0 and built the first version of Raven. If you’re interested in watching our submission video - we’ve just made it public on YouTube. (Please ignore the audio quality - all three of us were down with a pretty bad flu and had coded for ~48 hours prior).

A few weeks later, we formally set up a company to build open-source products and tools for the Frappe ecosystem. To sustain operations financially, we worked with an awesome client based in the US to build a SaaS platform for them on top of Frappe Framework and React. This allowed us to keep building open source products on the side while we worked with them for four days a week.

Fast forward a couple of years and Raven today is installed on over 600 active sites on Frappe Cloud. We’ve built a lot of tooling around Frappe and React with frappe-react-sdk, and also shipped a mobile app using React Native. While there’s still a lot we want to improve (I could think of at least 30 things just off the top of my head), I’m incredibly proud of the team for what we’ve been able to ship with limited time and resources.

Why join Frappe?

The main reason why we started the company was to build high-quality products. That’s it. We set really high standards for ourselves and wanted to match them with execution. But you can’t build something great when you’re only able to work on it one day a week.

As Raven’s user base grew, so did the expectations and support requests. At the end of the day, we need to do justice to our creations, our products and the users who rely on them. While we obsessed over details, we weren’t able to execute at the pace we wanted.

You can’t beat compounding

With more time available to us, we’ll be able to build faster and more importantly, learn faster. Skills compound over time, and so does product quality. This was especially evident at this year’s Frappeverse where relatively new Frappe products (CRM, Insights etc) progressed much faster than they had a year ago.

Joining Frappe gives us the space to focus fully on building, and finally have a real shot at matching the quality bar we set with the execution it requires.

A personal note

There’s a great article by Karri Saarinen (co-founder of Linear - a product I really look up to) about why quality is so rare. https://linear.app/now/why-is-quality-so-rare

It talks about craft - “the deliberate attention put into making something excellent, not because someone is checking, but because it matters to the maker.” But craft needs time and space, free from arbitrary deadlines. To build something excellent, it needs to be created without any expectations of metrics and revenue.

I felt this (the art of it) very strongly while building Mint.

I had been thinking about the problem of bank reconciliation for months, and researched how other products like QuickBooks approached it. But I never really got the time to build it until late July of 2025, when I finally had a couple of weeks to myself. I blocked out all noise and obsessed over the smallest details. If a date picker jumped position when switching months, I’d spend two hours trying to fix it. It didn’t matter whether Mint would be used by anyone, nor did I set any deadline for it. I built it for myself, for the pure joy of building. To this day, I think it’s the best product I’ve built.

After this, I thought to myself - what if I could do this all day, everyday? When Rushabh offered us the opportunity to join Frappe, it made perfect sense to me.

What does this mean for our users?

As part of this transition, all our products and libraries will move under Frappe and will continue to receive active development, maintenance, and support.

Raven

1. Version 3: With more time and focus, we’ll be moving ahead with Raven v3, along with a refreshed mobile app, over the coming months.
2. ERPNext Integrations: We’ll be improving the Raven chat experience inside the Desk interface. This has been overdue, and we will bring over all essential features for chat inside Desk.
3. Product Support: Raven will now be an official Frappe product. As a result, enterprise support for Raven will be available on Frappe Cloud, in line with other Frappe products.

ERPNext

I’ve been using ERPNext for the past few years, and joining Frappe gives me the opportunity to work directly on some of its core workflows - especially around accounting and day-to-day usability.

Much of this work will focus on improving everyday workflows in ERPNext, following the same approach we took with Mint when improving the bank reconciliation experience. The same UX principles - reducing friction, simplifying flows, and improving clarity - will be applied across core accounting areas such as payments, payables and receivables, and financial statements. I’ll share updates as this work progresses, primarily through posts on the Frappe forum.

We’re also planning to add native OCR support, along with LLM-based data extraction and mapping, to help capture key information from documents like invoices. The goal is to reduce manual data entry, have side-by-side file previews with forms, and make document-driven workflows smoother in ERPNext. We’ve explored parts of this already through Raven’s AI Agents, and the next step is to bring these capabilities more deeply into the Framework and ERPNext itself.

First-class support for React and React Native

We’ll continue investing in our core libraries - frappe-js-sdk, frappe-react-sdk, and frappe-types - to expand their capabilities and ensure they’re well maintained over the long term.

Support for React and React Native has been a long-standing request from the Frappe community, and with this acquisition, it will now be officially supported by Frappe :)

Based on our experience building Raven’s mobile app in React Native, we’ll also be working on building a UI component library based on the Espresso design system across both web and native environments.

Developer Tooling and Marketplace

With Commit, our initial focus was on improving the quality and accessibility of documentation for Frappe apps. We’ll continue building on this, including work towards Git-driven documentation for Frappe apps, making it easier for developers and the community to contribute and keep documentation in sync with code.

Having built and shipped apps as third-party developers on the Frappe Cloud marketplace, we’ve gained a clear view of what works well today and where app publishers face friction. Areas such as visibility into usage, telemetry, and user feedback can be improved to better support third-party developers.

Going forward, we plan to work on these gaps with the aim of making it easier for app publishers to monitor, maintain, and improve their apps—ultimately raising both the quality and breadth of apps available on the Frappe Cloud marketplace.

We’re excited to keep building - this time, as part of Frappe.