README
¶
SuperPlane
SuperPlane is an open source control plane for platform engineering. It lets you define and run event-based workflows across the tools you already use such as Git, CI/CD, observability, incident response, infra, and notifications.
Project status
This project is in alpha stage and moving quickly. Expect rough edges and occasional breaking changes while we stabilize the core model and integrations. If you try it and hit something confusing, please open an issue. Early feedback is extremely valuable.
What it does
- Workflow orchestration: Model multi-step operational workflows that span multiple systems.
- Event-driven automation: Trigger workflows from alerts, infrastructure events, code changes, issue updates, schedules, and webhooks.
- Control plane UI & CLI: Design and manage platform engineering processes; inspect runs, manage secrets, and view history in a single place or via the CLI.
- Memory: Persist and retrieve runtime data across different paths and executions of the same canvas using built-in data storage components.
- Shared operational context: Keep workflow definitions and operational intent in one system instead of scattered scripts.
How it works
- Canvases: You model a workflow as a directed graph (a “Canvas”) of steps and dependencies.
- Components: Each step is a reusable component (built-in or integration-backed) that performs an action (for example: call CI/CD, open an incident, post a notification, wait for a condition, require approval).
- Events & triggers: Incoming events (webhooks, schedules, tool events) match triggers and start executions with the event payload as input.
- Execution + visibility: SuperPlane executes the graph, tracks state, and exposes runs/history/debugging in the UI and via the CLI.
- Agent-friendly: Equip your coding agents with SuperPlane's CLI and skills to autonomously trigger workflows, manage resources, and investigate executions.
Example use cases
A few concrete things teams build with SuperPlane:
- Policy-gated production deploy: when CI finishes green, hold outside business hours, require on-call + product approval, then trigger the deploy.
- Progressive delivery (10% → 30% → 60% → 100%): deploy in waves, wait/verify at each step, and rollback on failure with an approval gate.
- Release train with a multi-repo ship set: wait for tags/builds from a set of services, fan-in once all are ready, then dispatch a coordinated deploy.
- “First 5 minutes” incident triage: on incident created, fetch context in parallel (recent deploys + health signals), generate an evidence pack, and open an issue.
Quick start
Run the latest demo container:
docker pull ghcr.io/superplanehq/superplane-demo:stable
docker run --rm -p 3000:3000 -v spdata:/app/data -ti ghcr.io/superplanehq/superplane-demo:stable
Then open http://localhost:3000 and follow the quick start guide.
Supported Integrations
SuperPlane integrates with the tools you already use. Each integration provides triggers (events that start workflows) and components (actions you can run).
View the full list in our documentation. Missing a provider? Open an issue to request it.
AI & LLM
 Claude |
 Cursor |
 OpenAI |
 Perplexity |
Version Control & CI/CD
 Bitbucket |
 CircleCI |
 GitHub |
 GitLab |
 Harness |
 Octopus Deploy |
 Render |
 Semaphore |
Cloud & Infrastructure
 AWS ECR |
 AWS Lambda |
 AWS CodeArtifact |
 AWS CloudWatch |
 AWS SNS |
 GCP Cloud Build |
 GCP Cloud Functions |
 GCP Compute |
 Cloudflare |
 DigitalOcean |
 DockerHub |
 Hetzner Cloud |
 Azure |
Observability
 DataDog |
 Dash0 |
 Grafana |
 Honeycomb |
 New Relic |
 Prometheus |
 Elastic |
 Sentry |
Incident Management
 FireHydrant |
 Incident.io |
 PagerDuty |
 Rootly |
 Statuspage |
Communication
 Discord |
 SendGrid |
 Slack |
 SMTP |
 Microsoft Teams |
 Telegram |
Ticketing
 Jira |
 ServiceNow |
Developer Tools
 Daytona |
 JFrog Artifactory |
 LaunchDarkly |
Production installation
You can deploy SuperPlane on a single host or on Kubernetes:
- Single Host Installation - Deploy on AWS EC2, GCP Compute Engine, or other cloud providers
- Kubernetes Installation - Deploy on GKE, EKS, or any Kubernetes cluster
Installation admins can enable private network access during owner setup or later in /admin/settings when SuperPlane needs to reach tools inside a VPC, private Kubernetes cluster, or another closed network. Environment variables still take precedence: set BLOCKED_HTTP_HOSTS or BLOCKED_PRIVATE_IP_RANGES to override the UI-controlled policy, and set either variable to an empty value to disable that specific block list entirely.
Contributing
We welcome your bug reports, ideas for improvement, and focused PRs.
- Read the Contributing Guide to get started.
- Issues: use GitHub issues for bugs and feature requests.
License
Apache License 2.0. See LICENSE.
Community
Directories
¶
| Path | Synopsis |
|---|---|
|
cmd
|
|
|
cli
command
|
|
|
server
command
|
|
|
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. |
|
cli/canvasresolve
Package canvasresolve groups the small set of helpers used by multiple CLI command packages to resolve a canvas (by name or id), read canvas settings such as change management, and find or create the current user's draft version.
|
Package canvasresolve groups the small set of helpers used by multiple CLI command packages to resolve a canvas (by name or id), read canvas settings such as change management, and find or create the current user's draft version. |
|
cli/commands/console
Package console contains the `superplane console` command group.
|
Package console contains the `superplane console` command group. |
|
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). |
|
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. |
|
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. |
|
check_canvases_templates
command
|
|
|
integrations
command
|
|
|
test
|
|