Retool

Retool became the reference point for low-code internal tools by making a specific promise: connect your database or API, drag components onto a canvas, write a few lines of JavaScript to wire them together, and ship a working admin panel in an afternoon. That promise holds. Its component library is deep, its connector list covers virtually every database and SaaS API an engineering team encounters, and the permission model is serious enough for enterprise use.

The trade-offs are structural. Retool bills per seat, which means every analyst, support agent, or manager who needs read-only access to a dashboard carries a monthly line item. Teams that start with five internal users often find themselves explaining a five-figure annual bill once the tool spreads across operations, finance, and customer success. The self-hosting option exists but is reserved for the Enterprise tier, so smaller teams on Team or Business plans have no path to running Retool on their own infrastructure.

Vendor lock-in is real: Retool apps are defined in a proprietary format with no standard export. If you decide to migrate, you are rebuilding — not porting. For teams with modest headcounts and stable user counts, the speed-to-ship advantage can outweigh the cost. For everyone else, the open-source alternatives in this category now cover most of the same ground without the per-seat tax.