Retool vs a Custom Dashboard: Low-Code or Custom-Built

A fair look at Retool-class platforms against custom-built dashboards: pricing model, lock-in and who maintains what.

By · 17.11.2026

The short answer: a low-code platform like Retool is quick for a throwaway internal tool, but if the dashboard is going to be used by many people, shown to customers, or relied on for years, a custom dashboard costs less over time and you own it. Per-user licensing grows with every person who gets access, the apps live in the platform's format, and someone on your team still has to build and maintain them. A custom dashboard has none of those, and a focused first version is a modest project.

Retool-class tools are good products, and the comparison is about fit rather than quality. The fit changes as the audience, the stakes and the time horizon grow.

What each approach is

A low-code internal tool platform gives you a visual builder, pre-made components such as tables and forms, and connectors to databases and APIs. You assemble the interface mostly by configuration, writing code only where needed. The platform hosts the result, or in some cases you host it yourself under a paid licence. Retool is the best-known example, and similar tools exist.

A custom dashboard is a web application written in a normal programming language and framework, hosted wherever you choose, reading from your data sources. You own the code, the hosting and the design, and your builder handles the build and maintenance work.

Same-criteria comparison

CriterionLow-code platform (Retool-class)Custom dashboard
Cost structureSubscription, typically priced per user with tiers by role. Cost rises with the number of people using it.One build cost, then hosting and maintenance. No per-user licence, so adding people costs nothing.
Time to valueFast. A working internal tool can exist in days, built by a technical person.A first useful version in weeks, designed around your data and your users from the start.
FlexibilityHigh within the platform's components. Unusual layouts, behaviour or branding can be hard or impossible.Any interface, any logic, any data source, with your branding.
Maintenance burdenThe platform maintains hosting and core components. You maintain the apps you built and adapt to platform changes.Your builder maintains everything on an agreed basis, including updates and security.
Lock-inReal. Apps are built in the platform's format and generally cannot be exported as standalone code.You own the code and can move builders or hosting.
Team requiredA technical person comfortable with SQL and some JavaScript to build and look after each app.A builder, with one decision-maker on your side. No in-house developer needed.

Choose a low-code platform when

You are a solo founder or a tiny team, you are the technical person, and you need a quick admin panel for ten users or fewer. A platform gets that live in days, and the per-user cost is small at that size.

Choose a custom dashboard when

The platform's constraints start costing you. If any of these sound like your last quarter, you have probably reached that point:

  • The renewal quote went up because more people needed access. A 40-person company giving most staff read access watches the per-user licence become a meaningful annual cost, one a one-off build would undercut within a couple of years.
  • Customers or partners need to see it. A branded, polished view for clients is a poor fit for most internal-tool platforms, and external users can change the pricing picture sharply.
  • The person who built the Retool apps is the only one who understands them. If they leave or get busy, you have a key-person problem inside a tool that was supposed to remove one.
  • You keep working around the component library. The layout almost works, the interaction is nearly right, and every compromise is a small daily annoyance for the team.
  • The dashboard has become a core business asset. Depending on a vendor's pricing and roadmap for something you run the company on is a risk you may not want.
  • You need behaviour the platform does not offer, such as complex data processing, unusual interactions or performance at volume.

Who maintains what

This is the question people forget to ask. With a platform, the vendor maintains the infrastructure and components, but you maintain every app built on it, and platform updates sometimes change behaviour. In a small company that means whichever technical person built it, so there is key-person risk even with low-code.

With a custom build, maintenance is done by the people who built it, on terms you agree in advance. Neither option removes maintenance; the difference is who is accountable for it.

A fair note on lock-in

Low-code lock-in is real. Apps are built in the platform's format, so moving away means rebuilding. If the tool is cheap to rebuild and you would not mind doing so, that matters little. If it will hold core logic for years, the cost of rebuilding later is worth pricing in now. Check the pricing model and export options before committing, and re-read them annually, since platform terms change. A platform version also makes a good specification for the custom one, which is how many of our dashboards start.

Decision checklist

If two or more of these sound familiar, a custom dashboard will pay for itself:

  • The number of people with access is growing, and so is the licence bill.
  • Customers, partners or suppliers need to see some of it.
  • One person built the current tools and is the only one who can change them.
  • The design needs to match your brand, and the platform will not quite allow it.
  • You have already worked around a limitation of the platform more than once.
  • You expect to use this tool for three years or more.
  • You have read the platform's export terms and not liked what you saw.

Book a short call and we'll tell you honestly if it won't.

FAQ

Isn't Retool cheaper than a custom dashboard? At very small scale, usually. As the user count and time horizon grow, a one-off build becomes cheaper. Compare your expected user numbers over three years, including the hours your technical person spends maintaining platform apps.

Can't we just keep building in Retool? You can, and it works until the audience, the branding or the licence bill outgrows it. A common route is to keep the platform version as a working specification and rebuild it as a custom dashboard once the need is proven, which removes the guesswork from the build.

What about migration? Will we lose what we have? You rebuild rather than export, but the platform app tells us exactly what the dashboard must do. Nothing about the data changes; it stays in your own databases and tools, and the dashboard reads from the same sources.

Does a custom dashboard have to be expensive? No. A focused dashboard with a few connected sources and a clear scope is a modest project. Cost grows with scope, so we keep the first version small and expand it only where the team asks for more.

Do low-code tools need a developer? Usually someone technical, yes. They are far easier than writing everything from scratch, but they still involve SQL, APIs and scripting, and that person becomes the maintainer. With a custom build, that responsibility sits with us.

What about self-hosting a low-code platform? Some platforms offer self-hosted editions under paid licences. This addresses data residency but you then run the infrastructure, which brings back part of the maintenance burden you were trying to avoid.

Where BlackCard comes in

We design and build custom business dashboards for companies of 5 to 50 people, from the metric definitions to the live page, connected to the sources you already use. A first version usually lands within a few weeks, you own the code and hosting, and there are no per-user fees as the team grows. Our guide on how to set up a business dashboard shows the process we follow. The first call is free and diagnostic: bring what you have built or budgeted, and we will tell you where a custom build would change the economics.

See how our business dashboards service works, or book a short call and bring your use case.