Thrum and Make, side by side
Checked on
Make is a visual automation tool where you build scenarios from app modules on a canvas, and every module that runs is billed in credits. Most modules use 1 credit a run whatever the size of the data, while Make’s built-in AI apps use credits by tokens, pages, file size or run time. Thrum counts workflow runs per seat instead, and gives each client a workspace with its own keys, CRM and portal.
Thrum opens soon. Sign up now and you’ll be among the first in.
Which to choose
Choose Make if
You already run your clients’ scenarios in Make, you want AI through Make’s provider with no model account to set up, or you like paying for every app and AI step in one currency of credits.
Choose Thrum if
You want a monthly allowance of workflow runs per seat, an alert when a client’s workflow stops being started, and the forms, CRM and portal on the same account as the automation that uses them.
Feature by feature
Make’s side as of 15 November 2026, with sources below. Where one side clearly does more, the row says which.
- Yes
- Partly
- No, or not found in their docs
Building
- Workflows
- MakeThrum
Yes. Scenarios built from app modules on a canvas.1
Yes. Workflows on a canvas that lays itself out, with branches, loops of up to 500 items and 2 to 8 paths at once.
- AI
Make is stronger here
- MakeThrum
Yes. Make AI Agents and the AI Toolkit run on Make’s AI Provider on all plans; paid plans can connect your OpenAI or Anthropic account instead.1
Partly. An agent step with app actions as tools.
- When a step fails
- MakeThrum
Yes. Its help centre covers error handlers and exponential backoff.1
Yes. A step that meets a server error, a rate limit or a network fault is tried up to 3 times, waiting 5 seconds and doubling to at most 10 minutes. A run restarts from the failed step or any other.
Price
- Billing unit
- MakeThrum
Credits. A module from a non-AI app uses 1 credit per run, so a Google Drive upload costs 1 credit whatever the file size. A few modules use 2 or 10.1
Workflow runs a month per seat: 500 on Solo, 25,000 on Agency, 100,000 on Scale.
- AI steps
- MakeThrum
On Make’s AI Provider, credits follow the tokens used and the model chosen. When you connect a provider, Make charges per operation and the provider bills the tokens.1
On the client’s own Anthropic, OpenAI, OpenRouter or Groq key, and the provider bills the tokens to that key.
- Running out
- MakeThrum
Upgrade the plan, buy extra credits, or turn on automatic purchase of extra credits.1
Add a seat. At the limit, scheduled runs pause while forms keep collecting and the workflows they start keep running.
- Priced by
- MakeThrum
The cost of a credit varies by plan. Its pricing page could not be read for this comparison.1
Per seat: Solo $20, Agency $99, Scale $249 a month. A seat carries clients, workflow runs, forms, responses, records and email.
Client delivery
- One workspace per client
Thrum is stronger here
- MakeThrum
Partly. Organizations and teams, which its help centre lists.1
Yes. Each client is a separate workspace, with its keys, forms, workflows, CRM and portal.
- Forms, CRM, inbox, booking, email, payments
Thrum is stronger here
- MakeThrum
No.
Yes. Forms, CRM, inbox, booking, email campaigns, a blog, a newsletter and payments, built in.
- A workflow that goes quiet
Thrum is stronger here
- MakeThrum
No.
Yes. Learns each workflow’s usual gap and calls it Stopped after 3 times that gap of silence.
- A portal for the client
Thrum is stronger here
- MakeThrum
No.
Yes. A portal per client in their colours: leads, their month, inbox, bookings, email, content and revenue. White-label on Agency and Scale.
- A monthly report to the client
Thrum is stronger here
- MakeThrum
No.
Yes. Emailed to each client on the 1st, in their time zone, and kept in their portal.
In beta on Thrum: the agent step. Built and tested, not yet run against the live services they use.
Using both
A scenario you built in Make can come across without being drawn again by hand. Drop its blueprint into Thrum and it is redrawn as steps, routers turned into paths that run at once and iterators into loops, with a report of what came across. It arrives switched off, with a to-do for anything that did not convert with certainty, so you can move one client’s scenarios over one at a time while the others keep running in Make.
The workflow importer takes n8n workflows too.
Sources, checked 15 November 2026
Make’s pricing page could not be read on the day this was checked, so this page names no Make prices. Make’s side comes from its credits help page, and a No on that side means the page does not cover it.
If anything here about Make is out of date, write to hello@thrum.run and it will be corrected.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.