Retool Review

Retool Mobile and Retool Workflows shipped after the core platform — that's the moat. Internal tooling is a category where the visual builder is table stakes; what matters is whether the vendor keeps shipping past that. Founded 2017, $3.2B at last raise, David Hsu still CEO.

The Free tier handles 5 end users. Team starts at $10 per seat. Business at $50 per seat unlocks SSO, audit logs, and the Git Version Control workflow that lets your platform team treat apps like code. Appsmith is the open-source comparable, but the polish gap shows up by month two.

But the user-count meter bites — viewers count toward your tier limit, and one company-wide dashboard can reprice the contract fast. The JavaScript Code Editor exists for the edge cases your no-code champion hits by week three. Pilot one team for a quarter before standardizing the org.

I've deployed Retool across our engineering org over the past year, and it's transformed how we build internal tools. What used to take weeks now takes days - our developers can spin up complex admin interfaces connecting to multiple databases and APIs without writing boilerplate React code. The self-hosted option was crucial for us given our compliance requirements, and the deployment was surprisingly smooth.

The platform handles our scale well - we're running about 200 internal apps with 500+ daily users. Performance can get sluggish with very large datasets, but for 95% of our use cases it's solid. My biggest concern remains vendor lock-in; while we can export apps as JSON, migrating away would be a significant undertaking.

Stripe, Amazon, Netflix, and OpenAI run internal tooling on Retool — a roster, after eight years and a $3.2B valuation in 2022, that tells a CTO this isn't a dev-tools fad. Founded 2017 by David Hsu, it sits in the rare slot of low-code that engineers pick over building from scratch.

The architecture is the thing. Retool Workflows for scheduled jobs, Retool Mobile for field tooling, and a JavaScript escape hatch inside every component mean you don't paint into a no-code corner. Apps export as JSON and self-host on Docker — the data residency story is solved.

But the catch is exit cost. The component model and event handlers are Retool-shaped, not React-shaped, so migration off is a rewrite, not a port. At $50 per user monthly on Business plus end-user packs, the bill scales with adoption — Appsmith and Superblocks are cheaper, but neither has the integration depth.

I've been using Retool daily for over a year to build admin panels and internal dashboards. What sold me initially was how quickly I could connect to our Postgres database and build a functional interface in minutes rather than days. The drag-and-drop builder with JavaScript everywhere approach just clicks for developers.

The real power shows when you need complex logic - being able to write JavaScript transformers and custom components means I'm never truly blocked. Our team has built everything from simple CRUD tools to complex approval workflows. The built-in version control and environments setup has made deploying changes much less scary.

My main frustration is debugging complex queries and state management. When you have multiple queries triggering each other, tracking down issues can feel like detective work. The error messages could be more helpful too.

I've been using Retool daily since we needed a way to build custom dashboards that pull data from multiple sources - Salesforce, Google Analytics, our SQL databases, and various APIs. What started as a simple lead scoring tool has expanded into a suite of internal apps our team relies on.

The biggest win? We built a campaign performance dashboard that would've taken months of engineering time in just two weeks. Our ops team can now query customer data, update segments, and monitor attribution without constantly pinging data engineering. The drag-and-drop interface makes it possible for me to prototype tools myself before handing off to our technical marketing ops manager.

That said, while it's 'low-code,' you still need SQL knowledge and basic JavaScript understanding to really unlock its power. We've had to invest in training for team members who aren't technically inclined.

I've been using Retool for about 14 months now, initially to build a custom dashboard for our revenue reconciliation process. What started as a single use case has expanded to over a dozen internal tools across finance operations. The ability to quickly spin up interfaces that connect to our various data sources has been game-changing - we've automated processes that used to take hours of manual Excel work.

The pricing structure based on monthly active users seemed reasonable at first, but we learned the hard way that 'viewer' access still counts toward your user limit. Our costs jumped 40% in Q3 when we rolled out a company-wide KPI dashboard. The self-serve pricing is transparent up to a point, but once you hit enterprise tier, everything becomes a negotiation. Still, when I calculate the hours saved versus the platform cost, we're coming out ahead by a significant margin.

The State tab is the feature you don't notice until you've spent a week without one. Every component, query, and transformer shows live values in a left-rail tree — click a row, see the JSON, set a watch. JavaScript transformers run inline, and autocomplete actually knows your schema.

Retool Workflows covers the cron and webhook side — scheduled jobs, branching, retries — so teams stop writing throwaway Lambdas for nightly syncs. Free caps it at 500 runs/month, honest but tight. However, debugging cross-query state when six components fire on load still feels like chasing an Appsmith event chain.

Billing splits builders at $10/mo from internal users at $5/mo, and Business jumps to $50/builder for SSO and audit logs. Docs read like engineers wrote them — runnable snippets, error codes. The catch is a viewer who clicks "duplicate app" becomes a builder that cycle.

I've been using Retool daily for about 14 months now, mainly to build admin panels and data dashboards for our operations team. What hooked me was being able to drag and drop components and connect them to our databases without writing much code. I'm not a developer, but I can now build tools that would've taken weeks of dev time.

The learning curve was steeper than expected - it took me a solid two weeks to really get comfortable. But once things clicked, I was building new tools weekly. The pre-built components handle 90% of what I need, though sometimes I wish they were more customizable.

My biggest gripe is performance with larger datasets. When pulling thousands of rows, things can get sluggish. The mobile experience is also pretty rough - I've learned to just use desktop.

I championed Retool at my startup for building admin panels and internal dashboards. The first six months were great - dragging components, connecting to our databases, shipping tools in hours instead of weeks. But then the cracks showed. Apps started freezing with more than 50 rows of data. The editor became unbearably slow, taking 30+ seconds to load. Version control conflicts corrupted entire apps twice, forcing us to rebuild from scratch.

The final straw was our renewal - they wanted 4x our original price with 30 days notice. Support's response to performance complaints? 'Try reducing your query complexity.' We're now rebuilding everything in React admin frameworks. What should have saved developer time became a constant source of firefighting.