SuperPlane logo
Docs Blog GitHub
Blog

Introducing SuperPlane

Announcing the first release of SuperPlane, an open source DevOps control plane for event-driven workflows.

Today we’re open-sourcing SuperPlane, a DevOps control plane for defining and running event-driven workflows. It works across the tools teams already use, such as Git, CI/CD, observabiity, incident response, notifications, infrastructure, and more.

SuperPlane is built for workflows that don’t fit neatly into a single CI pipeline: long-running processes, cross-tool and cross-repository orchestration, human approvals, verification steps, and the need for a clear audit trail of what happened.

You can self-host it today and try one of the included example workflows.

SuperPlane canvas example
Automated rollback workflow in SuperPlane, with step-by-step run history: triggers, actions, and outcomes.

Why we built it

In many teams, operational workflows are stitched together with a mix of brittle scripts, one-off CI jobs, bespoke GitOps, and manual approvals spread across team chat and issue trackers. As developers learn to ship more code with AI, traditional DevOps becomes the bottleneck.

From building Semaphore (CI/CD), we learned pipelines are great at testing and deploying code from a single repository, but the messy cross-tool, human-in-the-loop workflows around releases, incidents, and infrastructure changes still end up as tribal knowledge.

SuperPlane’s thesis is simple: it’s time for an open source interoperability layer for DevOps that replaces tribal knowledge.

SuperPlane gives you first-class components to encode how your system behaves, including services, environments, releases, incidents, signals. Once a full model is in place, you can safely run cross-tool workflows across it with approvals, verification, and an end-to-end event history.

What’s included in this open source launch

  • A self-hosted product you can run locally, in your own cloud or on Kubernetes
  • Apache 2.0 licensed code in the repository
  • A graphical control plane UI for creating workflows and inspecting run history
  • Practical examples: workflows for release management and incident-response-adjacent automation
  • Integrations: AWS Lambda, Cloudflare, Dash0, GitHub, OpenAI, PagerDuty, Semaphore, Slack, SMTP, webhooks

What this is not (yet)

To keep expectations clear, the project is currently in alpha, so it’s most suitable for experimentation.

Although we run production workloads on SuperPlane ourselves, expect rough edges and occasional breaking changes while we stabilize core components and integrations.

There is no hosted version today, but you can sign up for the waitlist to be notified when it’s available.

Concrete example workflows

The SuperPlane installation comes with a few example workflows to get you started:

  • Policy-gated deployment: Gate deployments with a policy check, business hours, and approval.
  • Progressive delivery orchestration: Gradually roll out releases through 10%, 50%, and 100% stages with health checks and rollback paths at each step.
  • Automated rollback: Automatically trigger rollback workflows when deployments fail and verify system health via observability tool.
  • Multi-repo release: Coordinate releases across multiple repositories with unified CI builds and deployments.
  • First 5 minutes of incident triage: Collect relevant data and metrics when new P1/P2 incident is opened and create a GitHub issue.
  • Incident router: Route P1 incidents from Slack mentions to PagerDuty and GitHub with AI-generated titles and descriptions.

Try it locally

Quick start:

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

Find your preferred deployment method in the installation guide.

Links:

How to get involved

We’re building SuperPlane in the open, and we’re looking for feedback and contributions.