Can I vibecode Make?

KINDA · weekend project

price $12/moyou'd save $144/yrbuild time weekendcategory 🤖 automationreplaced by 0 people

A handful of workflows can be coded quickly, but Make's paid value is the visual builder, app modules, scheduling, observability, and maintenance.

the prompt

Build me a code-first workflow runner to replace Make for my handful of scenarios. Requirements:

- A Node project where each scenario is one file in scenarios/ exporting a trigger
  (cron string or webhook route) and an ordered list of steps, each step an async
  function that receives the previous step's output.
- The runner executes steps in order, retries a failed step 3 times with
  exponential backoff, then halts the run recording the step name and error.
- Every run saved to SQLite (better-sqlite3): scenario, start/end, per-step input
  and output JSON, status. That history is the debugging story, make it good.
- A minimal dashboard on localhost:4880 (Express, server-rendered): scenario list
  with last-run status, click into a run to see each step's payload.
- Webhook triggers land on the same Express app with signature verification
  helpers; cron triggers via node-cron. All credentials in .env.
- Ship two example scenarios: a Stripe payment webhook appends to a Google Sheet
  and sends a Telegram message; an RSS post gets an LLM summary drafted as email.
- Binds to localhost only, single user, no accounts, no telemetry.
- Out of scope: a visual drag-and-drop builder and an app-module catalog. Scenarios
  are code, that is the point of this build.
- README: how to add a scenario, .env keys, and a note that self-hosted n8n is the
  off-the-shelf fallback if maintaining this stops being fun.

$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR

why people still pay

They pay because workflows evolve and break; a maintained builder reduces the upkeep.

what you lose

xvisual scenario builder

xapp modules

xscheduling

xoperations history

xerror handling

xteam governance

share on X ↗"I just replaced Make ($12/mo) with one prompt"

the escape hatch

Don't feel like building it? These folks already made it free.

Activepieces Community EditionA polished visual workflow builder with hundreds of connectors and one Docker command.24kaug 2026open source↗

AutomatischA cleaner, smaller automation canvas when your scenarios do not need Make's long tail.14kjan 2026open source↗

n8n Community EditionThe closest broad replacement, with more self-hosting and fewer glossy scenario diagrams.$0free↗

all 3 free alternatives to Make →· no votes, no pay-to-list · just what's real

the numbers

Make pricing

plan	monthly	annual (per mo)	what you get
free	$0/workspace	$0/workspace	1,000 credits/month; 2 active scenarios; 15-minute minimum schedule; 5-minute execution cap; 5 MB files.
core	$12/workspace	$9/workspace	10,000 credits/month at entry price; unlimited active scenarios; 1-minute scheduling; 40-minute runs; 100 MB files.
pro	$21/workspace	$16/workspace	10,000 credits/month at entry price; unlimited scenarios; priority execution; 250 MB files; 30-day logs.
teams	$38/workspace	$29/workspace	10,000 credits/month at entry price; unlimited users and scenarios; team roles; 500 MB files; 30-day logs.
enterprise	custom	—	Custom credits; unlimited scenarios; 1,000 MB files; 60-day logs; overage protection.

free tier1,000 credits/month, 2 active scenarios, 15-minute scheduling, 5-minute execution cap and 5 MB maximum file size

billingmonthly + annual (annual saves at least 15%); annual credits can remain usable for the 12-month term

hidden costsMost module actions use 1 credit, but AI and code features can use more. Extra-credit packs or auto-purchase are available; credits expire at the end of the monthly or annual term, and scenarios pause when credits run out unless protection is enabled.