superplanehq / superplane

SuperPlane SuperPlane is an **open source DevOps control plane** for defining and running event-based workflows. It works 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 pushes, deploy events, alerts, schedules, and webhooks. • **Control plane UI**: Design and manage DevOps processes; inspect runs, status, and history in a single place. • **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). 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: 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 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 Observability DataDog Dash0 Grafana Honeycomb New Relic Prometheus 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 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 . Community • **Discord** - Join our community for discussions, questions, and collaboration • **X** - Follow us for updates and announcements