flowctl

An open source self-service workflow execution platform

Runssource: GitHubhomepageGoApache-2.0commit d55e591a0dfe

Go, Apache-2.0 licensed. The project labels itself: automation, devops, mcp, orchestration, platform engineering, scheduler, self service and workflow.

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

The flowctl binary builds and runs, PostgreSQL 16 serves the database, migrations apply, the server starts on port 7000, login with admin credentials succeeds, and authenticated API endpoints return valid data.

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.07 (measured)
recorded runs
1
last tested
stars
352
forks
28
open issues
5
watchers
2
size
51 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 flowctl, 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.

  • PostgreSQL not installed2 minutes
  • Go not installed in container1 minute
  • Build failed: //go:embed all:site/build requires site/build directory1 minute
  • libpq.so.5 missing at runtime1 minute
  • PostgreSQL failed to start: could not create lock file in /var/run/postgresql1 minute
  • Config validation failed: missing required fields1 minute
Install time
9 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
go test ./... exited 0 (9 packages passed). Server started on :7000, GET /ping -> 200, GET /info -> 200 (returned version/dev), POST /login with admin credentials -> 200, GET /api/v1/namespaces -> 200 (returned default namespace), GET /api/v1/users -> 200 (listed system + admin users), GET /api/v1/users/profile -> 200 (returned admin user)
Model tokens used
275,004
Exact commit tested
d55e591a0dfe
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.

/bin/sh -lc 'ARGUSIC_RESULT: {"install_succeeded": true, "launch_succeeded": true, "install_minutes…
 exited 127 in 0ms:
/bin/sh: 1: ARGUSIC_RESULT:: not found
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 9…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 9, "errors": [{"msg": "Go …
exec
/bin/sh -lc "printf 'ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"in…
 succeeded in 0ms:
tokens used
275,004

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 6 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 9 minutes to install, slower than the median of the 38 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 39 automation projects Argusic has installed and timed, flowctl was the 32nd fastest to reach a running state, and 27 of 39 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 9 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.07

Topics (from GitHub)

automationdevopsmcporchestrationplatform-engineeringschedulerself-serviceworkflowworkflow-automation

Embed the badge

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

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

Questions

Does flowctl run?
Yes. flowctl runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test flowctl?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d55e591a0dfe. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test flowctl?
The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does flowctl take to install?
9 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 flowctl need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing flowctl?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does flowctl compare with the alternatives?
Of the 39 automation projects Argusic has installed and timed, flowctl was the 32nd fastest to reach a running state, and 27 of 39 reached one at all.
Where is the evidence for flowctl?
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