Major

Retool Price: What Seats Cost and the Cost Model Beyond Seats

Comparing Retool’s seat-based pricing? Look beyond the headline plan to who builds, who uses the app, and what happens as the workflow scales.

Jason BaoUpdated
Retool Price: What Seats Cost and the Cost Model Beyond Seats

Retool pricing depends on the plan you choose and the role each person holds: builders who create apps, internal users who run them, and external users who reach them from outside your company. Enterprise terms are custom. Check retool.com/pricing on the day you buy, because plans and gates change. The useful question is what your bill looks like after adoption grows, and whether work that repeats keeps costing you every time it runs.

That second question is where Major fits. Major is the enterprise platform where agents build the software they run on. An agent works out a repeatable job once, builds an app for it, and then runs the app as code. Hosting, database, and deploy come with the app, so cost is front-loaded and then flat instead of re-spent on every run.

Why teams look beyond Retool price

The pricing complaints you find online are individual reports, and you should read them that way. One Hacker News commenter called the Retool pricing "so annoying". An author on Medium wrote that public apps on Retool Cloud come with the Business and Enterprise plans and described those plans as expensive. Another commenter said vendors generally are slow to respond and do not understand their own pricing.

None of that is a current price schedule, and none of it speaks for every customer. It does point at the real fear. A proof of concept looks cheap with three builders. Then the app reaches the whole ops team, then contractors, then customers, and the role mix drives the bill.

Add agents to the picture and a second meter appears. If an agent reasons through the same reconciliation or triage on every run, you pay model costs on every run, on top of any seat fees.

Compare the cost model, not just the plan

Each option below gets the same three questions: how work is built and run, what drives cost, and what to ask about governance and deployment. No prices are listed on purpose. Verify each on the vendor's own page.

  • Major: agents and people build apps that run as deterministic code with managed state. The cost driver is the one-time build plus model calls for real judgment, since repeatable steps run without the model. SSO, permissions, audit, database, and storage are handled at the platform layer from the first deploy.
  • Retool: people build internal apps and workflows on a visual canvas. Cost drivers to verify are builder, internal-user, and external-user roles, plus any usage-based charges. Ask which governance and deployment options sit on which tier.
  • Superblocks: a builder for internal apps and workflows. Verify how its plans scope users and what is gated. Ask where audit and deployment controls land. See Retool vs Superblocks for the direct comparison.
  • Appsmith: an app builder with cloud and self-hosted routes. Verify which plan carries your user count and which governance features. Ask who operates the deployment you choose.
  • Budibase: an app builder with a self-host option. Verify how plans scope users and automations. Ask what you run yourself and what you pay for.
  • ToolJet: an app builder with cloud and self-hosted routes. Verify user and plan scoping and feature gates. Ask what governance you get at each tier.

For a broader selection guide, read Retool alternatives for internal apps.

The thing every builder in this list shares is that a person has to build each app, and the app is an interface. Major starts from a different place. The agent builds the app as part of doing the work, so the app is both the control surface for your team and the execution layer the agent runs through.

How to estimate the real cost of an internal app

A plan headline is a poor basis for comparison. Fill in roles and gates first, then look at recurrence. Copy this worksheet into a spreadsheet and leave every cell blank until you have vendor-confirmed numbers.

  1. Builders: how many people create or edit apps? Leave the price blank.
  2. Internal users: how many employees only run apps?
  3. External users: how many customers, vendors, or contractors need access?
  4. Feature gates: do you need SSO, audit logs, role-based access, or public apps? Write down which tier each sits on.
  5. Hosting and deployment: cloud or self-hosted, and who operates it?
  6. Model and API usage: which steps call a model or a paid API on each run?
  7. Build and update work: hours to build, and hours each time requirements change.
  8. Recurrence: how many times a week does each workflow run?

Rows 6 and 8 decide the long-term bill, and they are the ones most teams skip. A workflow that runs 500 times a week and calls a model each time keeps costing you. The same workflow, once built as an app, runs the checks as code and calls the model only when a case needs judgment. For background, see how AI agent costs behave across repeated work and the enterprise app builder criteria.

The model never fully leaves. Classification and exceptions still need reasoning, and that usage is variable. The claim is that it carries a smaller share of the load.

How to build this on Major

The best way to see the cost model is to build the tool that tracks it: a seat and workflow cost register.

  • App and state: a Major app backed by managed PostgreSQL. Tables hold the app inventory, role counts, plan and capability checks, and run history.
  • Connectors: PostgreSQL for the register and Slack for the weekly summary and approval request.
  • Deterministic checks: the app computes role totals, flags apps missing cost inputs, and records every run. This is code, so it gives the same answer every time.
  • Agent judgment: when a new app request arrives, the agent classifies it and flags missing cost inputs for a human owner. It does not invent totals.
  • Trigger: a weekly scheduled run, plus an on-demand review when a new app request lands.
  • Governance: the agent's PostgreSQL credential reaches only the register tables, and its Slack permission covers only the designated review channel. Role-based access controls who can approve, and audit logs record each action.

The agent reasons about the process once, then the app runs it. Start on Major and describe the register in a sentence to get a first version.

The Major take

Internal-app spend is hard to judge when roles, plan gates, and repeated model work are blended into one number. Seat-based pricing makes the role mix matter. Agent workloads make recurrence matter. You need to see both.

Major resolves the second half structurally. Agents build a deterministic app once and run repeatable steps as code, with hosting, database, and deploy included. State lives in the app instead of a context window, and permissions and audit apply where the agent acts. Reason once, run forever.

That makes Major the way to build internal applications and AI agents together, on one governed layer, with a cost curve that is front-loaded and then flat for repeatable work.

Start building on Major

Build a governed cost register on Major to track internal-app roles, capability gates, and repeatable workflow costs.

Related articles

Frequently asked questions

what is retool good for?
Retool is used to build internal tools such as admin panels, dashboards, and workflow apps on top of databases and APIs. Teams use it so employees can view and change business data without custom front-end work. Evaluating it for your team is a separate question from what it costs, which depends on plan and user roles.
is retool profitable?
Public profitability information for Retool is not established by the pricing material cited here, and user pricing complaints say nothing about it. Retool is a private company, so check recent, reliable reporting directly if profitability matters to your purchase decision.
does retool have an app?
Retool is a platform for building internal apps, and it offers ways to run those apps on web and mobile. Whether it has an app depends on what you mean: apps you build with Retool, or a Retool-made app for end users. Check Retool's current product pages for specifics.
how do I estimate the total cost of an internal app?
Count builders, internal users, and external users, then note which tier holds the capabilities you need, such as SSO, audit logs, or public apps. Add hosting or deployment, usage-based charges, model or API calls per run, build and update time, and how often the workflow repeats. Leave out any universal total.
how is Major's cost model different from seat-based internal app pricing?
On Major, an agent builds an app once and then runs repeatable work as code, with hosting, database, and deploy included. Cost is front-loaded and then flat for that work instead of re-spent on each run. The model still handles judgment calls, so some variable usage remains.