flowbaker

Execution engine powering Flowbaker, a no code platform to build, connect, and automate workflows.

Runssource: GitHubhomepageGoApache-2.0commit b0cfbae449e8

Go, Apache-2.0 licensed. The project labels itself: agents, ai, ai agents, aiagents, automation, integration, integration platform and integrations.

flowbaker runs. An Argusic agent installed it in 4.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Flowbaker Executor builds from source with Go 1.27.3, its test suite passes entirely (3 packages, 142 assertions), and the binary responds to all CLI commands (help, status, start).

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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
1
last tested
stars
205
forks
21
open issues
2
watchers
3
size
3 MB
created
last push

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.

Time lost to each failure while testing flowbaker, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Go 1.25 required but not installed in container3.5 minutes
  • GOPATH not configured0.5 minutes
Install time
5 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
go test ./... exited 0 with 3 packages ok (pkg/dataschema, pkg/domain, pkg/integrations/ai_agent); ./flowbaker --help printed usage; ./flowbaker status printed 'Executor is not set up'; ./flowbaker start launched the interactive setup flow through to registration
Model tokens used
92,614
Exact commit tested
b0cfbae449e8
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

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

exec
/bin/sh -lc '# Verify test counts explicitly
export PATH="/home/runner/go/bin:$PATH" && export GOROOT="/home/runner/go" && export GOPATH="/home/…
 succeeded in 1406ms:
142
ok    github.com/flowbaker/flowbaker/pkg/dataschema  0.006s
ok    github.com/flowbaker/flowbaker/pkg/domain  0.005s
ok    github.com/flowbaker/flowbaker/pkg/integrations/ai_agent  0.008s
142 individual test assertions all passing across 3 test packages. Now compute the elapsed time.
tokens used
92,614
142 individual test assertions all passing across 3 test packages. Now compute the elapsed time.

Replay 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

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Took 4.5 minutes to install, slower than the median of the 40 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 41 agents projects Argusic has installed and timed, flowbaker was the 22nd fastest to reach a running state, and 29 of 41 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 4.5 minutes after the clone.

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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.03

Topics (from GitHub)

agentsaiai-agentsaiagentsautomationintegrationintegration-platformintegrationslow-codeno-codeself-hostedworkflowworkflow-automationworkflow-engineworkflows

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/flowbaker.svg)](https://argusic.com/subject/flowbaker)

Questions

Does flowbaker run?
Yes. flowbaker runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test flowbaker?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit b0cfbae449e8. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test flowbaker?
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 flowbaker take to install?
4.5 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 flowbaker need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing flowbaker?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does flowbaker compare with the alternatives?
Of the 41 agents projects Argusic has installed and timed, flowbaker was the 22nd fastest to reach a running state, and 29 of 41 reached one at all.
Where is the evidence for flowbaker?
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.

Discussion