# Build brief — a focused alternative to Make

> **Verdict:** Partly, if you narrow it · **Buildability:** 63/100 · **Category:** Automation
> **Source:** https://www.canitbevibecoded.com/make
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Make. Verify current pricing and capabilities before acting.

## Context

**Make** — Visual automation platform for scenarios across apps and APIs. It currently costs $12/mo.

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

This brief describes a focused, single-operator replacement for the part of Make that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Implement the needed scenarios as scripts or n8n workflows with API calls, retries, and logs.

- Automate a small number of known workflows with logs, retries, and manual recovery.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Hosted scheduler/worker.
- Secrets.
- Logs.
- Retry handling.

### Data and integrations

- API keys/OAuth.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

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.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Visual scenario builder.
- App modules.
- Scheduling.
- Operations history.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Activepieces](https://github.com/activepieces/activepieces) — Open-source automation platform with app pieces, triggers, and actions

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/make