mrkeyoor.comAsk

superplanehq/superplanetested 01 Oct 2026commit f9711f4

superplane review

Pilot SuperPlane for one clearly specified backlog task if its agent-to-review workflow matches your team's needs.

  • Install 90 s
  • Build 8 s
195/278passed, run exited non-zero
  • 415 packages
Automationevaluationupdated 31 Oct 2026
+67stars / 7d

Consider SuperPlane for a bounded pilot if you want coding agents to take well-defined backlog tasks through verification and human review. The SuperPlane README describes a system that coordinates coding agents, source control, CI, review, approvals and feedback. Our run on October 1, 2026, at commit f9711f4 does not establish that this complete workflow works in production.

Verdict

Pilot SuperPlane for one clearly specified backlog task if its agent-to-review workflow matches your team's needs. Our October 1, 2026, run at f9711f4 left build errors in the retained output and a nonzero test exit; it did not validate deployment or successful task delivery. Before expanding, reproduce the documented setup, resolve the observed failures, verify permissions and demonstrate recovery from a failed agent run.

We ran it

Lab card: what happened when we ran superplane
Lab card from our sandbox run
Screenshot of superplane (superplane.com)
superplane.com
Install✓ · 90s415 packages
Build✓ · 8s
Tests✗ · 178s195 passed · 83 failed of 278 (go test)
Repo9013 files~1,377,936 lines of source · 57.5 MB · 0 CI workflows · Dockerfile · tests dir

Answers from our run

Does superplane build from source?

Dependencies installed in 90 seconds (415 packages), and the build succeeded in 8 seconds. We cloned commit f9711f4 into a clean Debian container with 3 CPUs and no project-specific setup.

Do superplane's tests pass?

No. The project's own test command finished in 178 seconds and reported 195 passed, 83 failed (go test).

Who should not use superplane?

Teams expecting our sandbox results to demonstrate successful issue-to-pull-request delivery: that workload was not tested.

What are the alternatives to superplane?

Windmill, Temporal. Pilot SuperPlane for one clearly specified backlog task if its agent-to-review workflow matches your team's needs.

Setup2/5Material unresolved obstacles under the visible rubric: the stored build tail reports missing modules and vet-exit:1, while the test command exits 1. Deployment was not validated.
Docs4/5The README has an install section (“Getting started”) and usage in the same section; we did not run its quickstart ourselves.Editor’s note: The supplied README outlines setup routes, but the linked deployment and contributor instructions were not supplied in full or validated.
Community4/5Last push on 2026-08-26 and 10,051 stars.Editor’s note: Contribution invitations and issue activity do not establish sustained participation, maintainer responsiveness or support quality.
Maturity2/5Material unresolved obstacles under the visible rubric: retained build errors and a nonzero test exit remain unexplained, and operational recovery and authorization were not validated.

How we score

Discussed on

  1. hnShow HN: SuperPlane - open source DevOps control plane21 points

Who it’s for

Engineering teams with small, clearly specified backlog tasks and people available to review the resulting changes.
Teams that need agent execution, verification, retries and approval recorded in one workflow.
Operators prepared to validate repository access, integration credentials and recovery before expanding a pilot.

Who it’s NOT for

Teams expecting our sandbox results to demonstrate successful issue-to-pull-request delivery: that workload was not tested.
Teams seeking a verified production deployment or authorization assessment: neither is established by the attached run.
Simple automation that already works as a script or CI job and does not need a separate system to coordinate it.

Setup reality

Our run on October 1, 2026, used commit f9711f4 in our sandbox, configured with 3 CPUs, 8 GB of memory and the golang:1.24-bookworm image. The harness recorded installation at 90 seconds with exit 0, the build step at 8 seconds with exit 0, and testing at 178 seconds with exit 1.

Those command outcomes need qualification. The build tail contains missing-module errors for the OpenAPI client and several protocol packages, followed by vet-exit:1. The stored build status therefore does not establish a clean build. The attached stored parser summaries report 195 passing and 83 failing entries, with a total of 278; the raw measurement labels these as package outcomes. They are not verified counts of unique individual tests or exhaustive coverage.

The current README offers Docker Compose on one Linux VM or Kubernetes for self-hosting and describes contributor setup as Docker-based. Our run did not validate either deployment path, launch the CLI successfully, or complete an agent workload.

Should you pilot SuperPlane?

Start with a small bug, test fix or documentation task whose result a maintainer can inspect. SuperPlane's current README centers on moving suitable backlog issues through coding agents, verification and review. That is a more specific reason to evaluate it than a general need to connect engineering tools.

The SuperPlane README describes a system that coordinates coding agents, source control, CI, review, approvals and feedback. This is the project's description of its capability, not an outcome demonstrated by our sandbox. Its suggested first step is to connect a GitHub repository and choose a small task. Keep human review in that first trial and check what happens when verification fails.

