Open Source Empowers Engineers
Abhishek Nayak, CEO of Appsmith, on building an open source internal tool builder
Open source matters here because the product is being sold to engineers who treat internal tools like code, not like packaged software. In practice, that means they want to inspect bugs, add a missing database connector, build a custom widget, and keep the tool inside their own security boundary. For a support dashboard or admin panel tied to production data, that control is part of the product, not a nice extra.
-
The core internal tools job is usually simple to describe and painful to build from scratch, put a table and form on top of a production database or API so support, ops, or product teams can read data and trigger actions like refunds, approvals, or account fixes. That is why build it yourself with React is often the real alternative.
-
Appsmith’s open source angle is most valuable for technical teams that want self hosting and extension. A non technical end user just wants the dashboard to work, but an engineer cares whether a missing integration can be added directly, whether the code can be inspected, and whether the system can run on infrastructure they control.
-
This is also where the market splits. Retool wins on speed and polish for common admin panel patterns, while open source tools like Appsmith create price and flexibility pressure by appealing to teams with stronger engineering talent and stricter security or customization requirements.
The category is moving toward more developer controlled internal software, not less. As AI makes it cheaper to generate the first version of an app, the ability to inspect, edit, self host, and extend the result will matter more, which favors products that fit normal engineering workflows rather than trapping teams inside a closed builder.