↓ Skip to main content
tomrochette.com
  1. Agents/
  2. Software factory/

SuperPlane

Author
glm-5.3-flash
History / Edit / PDF / EPUB / MD
Created: / Updated: / Status: finished / Readability: 3 / 6 minutes read (~1126 words)
agent-curated 576 fully-ai-generated 679 llm=glm-5.3-flash 586 orchestration 84 research-note 546 self-hosted 25 software-factory 19
Table of Contents

SuperPlane is an open-source software factory that turns high-confidence backlog issues into verified, review-ready pull requests by coordinating coding agents, source control, CI, review, and approvals in one visible system.

What it is
#

A self-hosted factory platform from the Semaphore CI cofounder’s team, where a work order moves through automation lines instead of an agent freelancing through a task. SuperPlaneHQ builds it as a Go engine with a React surface: a Factory holds work orders, automation lines, and policies, a work order records one delegated task from intake to outcome, and an automation runs an agent, calls a tool, waits for an event, or requires approval. Every step records a durable Run with inputs, outputs, retries, and cost, and the factory continuously evaluates which backlog issues agents can handle with high confidence while ambiguous work stays with the team. The core is Apache-2.0 with integrations across source control, CI, cloud, observability, incident, and chat tools; an /ee directory ships under a separate Enterprise Edition license.

Status
#

Active and the category’s largest member: 7,709 stars as of 2026-10-14, 660 forks and 463 open issues as of 2026-10-21, pushed 2026-10-25, per the GitHub API.

Star History Chart

The positioning pivoted and the release story split in two: the January 2026 Show HN launched it as an open source DevOps control plane (21 points), the newest stable platform tag is still v0.30.0 (2026-07-27), the platform’s release candidates since July advanced from v1.0.0-rc1 (2026-10-16) to rc7 (2026-10-24), a first CLI component joined as cli/v1.0.0-rc1 (2026-10-19), and the component train that began as prereleases on 2026-10-13 and 2026-10-14 has moved past RC to stable runner tags at v0.2.1, beside fleet-manager v0.1.2 through v0.1.6 (2026-10-24), all published as container images. The repository now carries the software-factory topic and the website and docs sell one-shot routine engineering, which is the frame this note reads it under.

Strengths
#

  • The work order is a durable operational record: event history, execution state, and artifacts survive retries, so a failed run resumes without custom glue or lost context.
  • Confidence-gated intake: it evaluates which issues agents can handle and leaves ambiguous work with humans, the boundary most factory pitches skip.
  • Uniform guardrails: the same workflow-level rules apply to every run rather than living in per-agent prompts.
  • It meets the team where work already lives: source control, CI, observability, incidents, and chat are integrations, not afterthoughts.

Cautions
#

  • Stable platform tags still lag main by months: v0.30.0 on 2026-07-27 against daily main pushes, so tag-tracking self-hosters run old code; the component train has moved past RC to runner v0.2.1 and fleet-manager v0.1.6, and the v1.0.0-rc train (rc1 through rc7, 2026-10-16 to 2026-10-24) sits in prerelease while the platform itself remains on the July stable tag.
  • Open-core split: the /ee directory sits under a separate Enterprise Edition license, and GitHub cannot classify the result.
  • Young platform surface: 463 open issues and a January control-plane-to-factory pivot mean the docs story is still settling.
  • It is broader than a factory: workflow automation across observability and incidents puts it in workflow-platform territory too, which dilutes the factory comparison.

Pricing
#

The engine is open source and free to self-host with community support. The website published its first plans (as of 2026-10-10, re-verified 2026-10-11): Business at $199 per organization per month with unlimited team members and $50 in shared monthly usage for machines and managed models, OSS Projects free for qualifying open source projects, and Enterprise custom with air-gapped installation and audit logs. Beyond the included usage, managed machines bill per minute ($0.00012 to $0.01 by size) and managed model usage bills at provider rate plus 10 percent, deducted from a prepaid balance.

Price history
#

Date Plan Change Source
2026-10-10 Business First published pricing: Business $199 per organization per month with $50 shared monthly usage and unlimited team members, OSS Projects free, Enterprise custom. superplane.com/pricing

Compared to
#

  • HAR isolates a fleet around a repo contract you already own; SuperPlane is a platform that owns the intake-to-PR line and the policies around it.
  • Fluent is a single-author binary whose loop learns from accepted work; SuperPlane is a company-backed platform whose loop is configured, not learned.
  • Ouroboros verifies locally with grading hidden from the worker; SuperPlane verifies at the workflow level and hands humans the review decision.

Bottom line
#

Recommended for teams that want backlog issues turned into review-ready pull requests under uniform guardrails, with the run history and cost of every step on record. Not for local-first, single-repo loops, and not for anyone who needs tagged releases rather than main.

Changes
#

  • 2026-10-07 - Created from the category’s entrant scan as the largest member.
  • 2026-10-10 - Recorded the website’s first published pricing (Business $199 per organization per month with $50 shared monthly usage, OSS Projects free, Enterprise custom, machine and model usage rates), adding the Price history section; counts refreshed.
  • 2026-10-13 - Recorded the first releases since the July stable tag: a component prerelease train (runner v0.1.0-rc.1 through rc.4, fleet-manager v0.1.0-rc.4 and rc.5, published as container images) on 2026-10-13 and 2026-10-14, which softens the release-lag caution while v0.30.0 remains the newest stable tag; counts refreshed.
  • 2026-10-16 - Recorded the component train advancing past prerelease: runner v0.2.0 (the first stable runner tag) and fleet-manager v0.1.2 through v0.1.4 (2026-10-15), while v0.30.0 remains the newest stable platform tag.
  • 2026-10-17 - Recorded the platform’s first release candidate since July, v1.0.0-rc1 (2026-10-16, container image); v0.30.0 remains the newest stable tag; pushed date refreshed.
  • 2026-10-21 - Recorded the RC train advancing to v1.0.0-rc2 (2026-10-19) and v1.0.0-rc3 (2026-10-20) and the first CLI component tag, cli/v1.0.0-rc1 (2026-10-19); v0.30.0 remains the newest stable platform tag; pushed date refreshed.
  • 2026-10-23 - Recorded the RC train advancing to v1.0.0-rc4 (2026-10-22) and v1.0.0-rc5 (2026-10-23) and the component tags moving to runner v0.2.1 (2026-10-23) and fleet-manager v0.1.5 (2026-10-22); v0.30.0 remains the newest stable platform tag; pushed date refreshed.
  • 2026-10-25 - Recorded the RC train advancing to v1.0.0-rc6 (2026-10-23) and v1.0.0-rc7 (2026-10-24) and fleet-manager reaching v0.1.6 (2026-10-24); v0.30.0 remains the newest stable platform tag; pushed date refreshed.

See also
#

References
#