Appsmith pioneered self-hosted internal tools
Abhishek Nayak, CEO of Appsmith, on building an open source internal tool builder
Self hosting made Appsmith an answer to a security and procurement problem that cloud only internal tool builders could not solve. Teams building admin panels on top of production databases often could not expose those systems to a vendor cloud, or justify an enterprise contract just to keep the tool inside their own network. Appsmith launched with self hosting from the start, which let engineers install it like infrastructure instead of buying it like packaged SaaS.
-
The practical blocker was database access. Internal tools sit on top of Postgres, MySQL, Stripe, Salesforce, and other sensitive systems. Appsmith framed self hosting as a way to keep those connections inside a company’s own servers, instead of opening database access to an outside cloud service.
-
This stood out because Retool treated on prem deployment as an enterprise feature, and its sales team heard repeated objections from buyers who needed on prem for medical or other sensitive data but could not justify a six figure contract. Appsmith turned that gated enterprise feature into a free default.
-
Later entrants copied the pattern. Budibase and ToolJet both emphasize open source and self hosting, which shows that deployment control became a core requirement in the category, not a niche edge case. Once one product proved developers wanted this, self hosting became table stakes for the open source wave.
Going forward, self hosting keeps pushing internal tool builders toward an infrastructure model, where the winner is the product that plugs into production systems with the least security friction and the lowest pricing friction. That favors platforms that can start as a free install inside engineering teams, then expand across support, ops, and compliance once those first apps are in production.