Vibe-Workflow
Free, open-source alternative to Weavy AI, Krea Nodes, Freepik Spaces & FloraFauna AI, node-based AI workflow builder for generative image & video pipelines
Runs with mockssource: GitHubhomepageJavaScriptMITcommit 121bde4ef049
JavaScript, MIT licensed. The project labels itself: ai, ai workflow builder, artistic intelligence, comfyui, creative tools, fastapi, florafauna ai alternative and freepik spaces alternative.
Vibe-Workflow runs, with stand-ins for the services it depends on. An Argusic agent installed it in 16 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Frontend Next.js app serves on port 3000, backend FastAPI serves on port 8000 proxying to a mock MuAPI on port 9000; root page and workflow listing page both return HTTP 200, backend health check returns 200, and all workflow API endpoints respond correctly through the mock.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- MuAPI external API key required5 minutes
- Node.js v18 too old for Next.js 16 (requires >=20.9.0)3 minutes
- Mock API returned wrapped object but frontend expected bare array for get-workflow-defs1 minute
- Install time
- 16 minutes
- Cold machine to finish
- 16 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- curl -s http://localhost:3000/ returned 200; curl -s http://localhost:3000/workflow returned 200 (no __next_error__, renders Test Workflow); curl -s http://127.0.0.1:8000/api/health returned {status:healthy}; curl -s http://127.0.0.1:8000/api/workflow/get-workflow-defs returned mock data array; curl -s -X POST http://127.0.0.1:8000/api/workflow/create returned mock creation response; curl -s http://127.0.0.1:9000/health returned mock-ok
- Model tokens used
- 180,957
- Exact commit tested
- 121bde4ef049
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
2. **MuAPI external API key required** — stood up a schema-correct mock FastAPI server at `localhos…
3. **Mock response format mismatch** — the frontend expected a bare array from `get-workflow-defs`,…
**Verification**:
- Frontend homepage at `localhost:3000` → HTTP 200
- Workflow listing page at `localhost:3000/workflow` → HTTP 200, renders "Test Workflow" from mock …
- Backend health at `127.0.0.1:8000/api/health` → `{"status":"healthy"}`
- Workflow CRUD via backend proxy → all endpoints respond correctly through mock
- Mock MuAPI health → `{"status":"mock-ok"}`
**Running services**:
- Frontend: port 3000
- Backend (FastAPI): port 8000
- Mock MuAPI: port 9000Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 16 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 237 ai projects Argusic has installed and timed, Vibe-Workflow was the 200th fastest to reach a running state, and 168 of 237 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.03 |
Topics (from GitHub)
aiai-workflow-builderartistic-intelligencecomfyuicreative-toolsfastapiflorafauna-ai-alternativefreepik-spaces-alternativegenerative-aiimage-generationkrea-nodes-alternativenextjsnode-editoropen-sourceself-hosted-aivideo-generationweavyweavy-ai-alternativeweavyaiworkflow-automation
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vibe-workflow)Questions
- Does Vibe-Workflow run?
- Vibe-Workflow runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 16 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test Vibe-Workflow?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 121bde4ef049. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Vibe-Workflow?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Vibe-Workflow take to install?
- 16 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does Vibe-Workflow need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Vibe-Workflow?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Vibe-Workflow compare with the alternatives?
- Of the 237 ai projects Argusic has installed and timed, Vibe-Workflow was the 200th fastest to reach a running state, and 168 of 237 reached one at all.
- Where is the evidence for Vibe-Workflow?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.