README
¶
Website · Docs · Discord · Blog · Event
About
Open source factory for one-shot engineering.
SuperPlane turns high-confidence backlog issues into verified, review-ready pull requests so engineers can focus on work that needs judgment.
SuperPlane lets AI agents fully automate routine development work. It coordinates coding agents, source control, CI, review, approvals and feedback in one visible system so engineers do not have to project-manage every step.
The factory continuously evaluates which backlog issues agents can handle with high confidence. It applies the same workflow-level guardrails to every run, checks the result and sends failures back to the agent with actionable context. Ambiguous work and decisions that need human judgment stay with your team.
SuperPlane is built on an Apache 2.0 open source engine. Choose your models, run in the cloud or on-prem and build the factory around your stack and cost constraints.
How the factory works
A SuperPlane Factory turns incoming work into a durable operational record. A work order enters through the backlog, moves through one or more automation lines and produces pull requests, notes, branches and other reviewable artifacts.
| Resource | What it does |
|---|---|
| Factory | Holds work orders, automation lines and the policies for a team. |
| Work order | Records one delegated task from intake through its final outcome. |
| Line | Defines the ordered stages that process a work order. |
| Automation | Runs an agent, calls a tool, waits for an event or requires approval through a Canvas-backed app. |
| Run | Tracks durable execution, inputs, outputs, retries and cost for one automation step. |
Every step stays visible. SuperPlane preserves the event history, execution state and artifacts across retries so a failed run can resume without custom glue or lost context.
Built around your stack
SuperPlane coordinates the systems where engineering work already happens. Each integration provides event triggers and actions that you can compose on a Canvas.
| Area | Examples |
|---|---|
| AI and coding agents | Claude, Cursor, OpenAI, OpenRouter and Perplexity |
| Source control and CI | GitHub, GitLab, Bitbucket, Semaphore, CircleCI and Harness |
| Cloud and delivery | AWS, Google Cloud, Azure, Cloudflare, Docker Hub and Render |
| Observability | Datadog, Grafana, Honeycomb, New Relic, Prometheus and Sentry |
| Incidents and service management | PagerDuty, Rootly, FireHydrant, incident.io, Jira and ServiceNow |
| Communication | Slack, Discord, Microsoft Teams, Telegram, SendGrid and SMTP |
Contributing
We welcome focused pull requests, bug reports and product ideas.
- Read the contributing guide.
- Review the issue tracking process.
- Find an open issue or an open bounty.
- Join the Discord community to discuss an approach with maintainers.
Contributor setup is Docker-based. Start with the repository instructions in
AGENTS.md and the development section of
CONTRIBUTING.md.
Community and license
- Discord for discussions and support
- Blog for engineering notes and releases
- Community events for maintainer sessions
- X for product updates
SuperPlane is available under the Apache License 2.0.
Directories
¶
| Path | Synopsis |
|---|---|
|
cmd
|
|
|
admin
command
|
|
|
cli
command
|
|
|
fleetmanager
command
|
|
|
runner
command
|
|
|
server
command
|
|
|
ee
|
|
|
pkg
|
|
|
agents
Package agents defines the provider interface SuperPlane uses to talk to managed-agent backends, and a service layer that persists sessions and routes streamed events through the event distributor.
|
Package agents defines the provider interface SuperPlane uses to talk to managed-agent backends, and a service layer that persists sessions and routes streamed events through the event distributor. |
|
agents/anthropic
Package anthropic implements agents.Provider against Anthropic's managed-agents API.
|
Package anthropic implements agents.Provider against Anthropic's managed-agents API. |
|
components/memorywrite
Package memorywrite holds shared list-mode helpers used by the memory write components (addMemory, updateMemory, upsertMemory).
|
Package memorywrite holds shared list-mode helpers used by the memory write components (addMemory, updateMemory, upsertMemory). |
|
configuration/structuredoutput
Package structuredoutput lets LLM components accept a JSON Schema describing the desired response, validating it and normalizing it to the constraints strict-mode providers enforce (every object gets "additionalProperties": false; strict mode also requires listing every property in "required").
|
Package structuredoutput lets LLM components accept a JSON Schema describing the desired response, validating it and normalizing it to the constraints strict-mode providers enforce (every object gets "additionalProperties": false; strict mode also requires listing every property in "required"). |
|
factories/vcs
Package vcs is the factory workspace Git host seam.
|
Package vcs is the factory workspace Git host seam. |
|
features
Package features holds the registry of experimental features that can be enabled per organization.
|
Package features holds the registry of experimental features that can be enabled per organization. |
|
grpc/actions/agents
Package agents implements the gRPC handlers for the public Agents service.
|
Package agents implements the gRPC handlers for the public Agents service. |
|
integrations/statuspage
Package statuspage implements the Atlassian Statuspage integration.
|
Package statuspage implements the Atlassian Statuspage integration. |
|
licensing/devlicense
Package devlicense grants every Enterprise feature to the development server.
|
Package devlicense grants every Enterprise feature to the development server. |
|
licensing/licensingtest
Package licensingtest signs licenses with ephemeral keys for tests.
|
Package licensingtest signs licenses with ephemeral keys for tests. |
|
registryimports
Package registryimports loads all built-in components, integrations, triggers, and widgets so they register themselves via init().
|
Package registryimports loads all built-in components, integrations, triggers, and widgets so they register themselves via init(). |
|
retry
Package retry holds a helper function for retrying a task.
|
Package retry holds a helper function for retrying a task. |
|
db_reset_after_onboarding
command
|
|
|
integrations
command
|
|
|
test
|
|