What our dated sandbox run establishes

Our run took place on October 1, 2026, at commit f9711f4. It is an existing stored execution, not a new test performed for this correction. Our sandbox had 3 CPUs and 8 GB of memory, with the golang:1.24-bookworm image; the installation tail also records a download of Go 1.26.2.

The harness recorded the test command exiting 1 after 178 seconds. Installation was recorded as exit 0 after 90 seconds. The build step was recorded as exit 0 after 8 seconds, but its retained output reports missing modules, including the OpenAPI client and protocol packages, and ends with vet-exit:1. Preserve both observations: the outer command status and the errors inside its output disagree about whether this was a clean build. The excerpt does not establish why the outer status remained zero.

The attached stored parser summaries contain 195 passing and 83 failing entries, totaling 278. The raw measurement calls these package outcomes and separately records 17 packages with no tests. These summaries do not establish unique individual-test counts or exhaustive coverage. Packages with no tests are not failed tests, and we have not reconciled the complete logs.

The retained test tail explicitly names TestResolveHTTPPolicyInTransaction as failing in pkg/networkpolicy. That is one visible failure, not an explanation of every failing entry in the summary. The excerpt does not show enough assertion detail to assign its cause.

Our harness stores step status, exit code, elapsed time, parsed counts and output tails separately. Reading those fields together exposes the build discrepancy. The MrKeyoor testing methodology explains this reporting approach and its limits; the supplied methodology page was fetched on October 31, 2026, and does not prove that its current procedure was used unchanged for this older run.

What the factory adds to an agent

The README at the measured commit describes a factory containing work orders, ordered processing lines and automations. An automation can run an agent, call a tool, wait for an event or require approval. Runs retain execution state, inputs, outputs, retries and cost.

That model gives a pilot a useful question: can your team follow one delegated task from intake through correction and final review without losing its history? The README says state and artifacts survive retries. Our run did not test that recovery behavior, agent output quality, real integration calls, deployment, CLI operation or throughput. A zero command exit would not establish any of those outcomes.

Authorization needs its own check

Issue #6707 is closed as not planned. Its report describes missing authorization checks on widget endpoints, and its activity references a proposed fix commit. Neither the closure label nor that reference proves that the measured commit contains an effective fix.

The issue report is a reason to check the relevant endpoints and permissions during deployment review, not evidence from our own exploit test. The attached run contains no audit result, and scan coverage is unknown. It supports no conclusion that the system is secure or insecure overall.

When another platform fits better

Windmill turns scripts into shareable UIs, APIs and cron jobs that can be composed into flows. Consider it when your starting point is scripts and internal applications rather than backlog tasks delegated to agents. This is an alternative for that automation scope; the supplied source does not establish a drop-in replacement for SuperPlane's factory.

Temporal executes application workflows with automatic handling of intermittent failures and retries. Consider it when developers want to implement durable application logic through its supported languages. Its source also documents a Web UI, so choosing it does not inherently mean building every operator screen yourself. It addresses an execution requirement that may replace part of your proposed system or complement a broader engineering workflow.

These role distinctions come from the Windmill and Temporal repositories. We did not run either alternative for this comparison.

How to read the scores

Assessed scores use a five-point rubric: 1 means substantial demonstrated obstacles; 2 means material unresolved obstacles; 3 means adequate evidence for a bounded use; 4 means broad, directly supported readiness in that dimension; 5 means comprehensive validation in the stated scope. Setup concerns reproducibility, documentation concerns usable instructions, community concerns sustained participation and support, and maturity concerns operational readiness. Unknown dimensions remain unassessed.

Setup ease is 2 because the stored build output contains unresolved module errors and the tests exit nonzero. Maturity is 2 because this run leaves material verification gaps before operational use. These ratings concern the supplied evidence, not a claim that every deployment fails. Documentation and community remain unassessed because the supplied extracts do not establish their practical completeness or sustained support.

Alternatives

ProjectWhat it isPick it when
Windmill gh↗A platform for composing scripts into workflows, applications and agent tasks.Consider Windmill when scripts, generated interfaces, APIs and scheduled jobs are the main requirement; assess it as an alternative for that scope.
Temporal gh↗A durable execution platform for application workflows with failure handling and retries.Consider Temporal when developers need durable application logic in supported languages; it can address the execution layer without replacing every part of an engineering factory.

What people are saying

  1. [github-trending] superplanehq/superplane

Sources

  1. SuperPlane README
  2. SuperPlane v0.30.0 release
  3. Widget authorization bypass issue
  4. Coolify write-action issue
  5. SSH secret environment issue

More automation reviews